Summary of amc.picc.com:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 9th, 2026 10:28 GMT+0
Source IP/Port:180.166.182.138:443
Protocol:HTTPS
Location:Shanghai, China
Your final score:
- A
- B
- C
- F
A
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 amc.picc.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 a trusted RSA 2048 bits certificate with issuer DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1 valid until January 23, 2027. 1 certificate chain detected. Show details.
- 8 of 17 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
- 9 of 17 supported cipher suites are 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.1). 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.
- 1 issue related to industry best practices was identified: server does not provide HSTS. Show details.
Compliance Summary for amc.picc.com
- PCI DSS Compliance Failed: 8 of 17 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
- HIPAA Compliance Failed: 9 of 17 supported cipher suites are 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.1). 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: 8 of 17 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.1). All supported elliptic curves are compliant with GDPR: P-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.
