Summary of queensu.ca:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 4th, 2026 00:40 GMT+0
Source IP/Port:52.139.22.141:443
Protocol:HTTPS
Location:Toronto, Canada
Your final score:
- A
- B
- C
- F
C
Test Results Summary for queensu.ca
- 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 2048 bits certificate with issuer Sectigo Public Server Authentication CA OV R36 valid until March 10, 2027. 2 certificate chains detected. Show details.
- 6 of 10 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, brainpoolP512r1, brainpoolP384r1, P-384 and brainpoolP256r1) as well as non-compliant elliptic curves (secp256k1, B-571, K-571, K-409, B-409, K-283 and B-283). There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
- 6 of 10 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, brainpoolP512r1, brainpoolP384r1, P-384 and brainpoolP256r1) as well as non-compliant elliptic curves (secp256k1, B-571, K-571, K-409, B-409, K-283 and B-283). There are 2 more issues which make the server non-compliant with HIPAA: server does not support TLS 1.3, server does not support extended master sECret. Show details.
- 1 issue related to industry best practices was identified: server does not support TLS 1.3. Show details.
Compliance Summary for queensu.ca
- PCI DSS Compliance Failed: 6 of 10 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, brainpoolP512r1, brainpoolP384r1, P-384 and brainpoolP256r1) as well as non-compliant elliptic curves (secp256k1, B-571, K-571, K-409, B-409, K-283 and B-283). There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
- HIPAA Compliance Failed: 6 of 10 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, brainpoolP512r1, brainpoolP384r1, P-384 and brainpoolP256r1) as well as non-compliant elliptic curves (secp256k1, B-571, K-571, K-409, B-409, K-283 and B-283). There are 2 more issues which make the server non-compliant with HIPAA: server does not support TLS 1.3, server does not support extended master sECret.
- GDPR Compliance Failed: 6 of 10 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, brainpoolP512r1, brainpoolP384r1, P-384 and brainpoolP256r1) as well as non-compliant elliptic curves (secp256k1, B-571, K-571, K-409, B-409, K-283 and B-283). There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.