Topic · Transport Security
MTA-STS policy hosting
MTA-STS policy hosting makes a text policy available at the fixed HTTPS endpoint on mta-sts subdomain.
How it works
Sending MTAs fetch the policy with HTTPS server authentication and cache its mode and MX constraints.
What can go wrong
Wrong paths, redirects, certificate failures or inaccessible hosts prevent policy retrieval.
What to check or do
Fetch the exact well-known URL externally and verify HTTP status, content type, syntax and HTTPS trust.
How to investigate MTA-STS policy hosting
- Signal to investigate
- _mta-sts TXT exists but remote senders fail to obtain the policy document.
- Evidence to collect
- Test https://mta-sts.example.com/.well-known/mta-sts.txt, certificate trust, MIME response and file contents.
- Common wrong conclusion
- A valid TXT discovery record alone is not sufficient to establish MTA-STS protection.
How to interpret the evidence
The policy is fetched over HTTPS at a standardized hostname and path. CDN redirects, wrong certificate names or inaccessible web hosting can invalidate deployment.
What to change and how to verify it
Serve an accessible HTTPS policy with matching MX patterns, update its id on changes and verify from outside the hosting network.
curl -I https://mta-sts.example.com/.well-known/mta-sts.txtEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.