Summary of mail.brighthouse.com:993 (IMAPS) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 199 days ago and may be outdated
Refresh Test
Date/Time:Feb 22nd, 2026 21:34 GMT+0
Source IP/Port:47.43.26.56:993
Protocol:IMAPS
Location:Mount Hope, United States
Your final score:
- A
- B
- C
- F
F
Test Results Summary for mail.brighthouse.com
- 1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer DigiCert SHA2 Secure Server CA valid until April 14, 2026. 1 certificate chain detected. Show details.
- None of the 4 supported cipher suites are compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). There are 2 more issues which make the server non-compliant with PCI DSS: goldendoodle, potential Marvin Attack. Show details.
- None of the 4 supported cipher suites are compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, server does not support TLS 1.3, 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 prefer cipher suites providing PFS, server supports client-initiated secure renegotiation. Show details.
Compliance Summary for mail.brighthouse.com
- PCI DSS Compliance Failed: None of the 4 supported cipher suites are compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). There are 2 more issues which make the server non-compliant with PCI DSS: goldendoodle, potential Marvin Attack.
- HIPAA Compliance Failed: None of the 4 supported cipher suites are compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, server does not support TLS 1.3, server does not support extended master sECret.
- GDPR Compliance Failed: None of the 4 supported cipher suites are compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). There are 2 more issues which make the server non-compliant with GDPR: goldendoodle, potential Marvin Attack.
