Summary of mydata.id.rakuten.co.jp:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 22:59 GMT+0
Source IP/Port:151.101.138.63:443
Protocol:HTTPS
Location:Montreal, Canada
Your final score:
- A
- B
- C
- F
A-
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
The server supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
Test Results Summary for mydata.id.rakuten.co.jp
- This server on the tested port supports only hybrid ML-KEM key exchange groups, which are recommended by NIST for the transition period. 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 GlobalSign Atlas R46 OV TLS CA 2026 Q4 valid until May 12, 2027. 2 certificate chains detected. Show details.
- 4 of 12 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.0 and TLSv1.1). 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.
- 5 of 12 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.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. There is 1 more issue which makes the server non-compliant with HIPAA: server supports OCSP stapling. Show details.
- No issues related to industry best practices were identified. Show details.
Compliance Summary for mydata.id.rakuten.co.jp
- PCI DSS Compliance Failed: 4 of 12 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.0 and TLSv1.1). 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 12 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.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. There is 1 more issue which makes the server non-compliant with HIPAA: server supports OCSP stapling.
- GDPR Compliance Failed: 4 of 12 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.0 and TLSv1.1). 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.
