Summary of mirror.stanford.edu:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 4th, 2026 02:08 GMT+0
Source IP/Port:171.64.64.64:443
Protocol:HTTPS
Location:Stanford, United States
Your final score:
- A
- B
- C
- F
F
The SSL certificate is untrusted. Modern browsers will display a security warning message to all website visitors. Review and remediate highlighted issues.
Non-compliant with PCI DSS requirements
Test Results Summary for mirror.stanford.edu
- 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 an untrusted RSA 4096 bits certificate with issuer InCommon Intermediate CA - OVG2C valid until May 9, 2027. 1 certificate chain detected. Show details.
- 9 of 21 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. The server supports PCI DSS compliant elliptic curves (P-256, P-521 and P-384) as well as non-compliant elliptic curves (secp256k1). There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack. Show details.
- 9 of 21 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. The server supports HIPAA compliant elliptic curves (P-256, P-521 and P-384) as well as non-compliant elliptic curves (secp256k1). 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.
- 2 issues related to industry best practices were identified: server does not support TLS 1.3, HTTP site does not redirect to the HTTPS version. Show details.
Compliance Summary for mirror.stanford.edu
- PCI DSS Compliance Failed: 9 of 21 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. The server supports PCI DSS compliant elliptic curves (P-256, P-521 and P-384) as well as non-compliant elliptic curves (secp256k1). There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack.
- HIPAA Compliance Failed: 9 of 21 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. The server supports HIPAA compliant elliptic curves (P-256, P-521 and P-384) as well as non-compliant elliptic curves (secp256k1). 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: 9 of 21 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2. The server supports GDPR compliant elliptic curves (P-256, P-521 and P-384) as well as non-compliant elliptic curves (secp256k1). There are 2 more issues which make the server non-compliant with GDPR: certificates are untrusted, potential Marvin Attack.
