Summary of mail2.eff.org:25 (SMTP) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 1684 days ago and may be outdated
Refresh Test
Date/Time:Mar 26th, 2022 17:56 GMT+0
Source IP/Port:173.239.79.204:25
Protocol:SMTP
Location:San Francisco, United States
Your final score:
- A
- B
- C
- F
F
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. NIST recommends to drop TLS 1.1 support since SP 800-52 REV. 2
Information
The tested service seems to be a SMTP.
Information
Test Results Summary for mail2.eff.org
- 1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 4096 bits certificate with issuer R3 valid until May 30, 2022. 1 certificate chain detected. Show details.
- 3 of 19 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 (TLSv1.0). The server supports PCI DSS compliant elliptic curves (P-224, P-384, P-521 and P-256) as well as non-compliant elliptic curves (P-192). No additional PCI DSS compliance issues were identified. Show details.
- 7 of 19 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 (TLSv1.0). The server supports HIPAA compliant elliptic curves (P-224, P-384, P-521 and P-256) as well as non-compliant elliptic curves (P-192). There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling. 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 mail2.eff.org
- PCI DSS Compliance Failed: 3 of 19 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 (TLSv1.0). The server supports PCI DSS compliant elliptic curves (P-224, P-384, P-521 and P-256) as well as non-compliant elliptic curves (P-192). No additional PCI DSS compliance issues were identified.
- HIPAA Compliance Failed: 7 of 19 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 (TLSv1.0). The server supports HIPAA compliant elliptic curves (P-224, P-384, P-521 and P-256) as well as non-compliant elliptic curves (P-192). There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling.
- GDPR Compliance Failed: 3 of 19 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 (TLSv1.0). The server supports GDPR compliant elliptic curves (P-224, P-384, P-521 and P-256) as well as non-compliant elliptic curves (P-192). No additional GDPR compliance issues were identified.
