MTA-STS Checker
Type a domain to test its MTA-STS setup (RFC 8461), the standard that tells other mail servers to deliver to it only over TLS, to a mail server with a valid certificate. It has two parts and the checker reads both: a TXT record at _mta-sts.<domain> saying a policy exists (v=STSv1 and an id), and a policy file served over HTTPS at https://mta-sts.<domain>/.well-known/mta-sts.txt that sets the mode (enforce, testing or none), the mail servers allowed (mx: lines) and how many seconds senders cache it (max_age). It then matches every MX host against the mx: lines, because in enforce mode a server the policy leaves out stops receiving mail, and reads the TLS-RPT record at _smtp._tls.<domain> that says where senders report TLS failures. On 13 November 2026, gmail.com enforced its policy with a one-day max_age, while yahoo.com was still in testing mode.
Free, no sign-in, 20 lookups a minute. Answers are cached for 5 minutes. Also: DNS lookup, MX lookup, Nameserver lookup, TXT record lookup, SPF record checker, DMARC checker, DKIM checker, CNAME lookup, DNS propagation checker, reverse DNS lookup, BIMI checker, email deliverability checker.
MTA-STS on well-known mail domains
Checked through this tool on November 13, 2026. Click a name to run it live.
| Domain | Policy | mx lines | max_age | TLS-RPT | Findings |
|---|---|---|---|---|---|
| gmail.com | enforce | 3 | 1 d | yes | max_age under a week |
| google.com | enforce | 3 | 1 d | yes | max_age under a week |
| microsoft.com | enforce | 1 | 7 d | yes | none |
| paypal.com | none | no | no record | ||
| cnn.com | none | no | no record | ||
| github.com | none | no | no record | ||
| stripe.com | none | no | no record | ||
| yahoo.com | testing | 3 | 1 d | yes | testing mode |
| apple.com | none | no | no record | ||
| shopify.com | none | no | no record | ||
| proton.me | enforce | 2 | 7 d | yes | none |
6 of these 11 publish no MTA-STS at all, PayPal, Apple, GitHub and Shopify among them. gmail.com and google.com enforce with a one-day max_age, far shorter than the weeks RFC 8461 suggests; microsoft.com covers every Exchange Online server with a single wildcard, *.mail.protection.outlook.com. yahoo.com runs in testing mode, so a failed TLS check is reported but the mail still goes through.
MTA-STS Checker questions
What is the difference between MTA-STS testing and enforce mode?
In testing mode a sender that supports MTA-STS checks the connection (TLS offered, certificate valid for an MX host listed in the policy) and reports any failure through TLS-RPT, but delivers the message anyway. In enforce mode it refuses to deliver over a connection that fails, and keeps the message queued to retry until its own give-up time, after which it bounces. Run testing for two or three weeks with TLS-RPT reports going to a mailbox someone reads, fix whatever they show, then switch to enforce.
Why do I have to change the id in the _mta-sts TXT record?
Senders keep a copy of the policy for max_age seconds and look at the TXT record on each delivery. Only a new id tells them the file changed and should be fetched again (RFC 8461 3.1), so editing the policy without changing the id leaves senders on the old one until it expires. The id is 1 to 32 letters and digits with no set format; a timestamp is the usual choice, like gmail.com's 20190429T010101.
Why does my MTA-STS policy file fail to load?
Senders fetch it with strict rules. The host mta-sts.<domain> needs a publicly trusted certificate valid for that exact name, so a certificate for the main domain alone fails. Redirects are never followed, so the file must answer 200 at /.well-known/mta-sts.txt itself; an http to https or www hop breaks it. It must be served as text/plain. And mta-sts.<domain> needs its own A, AAAA or CNAME record, which is the step most often missed. Whatever the cause, senders with no cached policy then deliver as if the domain had none.
What is in a TLS-RPT report?
A JSON file (RFC 8460), usually one a day from each large sender such as Google or Microsoft, counting the TLS sessions it opened to your mail servers and how many succeeded. Failures are grouped by type: starttls-not-supported, certificate-expired, certificate-host-mismatch, certificate-not-trusted, sts-policy-fetch-error and sts-policy-invalid among them. Reports go to the rua= address in the TXT record at _smtp._tls.<domain>, a mailto: or https: URL. They are what make testing mode safe: you see what enforce mode would block before you turn it on.
More free domain tools
The DNS lookup shows every record a domain publishes. The MX lookup shows which servers take a domain's email and who runs them. The Nameserver lookup shows a domain's nameservers and which company hosts its DNS. The TXT record lookup reads a domain's SPF and DMARC records. The SPF record checker validates a domain's SPF record and counts its DNS lookups against the limit of 10. The DMARC checker reads a domain's DMARC policy, reports and alignment, and flags what weakens it. The DKIM checker finds a domain's DKIM keys among 22 common selectors and checks each key's size. The CNAME lookup follows a hostname's CNAME chain to its final address and spots dangling records. The DNS propagation checker shows whether 15 resolvers around the world return the same answer after a change. The reverse DNS lookup finds the hostname (PTR record) behind an IP address and checks that it resolves back. The BIMI checker checks a domain's BIMI record, SVG Tiny PS logo, mark certificate and whether DMARC lets the logo show. The email deliverability checker runs every DNS check that decides whether a domain's mail is trusted, with the failures first. For the website itself, the redirect checker follows a URL through every 301, 302, 307 and 308 to the page that answers, the HTTP header checker shows the response headers a URL sends and grades its six security headers and the website down checker checks from outside your network whether a site answers, and how fast. For who registered a name and when, use the WHOIS lookup, Domain age checker or Domain expiration checker. See which extensions a name is still free in with the domain availability checker, or price one in the domain value calculator.