Summary of www.uct.ac.za:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 4th, 2026 05:47 GMT+0
Source IP/Port:137.158.159.192:443
Protocol:HTTPS
Location:Cape Town, South Africa
Your final score:
- A
- B
- C
- F
B
The server supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
Test Results Summary for www.uct.ac.za
- 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 3072 bits certificate with issuer HARICA OV TLS RSA valid until February 7, 2027. 2 certificate chains detected. Show details.
- 8 of 16 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2 and TLSv1.3. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
- 9 of 16 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. There are 2 more issues which make the server non-compliant with HIPAA: certificate does not include an OCSP responder url, no support for common curves. Show details.
- 1 issue related to industry best practices was identified: server does not have cipher preference. Show details.
Compliance Summary for www.uct.ac.za
- PCI DSS Compliance Failed: 8 of 16 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2 and TLSv1.3. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
- HIPAA Compliance Failed: 9 of 16 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. There are 2 more issues which make the server non-compliant with HIPAA: certificate does not include an OCSP responder url, no support for common curves.
- GDPR Compliance Failed: 8 of 16 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2 and TLSv1.3. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.
