SSL Security Test of
www.tdcnet.com

Test Results Summary for www.tdcnet.com

• Post-Quantum Cryptography (PQC) Readiness Test
  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.
• SSL/TLS Certificate Analysis
  2 SSL/TLS end-entity certificates detected: the first certificate is a trusted RSA 2048 bits certificate with issuer WR1 valid until December 25, 2026; the second certificate is a trusted ECDSA 256 bits certificate with issuer WE1 valid until December 25, 2026. 5 certificate chains detected. Show details.
• PCI DSS Compliance Test
  4 of 12 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, P-521 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
• NIST and HIPAA Compliance Test
  4 of 12 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, P-521 and X25519. There are 2 more issues which make the server non-compliant with HIPAA: certificate does not include an OCSP responder url, server does not support TLS 1.3. Show details.
• Industry Best Practices Test
  2 issues related to industry best practices were identified: server does not support TLS 1.3, server does not provide HSTS. Show details.

Compliance Summary for www.tdcnet.com

• PCI DSS Compliance Failed: 4 of 12 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, P-521 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
• HIPAA Compliance Failed: 4 of 12 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, P-521 and X25519. There are 2 more issues which make the server non-compliant with HIPAA: certificate does not include an OCSP responder url, server does not support TLS 1.3.
• GDPR Compliance Failed: 4 of 12 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, P-521 and X25519. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.