Summary of link.renault-bank-direkt.at:443 (HTTPS) SSL Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 09:03 GMT+0
Source IP/Port:217.175.192.20:443
Protocol:HTTPS
Location:Austria
Your final score:
- A
- B
- C
- F
C+
The SSL certificate is untrusted. Modern browsers will display a security warning message to all website visitors. Review and remediate highlighted issues.
Non-compliant with PCI DSS requirements
The server supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
Test Results Summary for link.renault-bank-direkt.at
- 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 an untrusted RSA 2048 bits certificate with issuer DigiCert Global G3 TLS ECC SHA384 2020 CA1 valid until February 23, 2027. 1 certificate chain detected. Show details.
- 1 of 11 supported cipher suites is 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: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack. Show details.
- 2 of 11 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: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with HIPAA: server certificates are signed with an algorithm non-compliant with nist guidelines, server does not support OCSP stapling. Show details.
- No issues related to industry best practices were identified. Show details.
Compliance Summary for link.renault-bank-direkt.at
- PCI DSS Compliance Failed: 1 of 11 supported cipher suites is 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: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, potential Marvin Attack.
- HIPAA Compliance Failed: 2 of 11 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: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with HIPAA: server certificates are signed with an algorithm non-compliant with nist guidelines, server does not support OCSP stapling.
- GDPR Compliance Failed: 1 of 11 supported cipher suites is not compliant with GDPR. The server supports only GDPR compliant protocols: TLSv1.2 and TLSv1.3. All supported elliptic curves are compliant with GDPR: P-256, P-521, P-384, X25519 and X448. There are 2 more issues which make the server non-compliant with GDPR: certificates are untrusted, potential Marvin Attack.
