Summary of avalon.law.yale.edu:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 4th, 2026 11:06 GMT+0
Source IP/Port:52.177.206.73:443
Protocol:HTTPS
Location:Boydton, United States
Your final score:
- A
- B
- C
- F
A-
The server supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
Test Results Summary for avalon.law.yale.edu
- This server on the tested port supports only hybrid ML-KEM key exchange groups, which are recommended by NIST for the transition period. 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 GeoTrust TLS RSA CA G1 valid until April 1, 2027. 2 certificate chains detected. Show details.
- 6 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-521, P-384 and P-256. 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-521, P-384 and P-256. No additional HIPAA compliance issues were identified. Show details.
- 2 issues related to industry best practices were identified: server does not provide HSTS, TLS_fallback_scsv. Show details.
Compliance Summary for avalon.law.yale.edu
- PCI DSS Compliance Failed: 6 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-521, P-384 and P-256. 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-521, P-384 and P-256. No additional HIPAA compliance issues were identified.
- GDPR Compliance Failed: 6 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-521, P-384 and P-256. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.


