Topic · Transport Security
TLS certificate SAN
A Subject Alternative Name extension lists DNS identities and other accepted names for a certificate.
How it works
Modern TLS hostname checks compare the requested hostname with SAN identities under the verifier's matching rules.
What can go wrong
A certificate with only an unrelated name can fail SMTP MTA-STS checks despite being unexpired.
What to check or do
Review SAN entries for every production MX hostname and plan replacements before mail routing changes.
How to investigate TLS certificate SAN
- Signal to investigate
- A certificate is valid for mail.example.com while the receiving MX is inbound.example.com.
- Evidence to collect
- Inspect subjectAltName values, DNS MX targets and the name checked under MTA-STS policy.
- Common wrong conclusion
- A certificate matching an arbitrary web domain does not necessarily validate an SMTP MX hostname.
How to interpret the evidence
Modern certificate matching relies on SAN identity. Aliases, host migrations and shared relays often create mismatches even if TLS encryption itself works.
What to change and how to verify it
Request a certificate containing the actual mail service identity and retest from a standards-conformant external client.
Put this into practice
Run a focused check, then explore protection if your domain needs it.