Summary of remote.atl.corning.com:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 9 days ago and may be outdated
Refresh Test
Date/Time:Oct 31st, 2026 12:29 GMT+0
Source IP/Port:199.197.129.18:443
Protocol:HTTPS
Location:Mount Hope, United States
Your final score:
- A
- B
- C
- F
C+
The SSL certificate is untrusted. Modern browsers will display a security warning message to all website visitors. Review and remediate highlighted issues.
Non-compliant with PCI DSS requirements
The server supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
Test Results Summary for remote.atl.corning.com
- 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 an untrusted RSA 2048 bits certificate with issuer Corning.com Issuing CA G2 valid until November 28, 2026. 1 certificate chain detected. Show details.
- 2 of 9 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 are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack. Show details.
- 3 of 9 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: server does not support OCSP stapling. Show details.
- No issues related to industry best practices were identified. Show details.
Compliance Summary for remote.atl.corning.com
- PCI DSS Compliance Failed: 2 of 9 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 are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack.
- HIPAA Compliance Failed: 3 of 9 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: server does not support OCSP stapling.
- GDPR Compliance Failed: 2 of 9 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 are 2 more issues which make the server non-compliant with GDPR: certificates are untrusted, potential Marvin Attack.
