Summary of protocol.z.cash:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 14:41 GMT+0
Source IP/Port:148.113.190.161:443
Protocol:HTTPS
Location:Toronto, Canada
Your final score:
- A
- B
- C
- F
A
The server has TLS 1.0 enabled. It is non-compliant with NIST since SP 800-52 REV. 2 and non-compliant with PCI DSS since the 30th of June 2018.
Non-compliant with PCI DSS and NIST
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
The server supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
Test Results Summary for protocol.z.cash
- This server on the tested port supports only hybrid ML-KEM key exchange groups, which are recommended by NIST for the transition period. 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 ECDSA 256 bits certificate with issuer YE2 valid until January 21, 2027. 2 certificate chains detected. Show details.
- All 9 supported cipher suites are compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256. No additional PCI DSS compliance issues were identified. Show details.
- 1 of 9 supported cipher suites is not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256. There is 1 more issue which makes the server non-compliant with HIPAA: certificate does not include an OCSP responder url. Show details.
- 2 issues related to industry best practices were identified: HTTP site does not redirect to the HTTPS version, server does not provide HSTS. Show details.
Compliance Summary for protocol.z.cash
- PCI DSS Compliance Failed: All 9 supported cipher suites are compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256. No additional PCI DSS compliance issues were identified.
- HIPAA Compliance Failed: 1 of 9 supported cipher suites is not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256. There is 1 more issue which makes the server non-compliant with HIPAA: certificate does not include an OCSP responder url.
- GDPR Compliance Failed: All 9 supported cipher suites are compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with GDPR: P-256. No additional GDPR compliance issues were identified.
