Topic · Transport Security
SMTP TLS certificate chain
An SMTP TLS certificate chain links a mail server's presented leaf certificate to one or more trusted issuing authorities.
How it works
A receiving mail server may validate names, signatures, validity periods and trust anchors under its transport policy.
What can go wrong
Missing intermediates or untrusted authorities can break policy-enforced encrypted delivery.
What to check or do
Test certificate chain assembly and trust from independent SMTP clients, not only a browser.
How to investigate SMTP TLS certificate chain
- Signal to investigate
- SMTP TLS negotiation succeeds but a strict sender rejects certificate validation.
- Evidence to collect
- Inspect the presented leaf and intermediate certificates, issuer trust and selected MX hostname.
- Common wrong conclusion
- Successful encryption does not establish certificate trust or hostname validity.
How to interpret the evidence
An MTA can negotiate TLS while presenting an incomplete or unrelated certificate. Strict policy enforcement depends on validation; opportunistic delivery clients may behave differently.
What to change and how to verify it
Install the full server chain, correct the MX certificate identity, and test with strict verification against every advertised MX host.
Put this into practice
Run a focused check, then explore protection if your domain needs it.