Free tool
MTA-STS checker
Check a domain's MTA-STS record, fetch its policy file, and compare the policy with the real MX hosts. Also checks TLS-RPT. Free, no signup.
Results for
gmail.com
Looks good
Mode is enforce
Senders that support MTA-STS only deliver over TLS to the listed MX hosts.
OK
The policy covers every MX host
All 5 MX hosts match an mx line in the policy.
OK
TLS-RPT is set up
TLS failure reports go to mailto:sts-reports@google.com.
OK
_mta-sts.gmail.com
v=STSv1; id=20190429T010101;
https://mta-sts.gmail.com/.well-known/mta-sts.txt
version: STSv1 mode: enforce mx: smtp.google.com mx: gmail-smtp-in.l.google.com mx: *.gmail-smtp-in.l.google.com max_age: 86400
_smtp._tls.gmail.com
v=TLSRPTv1;rua=mailto:sts-reports@google.com
Need a policy that covers every MX host? Build the record and the policy file with the MTA-STS generator
What this checks
MTA-STS makes sending servers deliver mail to your domain over TLS, and only to the MX hosts you list. It has three parts, and this check reads each one: the TXT record at _mta-sts.yourdomain.com, the policy file at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt, and your MX records, which the mx lines in the policy must cover.
It also reads the TLS-RPT record at _smtp._tls.yourdomain.com. That record is optional, but without it nobody tells you when a sender fails to reach you over TLS.
Why an uncovered MX host matters
In enforce mode a sender refuses to deliver to an MX host that the policy does not list. If you add a backup MX or move to a new provider and forget the policy, mail to that host bounces or waits in the sender's queue. In testing mode the same gap only shows up in TLS reports.
A wildcard such as *.mail.example.net covers exactly one label. It matches eu.mail.example.net, but not mail.example.net or a.eu.mail.example.net.
How the policy file is fetched
We request the file the way a sending server does: over HTTPS, with a valid certificate, and without following redirects, because RFC 8461 forbids them. We stop after 10 seconds or 64 KB.
A file served with a content type other than text/plain gets a warning, because some senders refuse it.
Why does the check fail when the policy file opens in my browser?
Browsers follow redirects, and sending servers do not. If https://mta-sts.yourdomain.com/.well-known/mta-sts.txt redirects, for example to add a trailing slash or a www, senders ignore the policy. The certificate must also name mta-sts.yourdomain.com itself.
Do I need to change the id after editing the policy?
Yes. Senders cache the policy for max_age seconds and only fetch it again early when the id in the TXT record changes. Use 1 to 32 letters and digits, such as the current date and time.
Is a missing TLS-RPT record a problem?
It does not affect delivery. Without it you get no daily report when a sender fails to deliver over TLS, so you learn about an expired certificate or a missing mx line from bounces instead.
Should I use testing or enforce?
Start with testing, read the TLS reports for a week or two, then switch to enforce and change the id. Only enforce protects your mail; testing only reports.
Email, newsletters and booking pages on your own domain, in one plan.
Get started for free