SSL Security Test of
eplus.ricambi.fiat.com

Test the SSL/TLS stack of your web or email server for security, cryptographic flaws and misconfigurations, and compliance with NIST & HIPAA
Free online tool with PDF report
  • Web Server SSL/TLS Security
  • Post-Quantum Cryptography (PQC) Readiness
  • Email Server SSL/TLS Security
  • PCI DSS, GDPR, HIPAA & NIST Compliance
  • SSL Certificate Validity
  • Best-Practices Compliance
Free online tool with PDF report
188,711,298 tests performed
Provided "as is" without any warranty of any kind
206
tests
running
104,163
tests
in 24 hours
Tests in 24 Hours
Share this report:

Summary of eplus.ricambi.fiat.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:151.92.198.251:443
Protocol:HTTPS
Location:Isola Maggiore, ItalyItaly
Your final score:
  • A
  • B
  • C
  • F
F
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 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
The server is vulnerable to POODLE over SSL attack. Urgently disable support of SSLv3 protocol.
Non-compliant with PCI DSS requirements
The server supports encryption protocols that are insecure and have known security flaws or weaknesses.
Non-compliant with PCI DSS, NIST and HIPAA

Test Results Summary for eplus.ricambi.fiat.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 an untrusted RSA 2048 bits certificate with issuer DigiCert Global G2 TLS RSA SHA256 2020 CA1 valid until February 27, 2027. 1 certificate chain detected. Show details.
  • PCI DSS Compliance Test
    None of the 19 supported cipher suites are compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). There are 3 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, poodle over ssl, potential Marvin Attack. Show details.
  • NIST and HIPAA Compliance Test
    None of the 19 supported cipher suites are compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). 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
    4 issues related to industry best practices were identified: server does not support TLS 1.3, server does not prefer cipher suites providing PFS, server does not provide HSTS, server supports client-initiated secure renegotiation. Show details.

Compliance Summary for eplus.ricambi.fiat.com

  • PCI DSS Compliance Failed: None of the 19 supported cipher suites are compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). There are 3 more issues which make the server non-compliant with PCI DSS: certificates are untrusted, poodle over ssl, potential Marvin Attack.
  • HIPAA Compliance Failed: None of the 19 supported cipher suites are compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). 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: None of the 19 supported cipher suites are compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2) as well as non-compliant protocols (SSLv3, TLSv1.0 and TLSv1.1). There are 3 more issues which make the server non-compliant with GDPR: certificates are untrusted, poodle over ssl, potential Marvin Attack.
Please wait. Data is loading...
Share this report: