Summary of telcel.com:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 9 days ago and may be outdated
Refresh Test
Date/Time:Oct 31st, 2026 14:13 GMT+0
Source IP/Port:201.161.100.166:443
Protocol:HTTPS
Location:Nezahualcóyotl, Mexico
Your final score:
- A
- B
- C
- F
C
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 is vulnerable to POODLE over SSL attack. Urgently disable support of SSLv3 protocol.
Non-compliant with PCI DSS requirements
The server supports encryption protocols that are insecure and have known security flaws or weaknesses.
Non-compliant with PCI DSS, NIST and HIPAA
Test Results Summary for telcel.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.
- 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 April 11, 2027. 1 certificate chain detected. Show details.
- 18 of 32 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256. There are 2 more issues which make the server non-compliant with PCI DSS: poodle over ssl, potential Marvin Attack. Show details.
- 20 of 32 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256. There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, server does not support TLS 1.3, server does not support extended master sECret. Show details.
- 3 issues related to industry best practices were identified: server does not support TLS 1.3, server does not have cipher preference, server does not provide HSTS. Show details.
Compliance Summary for telcel.com
- PCI DSS Compliance Failed: 18 of 32 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256. There are 2 more issues which make the server non-compliant with PCI DSS: poodle over ssl, potential Marvin Attack.
- HIPAA Compliance Failed: 20 of 32 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256. There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, server does not support TLS 1.3, server does not support extended master sECret.
- GDPR Compliance Failed: 18 of 32 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with GDPR: P-256. There are 2 more issues which make the server non-compliant with GDPR: poodle over ssl, potential Marvin Attack.
