Summary of detail.m.tmall.com:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 23:45 GMT+0
Source IP/Port:59.82.133.104:443
Protocol:HTTPS
Location:China
Your final score:
- A
- B
- C
- F
C+
Server supports HTTPS but it is configured to redirect to HTTP. This is a major security and privacy risk.
Misconfiguration or weakness
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 detail.m.tmall.com
- 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.
- 2 SSL/TLS end-entity certificates detected: the first certificate is a trusted RSA 2048 bits certificate with issuer GlobalSign GCC R46 OV TLS CA 2025 valid until May 13, 2027; the second certificate is a trusted ECDSA 256 bits certificate with issuer GlobalSign GCC R46 OV TLS CA 2025 valid until May 13, 2027. 2 certificate chains detected. Show details.
- 6 of 21 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-521, P-384, X25519 and X448. 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 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-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling. Show details.
- 3 issues related to industry best practices were identified: HTTP site does not redirect to the HTTPS version, HTTPs site redirECts to HTTP, server supports client-initiated secure renegotiation. Show details.
Compliance Summary for detail.m.tmall.com
- PCI DSS Compliance Failed: 6 of 21 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-521, P-384, X25519 and X448. 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 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-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling.
- GDPR Compliance Failed: 6 of 21 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-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.
