Summary of thehartford.com:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 9th, 2026 10:58 GMT+0
Source IP/Port:162.136.188.192:443
Protocol:HTTPS
Location:Hartford, United States
Your final score:
- A
- B
- C
- F
C+
Test Results Summary for thehartford.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 2048 bits certificate with issuer TrustID Server CA O1 valid until January 15, 2027. 1 certificate chain detected. Show details.
- None of the 3 supported cipher suites are compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
- None of the 3 supported cipher suites are compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. There are 2 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, server does not support TLS 1.3. Show details.
- 4 issues related to industry best practices were identified: server does not support TLS 1.3, server does not prefer cipher suites providing PFS, server does not provide HSTS, server supports client-initiated secure renegotiation. Show details.
Compliance Summary for thehartford.com
- PCI DSS Compliance Failed: None of the 3 supported cipher suites are compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
- HIPAA Compliance Failed: None of the 3 supported cipher suites are compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. There are 2 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, server does not support TLS 1.3.
- GDPR Compliance Failed: None of the 3 supported cipher suites are compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.
