Summary of mailrelay1.frankfurt.postbank.de:25 (SMTP) SSL Security Test
Provided "as is" without any warranty of any kind.
This test was made 1683 days ago and may be outdated
Refresh Test
Date/Time:Mar 27th, 2022 12:46 GMT+0
Source IP/Port:185.157.35.2:25
Protocol:SMTP
Location:Bonn, Germany
Your final score:
- A
- B
- C
- F
A-
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 tested service seems to be a SMTP.
Information
Test Results Summary for mailrelay1.frankfurt.postbank.de
- 1 SSL/TLS end-entity certificate detected: the first certificate is a trusted RSA 2048 bits certificate with issuer DigiCert EV RSA CA G2 valid until March 21, 2023. 1 certificate chain detected. Show details.
- All 4 supported cipher suites are compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0). No additional PCI DSS compliance issues were identified. Show details.
- All 4 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 (TLSv1.0). There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, no support for common curves, server does not support extended master sECret. Show details.
- 2 issues related to industry best practices were identified: server does not support TLS 1.3, server supports client-initiated secure renegotiation. Show details.
Compliance Summary for mailrelay1.frankfurt.postbank.de
- PCI DSS Compliance Failed: All 4 supported cipher suites are compliant with PCI DSS. The server supports PCI DSS compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0). No additional PCI DSS compliance issues were identified.
- HIPAA Compliance Failed: All 4 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 (TLSv1.0). There are 3 more issues which make the server non-compliant with HIPAA: server does not support OCSP stapling, no support for common curves, server does not support extended master sECret.
- GDPR Compliance Failed: All 4 supported cipher suites are compliant with GDPR. The server supports GDPR compliant protocols (TLSv1.2) as well as non-compliant protocols (TLSv1.0). No additional GDPR compliance issues were identified.
