How to fix: MTA-STS (SMTP Strict Transport Security)
Async check: probes _mta-sts.<domain> for a v=STSv1 TXT record and reports its mode= value. Policy-file reachability at mta-sts.<domain>/.well-known/mta-sts.txt is verified separately by the email-mta-sts-policy-missing check.
Why it matters
Without MTA-STS, inbound SMTP sessions can be downgraded from STARTTLS to plaintext by a network attacker, exposing all email content and credentials.
MTA-STS tells sending mail servers to require TLS and refuse to deliver mail if TLS cannot be established. Without it, opportunistic STARTTLS can be stripped by a MITM between sending and receiving mail servers.
How to fix it
- 1Publish _mta-sts.<domain> TXT with v=STSv1; id=<timestamp>
- 2Serve the policy at https://mta-sts.<domain>/.well-known/mta-sts.txt
- 3Submit to the TLSRPT reporting address.
Code examples
mta-sts.txt
version: STSv1
mode: enforce
mx: *.example.com
max_age: 86400DNS TXT
_mta-sts.example.com. IN TXT "v=STSv1; id=20240101000000"References
Detected automatically by VulnRadar. The check id is mta-sts, stable across every scan so you can filter or diff on it.
More email checks
Questions
- How severe is MTA-STS (SMTP Strict Transport Security)?
- 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 mta-sts, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does MTA-STS (SMTP Strict Transport Security) 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.