Summary of chatmegacable.megacable.com.mx: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 04:24 GMT+0
Source IP/Port:187.244.20.41:443
Protocol:HTTPS
Location:Tepic, Mexico
Your final score:
- A
- B
- C
- F
B
Test Results Summary for chatmegacable.megacable.com.mx
- 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 GeoTrust TLS RSA CA G1 valid until February 4, 2027. 1 certificate chain detected. Show details.
- 9 of 19 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. 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.
- 9 of 19 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, server does not support TLS 1.3. Show details.
- 1 issue related to industry best practices was identified: server does not support TLS 1.3. Show details.
Compliance Summary for chatmegacable.megacable.com.mx
- PCI DSS Compliance Failed: 9 of 19 supported cipher suites are not compliant with PCI DSS. The server supports only PCI DSS compliant protocols: TLSv1.2. 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: 9 of 19 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports only HIPAA compliant protocols: TLSv1.2. All supported elliptic curves are compliant with HIPAA: P-256, P-384 and X25519. There are 2 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, server does not support TLS 1.3.
- GDPR Compliance Failed: 9 of 19 supported cipher suites are not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2. 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.