Summary of www.sglp.uzh.ch:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 4th, 2026 10:41 GMT+0
Source IP/Port:130.60.184.132:443
Protocol:HTTPS
Location:Zurich, Switzerland
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 www.sglp.uzh.ch
- 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 4096 bits certificate with issuer YR1 valid until January 16, 2027. 1 certificate chain detected. Show details.
- 6 of 22 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-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
- 7 of 22 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-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with HIPAA: certificate does not include an OCSP responder url. Show details.
- 1 issue related to industry best practices was identified: server does not provide HSTS. Show details.
Compliance Summary for www.sglp.uzh.ch
- PCI DSS Compliance Failed: 6 of 22 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-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
- HIPAA Compliance Failed: 7 of 22 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-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with HIPAA: certificate does not include an OCSP responder url.
- GDPR Compliance Failed: 6 of 22 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-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.


