Summary of tuyen.blog:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 143 days ago and may be outdated
Refresh Test
Date/Time:Apr 10th, 2026 15:35 GMT+0
Source IP/Port:172.64.80.1:443
Protocol:HTTPS
Location:Unknown
Your final score:
- A
- B
- C
- F
A
Test Results Summary for tuyen.blog
- 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.
- 2 SSL/TLS end-entity certificates detected: the first certificate is a trusted RSA 2048 bits certificate with issuer WR1 valid until July 4, 2026; the second certificate is a trusted ECDSA 256 bits certificate with issuer WE1 valid until July 4, 2026. 5 certificate chains detected. Show details.
- 6 of 21 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with PCI DSS: P-256, P-384, P-521 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
- 7 of 21 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with HIPAA: P-256, P-384, P-521 and X25519. No additional HIPAA compliance issues were identified. Show details.
- No issues related to industry best practices were identified. Show details.
Compliance Summary for tuyen.blog
- PCI DSS Compliance Failed: 6 of 21 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with PCI DSS: P-256, P-384, P-521 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
- HIPAA Compliance Failed: 7 of 21 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with HIPAA: P-256, P-384, P-521 and X25519. No additional HIPAA compliance issues were identified.
- GDPR Compliance Failed: 6 of 21 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with GDPR: P-256, P-384, P-521 and X25519. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.
