Summary of aspmx.l.google.com:25 (SMTP) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 9 days ago and may be outdated
Refresh Test
Date/Time:Oct 26th, 2026 23:36 GMT+0
Source IP/Port:172.253.115.27:25
Protocol:SMTP
Location:Mount Hope, United States
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 aspmx.l.google.com
- This server on the tested port supports both hybrid and pure ML-KEM post-quantum key exchange groups approved by NIST, providing full readiness for the post-quantum transition. The server’s certificate chain relies entirely on classical signature algorithms without post-quantum support. Show details.
- 2 SSL/TLS end-entity certificates detected: the first certificate is a trusted RSA 2048 bits certificate with issuer WR2 valid until December 21, 2026; the second certificate is a trusted ECDSA 256 bits certificate with issuer WE2 valid until December 21, 2026. 5 certificate chains detected. Show details.
- 4 of 15 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 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack. Show details.
- 5 of 15 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 and X25519. There is 1 more issue which makes the server non-compliant with HIPAA: certificate does not include an OCSP responder url. Show details.
- No issues related to industry best practices were identified. Show details.
Compliance Summary for aspmx.l.google.com
- PCI DSS Compliance Failed: 4 of 15 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 and X25519. There is 1 more issue which makes the server non-compliant with PCI DSS: potential Marvin Attack.
- HIPAA Compliance Failed: 5 of 15 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 and X25519. There is 1 more issue which makes the server non-compliant with HIPAA: certificate does not include an OCSP responder url.
- GDPR Compliance Failed: 4 of 15 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 and X25519. There is 1 more issue which makes the server non-compliant with GDPR: potential Marvin Attack.
