How to fix: MTA-STS Policy File Missing
An MTA-STS TXT record exists but the policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt is not reachable. Without the policy file, the MTA-STS declaration has no effect.
Why it matters
Without a retrievable policy file, sending servers that check MTA-STS will not enforce TLS for mail delivery to your domain. STARTTLS downgrade attacks remain possible.
MTA-STS works in two parts: a DNS TXT record at _mta-sts.<domain> declares the policy ID, and the actual policy file is served over HTTPS at a well-known path. If the policy file is unreachable, the MTA-STS declaration is incomplete and sending servers will not enforce TLS.
How to fix it
- 1Serve the policy at https://mta-sts.<domain>/.well-known/mta-sts.txt with mode: enforce.
- 2Ensure the mta-sts subdomain is HTTPS-accessible with a valid certificate.
- 3Verify: curl https://mta-sts.example.com/.well-known/mta-sts.txt
Code examples
mta-sts.txt
version: STSv1
mode: enforce
mx: mail.example.com
mx: *.example.com
max_age: 604800References
Detected automatically by VulnRadar. The check id is email-mta-sts-policy-missing, stable across every scan so you can filter or diff on it.
More email checks
- LowDMARC Forensic Report URI (ruf=) Missing
- MediumDMARC Aggregate Report URI (rua=) Missing
- MediumMTA-STS (SMTP Strict Transport Security)
- LowTLS-RPT Record Missing rua= Reporting URI
- HighSPF Exceeds 10 DNS Lookup Limit
- HighSPF Redirect Loop
- LowDMARC pct= Below 100
- MediumDMARC Policy Set to Monitor-Only (p=none)
Questions
- How severe is MTA-STS Policy File Missing?
- VulnRadar rates this medium severity in the email category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id email-mta-sts-policy-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does MTA-STS Policy File Missing map to?
- It maps to CWE-319. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.