SSL Security Test of
apmone.newchinalife.com

Test the SSL/TLS stack of your web or email server for security, cryptographic flaws and misconfigurations, and compliance with NIST & HIPAA
Free online tool with PDF report
  • Web Server SSL/TLS Security
  • Post-Quantum Cryptography (PQC) Readiness
  • Email Server SSL/TLS Security
  • PCI DSS, GDPR, HIPAA & NIST Compliance
  • SSL Certificate Validity
  • Best-Practices Compliance
Free online tool with PDF report
188,711,298 tests performed
Provided "as is" without any warranty of any kind
206
tests
running
104,163
tests
in 24 hours
Tests in 24 Hours
Share this report:

Summary of apmone.newchinalife.com:443 (HTTPS) SSL Security Test

Provided "as is" without any warranty of any kind.
Date/Time:Nov 9th, 2026 10:26 GMT+0
Source IP/Port:106.37.215.85:443
Protocol:HTTPS
Location:Beijing, ChinaChina
Your final score:
  • A
  • B
  • C
  • F
F
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

Test Results Summary for apmone.newchinalife.com

  • Post-Quantum Cryptography (PQC) Readiness Test
    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.
  • SSL/TLS Certificate Analysis
    1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer GlobalSign RSA OV SSL CA 2018 valid until December 13, 2026. 1 certificate chain detected. Show details.
  • PCI DSS Compliance Test
    8 of 22 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with PCI DSS: diffie-hellman parameter weak, potential Marvin Attack. Show details.
  • NIST and HIPAA Compliance Test
    10 of 22 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, diffie-hellman parameter weak, server does not support TLS 1.3. Show details.
  • Industry Best Practices Test
    3 issues related to industry best practices were identified: server does not support TLS 1.3, server does not provide HSTS, server supports client-initiated secure renegotiation. Show details.

Compliance Summary for apmone.newchinalife.com

  • PCI DSS Compliance Failed: 8 of 22 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with PCI DSS: diffie-hellman parameter weak, potential Marvin Attack.
  • HIPAA Compliance Failed: 10 of 22 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, diffie-hellman parameter weak, server does not support TLS 1.3.
  • GDPR Compliance Failed: 8 of 22 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with GDPR: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with GDPR: diffie-hellman parameter weak, potential Marvin Attack.
Please wait. Data is loading...
Share this report: