Summary of pop.bizmail.yahoo.com:995 (POP3S) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 425 days ago and may be outdated
Refresh Test
Date/Time:Sep 13th, 2025 05:15 GMT+0
Source IP/Port:66.218.88.157:995
Protocol:POP3S
Location:Lockport, United States
Your final score:
- A
- B
- C
- F
B+
Email server's SPF and DMARC are properly set.
Good configuration
The server supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
The tested service seems to be a POP3S.
Information
Test Results Summary for pop.bizmail.yahoo.com
- 1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer DigiCert SHA2 High Assurance Server CA valid until November 12, 2025. 1 certificate chain detected. Show details.
- 5 of 14 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2 and TLSv1.3. 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.
- 6 of 14 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2 and TLSv1.3. 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.
- 1 issue related to industry best practices was identified: TLS_fallback_scsv. Show details.
Compliance Summary for pop.bizmail.yahoo.com
- PCI DSS Compliance Failed: 5 of 14 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2 and TLSv1.3. 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: 6 of 14 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2 and TLSv1.3. 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: 5 of 14 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2 and TLSv1.3. 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.
