SSL Security Test of
tmb.tokiomarinehd.com

Test Results Summary for tmb.tokiomarinehd.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 DigiCert Global G2 TLS RSA SHA256 2020 CA1 valid until November 27, 2026. 1 certificate chain detected. Show details.
• PCI DSS Compliance Test
  3 of 17 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. All supported elliptic curves are compliant with PCI DSS: P-256, P-384 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
• NIST and HIPAA Compliance Test
  5 of 17 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, 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 tmb.tokiomarinehd.com

• PCI DSS Compliance Failed: 3 of 17 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. All supported elliptic curves are compliant with PCI DSS: P-256, P-384 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
• HIPAA Compliance Failed: 5 of 17 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, server does not support TLS 1.3.
• GDPR Compliance Failed: 3 of 17 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2. All supported elliptic curves are compliant with GDPR: P-256, P-384 and X25519. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.