SSL Security Test of
www.tokyostarbank.co.jp

Test Results Summary for www.tokyostarbank.co.jp

• 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 GeoTrust EV RSA CA G2 valid until January 23, 2027. 1 certificate chain detected. Show details.
• PCI DSS Compliance Test
  6 of 11 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
• NIST and HIPAA Compliance Test
  6 of 11 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. There are 4 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, no support for common curves, server does not support TLS 1.3, server does not support extended master sECret. 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 have cipher preference, server-initiated secure renegotiation. Show details.

Compliance Summary for www.tokyostarbank.co.jp

• PCI DSS Compliance Failed: 6 of 11 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
• HIPAA Compliance Failed: 6 of 11 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. There are 4 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, no support for common curves, server does not support TLS 1.3, server does not support extended master sECret.
• GDPR Compliance Failed: 6 of 11 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.