MTA-STS (Mail Transfer Agent Strict Transport Security) lets a domain publish a policy saying that servers sending it mail must use TLS and must verify the receiving server's certificate and hostname. Without it, SMTP encryption is opportunistic and can be stripped by an attacker.
Why it matters
Server-to-server STARTTLS falls back to plain text when the upgrade fails, so an attacker on the path can force a downgrade or redirect mail. MTA-STS closes that gap. It has two parts: a DNS TXT record announcing a policy version, and a policy file served over HTTPS from a fixed address. It is conceptually similar to HSTS for the web. Pairing it with TLS-RPT gives visibility into failures.
Example
DNS record:
_mta-sts.example.com. IN TXT "v=STSv1; id=20261005T000000"
Policy at https://mta-sts.example.com/.well-known/mta-sts.txt:
version: STSv1
mode: testing
mx: mail.example.com
max_age: 604800
Start in testing mode, then move to enforce once reports look clean.
Common mistakes
- Forgetting to change the
idafter editing the policy, so senders keep the cached version. - Listing an
mxpattern that does not match your real MX hosts and blocking your own mail in enforce mode. - Letting the policy site's HTTPS certificate expire.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.