sec.upenn.edu SSL Security Test

Summary of sec.upenn.edu:443 (HTTPS) SSL Security Test

Provided "as is" without any warranty of any kind.

Date/Time:Nov 4th, 2026 08:19 GMT+0

Source IP/Port:107.20.142.159:443

Protocol:HTTPS

Location:Ashburn, United States

Your final score:

A
B
C
F

F

The server has TLS 1.1 enabled. It is non-compliant with NIST since SP 800-52 REV. 2 and non-compliant with PCI DSS since the 31st of March 2025.

Non-compliant with PCI DSS and NIST

Test Results Summary for sec.upenn.edu

Post-Quantum Cryptography (PQC) Readiness Test
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.
SSL/TLS Certificate Analysis
1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer YR2 valid until January 23, 2027. 1 certificate chain detected. Show details.
PCI DSS Compliance Test
8 of 14 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.1). The server supports PCI DSS compliant elliptic curves (P-384, P-521 and P-256) as well as non-compliant elliptic curves (secp256k1). There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
NIST and HIPAA Compliance Test
8 of 14 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.1). The server supports HIPAA compliant elliptic curves (P-384, P-521 and P-256) as well as non-compliant elliptic curves (secp256k1). There are 3 more issues which make the server non-compliant with HIPAA: certificate does not include an OCSP responder url, server does not support TLS 1.3, server does not support extended master sECret. Show details.
Industry Best Practices Test
3 issues related to industry best practices were identified: server does not support TLS 1.3, server does not have cipher preference, server does not provide HSTS. Show details.

Compliance Summary for sec.upenn.edu

PCI DSS Compliance Failed: 8 of 14 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.1). The server supports PCI DSS compliant elliptic curves (P-384, P-521 and P-256) as well as non-compliant elliptic curves (secp256k1). There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
HIPAA Compliance Failed: 8 of 14 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.1). The server supports HIPAA compliant elliptic curves (P-384, P-521 and P-256) as well as non-compliant elliptic curves (secp256k1). There are 3 more issues which make the server non-compliant with HIPAA: certificate does not include an OCSP responder url, server does not support TLS 1.3, server does not support extended master sECret.
GDPR Compliance Failed: 8 of 14 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.1). The server supports GDPR compliant elliptic curves (P-384, P-521 and P-256) as well as non-compliant elliptic curves (secp256k1). There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.