Topic · Transport Security
SMTP TLS hostname validation
SMTP TLS hostname validation checks that the presented certificate matches the expected mail server identity under the applicable policy.
How it works
MTA-STS and other authenticated policy mechanisms define the names that a receiver must validate.
What can go wrong
A certificate valid for the wrong hostname can still make an enforce-mode delivery fail.
What to check or do
Compare the actual MX hostname, certificate SAN entries and deployed MTA-STS MX patterns.
How to investigate SMTP TLS hostname validation
- Signal to investigate
- A TLS handshake succeeds but strict policy fails hostname validation.
- Evidence to collect
- Inspect the exact MX hostname, SNI behavior and certificate SANs on the SMTP endpoint.
- Common wrong conclusion
- Encryption success and hostname authentication are separate results.
How to interpret the evidence
A successful TLS handshake proves that two peers negotiated cryptography, but not necessarily that the certificate's identity matches the MX hostname. Under strict sender policies, an otherwise encrypted connection can fail because the subject alternative names do not cover the hostname or because the chain is untrusted.
What to change and how to verify it
Inspect the actual host and certificate presented by each MX, including SNI-dependent behavior. Correct the certificate or MX naming and verify with a hostname-checking client; then observe new TLS-RPT results rather than judging success from a generic 'TLS yes' scanner output.
openssl s_client -starttls smtp -connect mx.example.com:25 -servername mx.example.com -verify_hostname mx.example.comEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.