
An email security standard that lets a domain require encrypted delivery. A receiving domain publishes a TXT record at _mta-sts and a policy file at https://mta-sts.yourdomain/.well-known/mta-sts.txt. Supporting senders such as Gmail and Microsoft Exchange Online fetch the policy, cache it, and then deliver mail only over TLS, only to the MX hosts the policy lists, and only when those hosts present a valid public certificate. It is defined in RFC 8461.
Why MTA-STS Matters
STARTTLS encryption between mail servers is opportunistic, so an attacker on the network path can strip it or spoof a domain’s MX records, and most senders will deliver in cleartext or to the wrong server. MTA-STS removes that fallback for domains that publish an enforce policy, protecting inbound mail against downgrade and MITM attacks without requiring DNSSEC.
MTA-STS Policy Modes
- Testing: Senders deliver even when checks fail and report the failures through TLS-RPT.
- Enforce: Senders refuse to deliver to any MX that is not listed or fails TLS validation.
- None: Senders treat the domain as having no policy, which is used to retire MTA-STS cleanly.
Related Standards
MTA-STS is usually deployed with TLS-RPT, which sends the domain daily reports on TLS failures, and it can coexist with DANE. Build a policy and check any domain with the MTA-STS Builder.