Summary of mx1.ovh.net:25 (SMTP) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 80 days ago and may be outdated
Refresh Test
Date/Time:Aug 16th, 2026 13:00 GMT+0
Source IP/Port:188.165.47.122:25
Protocol:SMTP
Location:Paris, France
Your final score:
- A
- B
- C
- F
B
Email server's SPF and DMARC are properly set.
Good configuration
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 supports the most recent and secure TLS protocol version of TLS 1.3.
Good configuration
The tested service seems to be a SMTP.
Information
Test Results Summary for mx1.ovh.net
- 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 a trusted RSA 4096 bits certificate with issuer Sectigo Public Server Authentication CA DV R36 valid until October 27, 2026. 2 certificate chains detected. Show details.
- 8 of 25 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
- 11 of 25 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling. Show details.
- No issues related to industry best practices were identified. Show details.
Compliance Summary for mx1.ovh.net
- PCI DSS Compliance Failed: 8 of 25 supported cipher suites are not compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with PCI DSS: P-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
- HIPAA Compliance Failed: 11 of 25 supported cipher suites are not compliant with HIPAA requirements (Ref. NIST SP 800-52). The server supports HIPAA compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with HIPAA: P-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with HIPAA: server does not support OCSP stapling.
- GDPR Compliance Failed: 8 of 25 supported cipher suites are not compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2 and TLSv1.3) as well as non-compliant protocols (TLSv1.0 and TLSv1.1). All supported elliptic curves are compliant with GDPR: P-256, P-521, P-384, X25519 and X448. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.
