gms.jf.faw.com SSL Security Test

Summary of gms.jf.faw.com:443 (HTTPS) SSL Security Test

Provided "as is" without any warranty of any kind.

Date/Time:Nov 5th, 2026 20:48 GMT+0

Source IP/Port:3.78.194.223:443

Protocol:HTTPS

Location:Frankfurt am Main, Germany Germany

Your final score:

A
B
C
F

B-

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

Test Results Summary for gms.jf.faw.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
1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer Amazon RSA 2048 M04 valid until March 12, 2027. 2 certificate chains detected. Show details.
PCI DSS Compliance Test
6 of 12 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-384 and P-521. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
NIST and HIPAA Compliance Test
6 of 12 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 (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-384 and P-521. 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.
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 gms.jf.faw.com

PCI DSS Compliance Failed: 6 of 12 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-384 and P-521. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
HIPAA Compliance Failed: 6 of 12 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 (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-384 and P-521. 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: 6 of 12 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with GDPR: P-256, P-384 and P-521. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.