Summary of mxint01.1and1.com:25 (SMTP) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 30 days ago and may be outdated
Refresh Test
Date/Time:Oct 5th, 2026 11:49 GMT+0
Source IP/Port:212.227.126.206:25
Protocol:SMTP
Location:Kassel, Germany
Your final score:
- A
- B
- C
- F
C
Email server's SPF, DMARC and DKIM are properly set.
Good configuration
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. It is non-compliant with NIST since SP 800-52 REV. 2 and non-compliant with PCI DSS since the 31st of March 2025.
Non-compliant with PCI DSS and NIST
The server supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
The tested service seems to be a SMTP.
Information
Test Results Summary for mxint01.1and1.com
- The server on the tested port is currently not prepared for post-quantum key exchange. The server’s certificate chain relies entirely on classical signature algorithms without post-quantum support. Show details.
- 1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 3072 bits certificate with issuer Telekom Security OV RSA CA 26A valid until March 2, 2027. 2 certificate chains detected. Show details.
- 4 of 16 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-384, P-521, P-256, X25519 and X448. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
- 5 of 16 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-384, P-521, P-256, X25519 and X448. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling. Show details.
- 2 issues related to industry best practices were identified: server does not have cipher preference, server supports client-initiated secure renegotiation. Show details.
Compliance Summary for mxint01.1and1.com
- PCI DSS Compliance Failed: 4 of 16 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-384, P-521, P-256, X25519 and X448. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
- HIPAA Compliance Failed: 5 of 16 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-384, P-521, P-256, X25519 and X448. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling.
- GDPR Compliance Failed: 4 of 16 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with GDPR: P-384, P-521, P-256, X25519 and X448. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.
