Summary of support.coro.net:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 15:29 GMT+0
Source IP/Port:3.33.251.168:443
Protocol:HTTPS
Location:Mount Hope, United States
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 support.coro.net
- 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.
- 3 SSL/TLS end-entity certificates detected: the first certificate is a trusted RSA 2048 bits certificate with issuer GoDaddy TLS Intermediate CA DV - R1v1 valid until December 31, 2026; the second certificate is a trusted RSA 2048 bits certificate with issuer GoDaddy TLS Intermediate CA DV - R1v1 valid until December 31, 2026; the third certificate is a trusted RSA 2048 bits certificate with issuer GoDaddy TLS Intermediate CA DV - R1v1 valid until December 31, 2026. 6 certificate chains detected. Show details.
- All 3 supported cipher suites are compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.3. No additional PCI DSS compliance issues were identified. Show details.
- 1 of 3 supported cipher suites is not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.3. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling. Show details.
- 1 issue related to industry best practices was identified: server supports client-initiated secure renegotiation. Show details.
Compliance Summary for support.coro.net
- PCI DSS Compliance Passed: All 3 supported cipher suites are compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.3. No additional PCI DSS compliance issues were identified.
- HIPAA Compliance Failed: 1 of 3 supported cipher suites is not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.3. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling.
- GDPR Compliance Passed: All 3 supported cipher suites are compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.3. No additional GDPR compliance issues were identified.
