Summary of mail.walkingtoweb.com:25 (SMTP) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 436 days ago and may be outdated
Refresh Test
Date/Time:Aug 25th, 2025 08:48 GMT+0
Source IP/Port:192.162.204.51:25
Protocol:SMTP
Location:Eich, Switzerland
Your final score:
- A
- B
- C
- F
C
Email server's SPF, DMARC and DKIM are properly set.
Good configuration
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 mail.walkingtoweb.com
- 1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer Thawte TLS RSA CA G1 valid until August 24, 2026. 1 certificate chain 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.1). All supported elliptic curves are compliant with PCI DSS: P-256. There are 2 more issues which make the server non-compliant with PCI DSS: diffie-hellman parameter weak, 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.1). All supported elliptic curves are compliant with HIPAA: P-256. There are 2 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, diffie-hellman parameter weak. Show details.
- 1 issue related to industry best practices was identified: server supports client-initiated secure renegotiation. Show details.
Compliance Summary for mail.walkingtoweb.com
- 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.1). All supported elliptic curves are compliant with PCI DSS: P-256. There are 2 more issues which make the server non-compliant with PCI DSS: diffie-hellman parameter weak, 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.1). All supported elliptic curves are compliant with HIPAA: P-256. There are 2 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, diffie-hellman parameter weak.
- 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.1). All supported elliptic curves are compliant with GDPR: P-256. There are 2 more issues which make the server non-compliant with GDPR: diffie-hellman parameter weak, potential Marvin Attack.
