Summary of smtp.netcup.net:25 (SMTP) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 1683 days ago and may be outdated
Refresh Test
Date/Time:Mar 27th, 2022 17:30 GMT+0
Source IP/Port:46.38.225.170:25
Protocol:SMTP
Location:Kassel, Germany
Your final score:
- A
- B
- C
- F
F
The server has TLS 1.0 enabled. It is non-compliant with NIST since SP 800-52 REV. 2 and non-compliant with PCI DSS since the 30th of June 2018.
Non-compliant with PCI DSS and NIST
The server has TLS 1.1 enabled. NIST recommends to drop TLS 1.1 support since SP 800-52 REV. 2
Information
The server is vulnerable to POODLE over SSL attack. Urgently disable support of SSLv3 protocol.
Non-compliant with PCI DSS requirements
The server supports encryption protocols that are insecure and have known security flaws or weaknesses.
Non-compliant with PCI DSS, NIST and HIPAA
The tested service seems to be a SMTP.
Information
Test Results Summary for smtp.netcup.net
- 1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer RapidSSL TLS DV RSA Mixed SHA256 2020 CA-1 valid until October 25, 2022. 1 certificate chain detected. Show details.
- 27 of 51 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.1 and TLSv1.2) as well as non-compliant protocols (SSLv3 and TLSv1.0). All supported elliptic curves are compliant with PCI DSS: P-256. There are 2 more issues which make the server non-compliant with PCI DSS: diffie-hellman parameter weak, poodle over ssl. Show details.
- 33 of 51 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.1 and TLSv1.2) as well as non-compliant protocols (SSLv3 and TLSv1.0). All supported elliptic curves are compliant with HIPAA: P-256. There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, diffie-hellman parameter weak, server does not support extended master sECret. Show details.
- 3 issues related to industry best practices were identified: server does not support TLS 1.3, server does not have cipher preference, server supports client-initiated secure renegotiation. Show details.
Compliance Summary for smtp.netcup.net
- PCI DSS Compliance Failed: 27 of 51 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.1 and TLSv1.2) as well as non-compliant protocols (SSLv3 and TLSv1.0). All supported elliptic curves are compliant with PCI DSS: P-256. There are 2 more issues which make the server non-compliant with PCI DSS: diffie-hellman parameter weak, poodle over ssl.
- HIPAA Compliance Failed: 33 of 51 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.1 and TLSv1.2) as well as non-compliant protocols (SSLv3 and TLSv1.0). All supported elliptic curves are compliant with HIPAA: P-256. There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, diffie-hellman parameter weak, server does not support extended master sECret.
- GDPR Compliance Failed: 27 of 51 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.1 and TLSv1.2) as well as non-compliant protocols (SSLv3 and TLSv1.0). All supported elliptic curves are compliant with GDPR: P-256. There are 2 more issues which make the server non-compliant with GDPR: diffie-hellman parameter weak, poodle over ssl.
