SSL Security Test of
samsungfire.com

Test Results Summary for samsungfire.com

• Post-Quantum Cryptography (PQC) Readiness Test
  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.
• SSL/TLS Certificate Analysis
  1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer Sectigo Public Server Authentication CA OV R36 valid until April 14, 2027. 2 certificate chains detected. Show details.
• PCI DSS Compliance Test
  4 of 8 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: 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
  5 of 8 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: X25519. There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, no support for common curves, EC point format extension. Show details.
• Industry Best Practices Test
  2 issues related to industry best practices were identified: server does not have cipher preference, server does not provide HSTS. Show details.

Compliance Summary for samsungfire.com

• PCI DSS Compliance Failed: 4 of 8 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: X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
• HIPAA Compliance Failed: 5 of 8 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: X25519. There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, no support for common curves, EC point format extension.
• GDPR Compliance Failed: 4 of 8 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: X25519. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.