Summary of stanford.edu:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 4th, 2026 02:00 GMT+0
Source IP/Port:171.67.215.200:443
Protocol:HTTPS
Location:Menlo Park, 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
CA of your SSL certificate is distrusted by Google Chrome and Mozilla Firefox.
Misconfiguration or weakness
Certificate chain relies on expired certificate, it can break connection for some clients.
Misconfiguration or weakness
Test Results Summary for 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 2048 bits certificate with issuer InCommon Intermediate CA - DVG2C valid until May 14, 2027. 1 certificate chain detected. Show details.
- 6 of 12 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. All supported elliptic curves are compliant with PCI DSS: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack. Show details.
- 6 of 12 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. 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 supports client-initiated secure renegotiation, certificate chain rely on expired certificate. Show details.
Compliance Summary for stanford.edu
- PCI DSS Compliance Failed: 6 of 12 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. All supported elliptic curves are compliant with PCI DSS: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack.
- HIPAA Compliance Failed: 6 of 12 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. 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: 6 of 12 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2. All supported elliptic curves are compliant with GDPR: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with GDPR: certificates are untrusted, potential Marvin Attack.
