Topic · Transport Security
MTA-STS
Mail Transfer Agent Strict Transport Security lets a receiving domain publish an HTTPS policy requiring supported senders to use authenticated TLS.
How it works
A DNS policy ID points to an HTTPS policy that lists permitted MX hosts and a mode.
What can go wrong
A policy mismatch or expired certificate can block delivery from supporting senders.
What to check or do
Start in testing mode, validate MX hostnames and certificates, then enforce.
Practical scenario
A domain hosts an MTA-STS policy listing mail1.example.com but its secondary MX mail2.example.com is omitted. In enforce mode, policy-aware sending systems may defer delivery to the secondary MX even if its certificate is otherwise valid.
Verification checklist
- Verify the HTTPS policy file is publicly retrievable and syntactically valid.
- Compare every active MX hostname with declared mx patterns.
- Check certificate chain, identity and expiry for each host.
- Use TLS reports during testing before switching to enforce mode.
How to investigate MTA-STS
- Signal to investigate
- An SMTP sender refuses delivery after a secondary MX fails hostname validation against policy.
- Evidence to collect
- Check both the HTTPS policy and each active MX hostname/certificate before enforcing.
- Common wrong conclusion
- A published MTA-STS TXT record without a retrievable valid HTTPS policy is incomplete.
How to interpret the evidence
MTA-STS has a discovery TXT record and a separate HTTPS-served policy file. A strict sending system checks MX patterns and TLS identity against the policy it knows, which may be cached for the configured lifetime. This makes staged rollout and secondary-MX compatibility essential; a perfectly valid HTTPS site at the root domain is not the policy endpoint.
What to change and how to verify it
Fetch the policy using the required host/path and test every advertised MX hostname and certificate, including alternate IP families. Use testing mode and TLS-RPT to observe failures where appropriate before moving to enforce. Coordinate server and certificate changes with policy max_age.
dig +short TXT _mta-sts.example.com
curl -i https://mta-sts.example.com/.well-known/mta-sts.txtEducational example; not validated against your live infrastructure._mta-sts.example.com TXT "v=STSv1; id=20261119"Put this into practice
Run a focused check, then explore protection if your domain needs it.