MTA-STS checker
This free MTA-STS checker looks up a domain's MTA-STS TXT record at _mta-sts and fetches its policy file from https://mta-sts.<domain>/.well-known/mta-sts.txt, then checks both against the MTA-STS rules. Use it to confirm your setup before you switch a policy from testing to enforce.
Inputs are sent to our server to run this check. They are not included in usage analytics.
Your result
Add your inputs, or try the example, to see your result here.
A policy check cannot test every sender's TLS negotiation.
Sending cold email from this domain? Terlido checks SPF, DKIM, DMARC and MX for every mailbox you connect, and warms it up for free. Connect a mailbox, free
How Terlido handles this
Stop checking by hand. Terlido watches every mailbox you send from.
Domain score on connect
SPF, DKIM, DMARC and MX checked the day you connect a mailbox, then daily.
Free warmup, forever
Every mailbox warms up on every plan, at no cost.
Campaigns in the same place
Contacts, sequences and replies sit next to the mailbox checks.
No card, at any point.
How to use this tool
- Reads _mta-sts.domain and the HTTPS policy at mta-sts.domain.
What the result tells you
- A policy check cannot test every sender's TLS negotiation.
What is MTA-STS?
MTA-STS (Mail Transfer Agent Strict Transport Security, RFC 8461) lets a domain tell other mail servers that it only accepts email over an encrypted TLS connection to approved mail servers. Without it, an attacker on the network path can try to downgrade the connection to plain text or redirect mail to another server.
MTA-STS protects mail coming in to your domain. It has two parts that must agree: a DNS TXT record that announces a policy exists, and a policy file served over HTTPS.
The two parts this MTA-STS checker reads
The DNS record lives at _mta-sts.yourdomain.com and carries a policy id:
_mta-sts.example.com TXT "v=STSv1; id=20261031" https://mta-sts.example.com/.well-known/mta-sts.txt version: STSv1 mode: enforce mx: mail.example.com mx: *.example.net max_age: 604800
What the checker tests
A valid setup returns "MTA-STS DNS record found." and a pass such as "Policy fetched: mode enforce, max_age 604800s, 2 MX patterns." A domain without the record returns "No matching DNS record found."
- DNS: whether a TXT record starting with v=STSv1 exists at _mta-sts.<domain>. More than one such record is a failure, because senders cannot tell which one counts.
- Policy id: the record must be v=STSv1 followed by exactly one id of 1 to 32 letters or digits.
- Policy file: version must be STSv1, mode must be enforce, testing or none, and max_age must be a whole number of seconds from 0 to 31557600 (about one year). Each key except mx must appear exactly once.
- MX patterns: enforce and testing need at least one mx line. A pattern may start with *. for one wildcard label, like *.example.net, and must be a valid host name.
- Content type: the policy file should be served as text/plain. Anything else is flagged as a warning.
How to set up MTA-STS step by step
- Create the subdomain mta-sts.yourdomain.com with a valid HTTPS certificate.
- Serve the policy file at /.well-known/mta-sts.txt with every MX host you use, in mode: testing first.
- Publish the _mta-sts TXT record with v=STSv1 and a new id.
- Add a TLS-RPT record so other servers send you reports about TLS failures. The TLS-RPT record generator builds it.
- When the reports show no failures, change the mode to enforce and change the id in DNS, so senders fetch the new policy.
Limits of this check
The checker reads the published record and policy. It cannot test how every sending server negotiates TLS with your mail servers, and it does not check that your MX hosts present valid certificates. TLS-RPT reports show those results from real senders.
Frequently asked questions
Is this MTA-STS checker free?
Yes. It is free and needs no account.
Why does the checker say the policy could not be confirmed?
The policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt did not return a valid policy. Check that the subdomain has a valid certificate, the path is exact, the file returns HTTP 200 and every required line is present once.
Should I use testing or enforce mode?
Start with testing and a TLS-RPT record, so failures are reported but mail still arrives. Switch to enforce when the reports are clean.
Do I need to change the id when I change the policy?
Yes. Senders cache the policy for max_age seconds and only fetch it again when the id in the DNS record changes.
What is a good max_age?
Many domains use 604800 seconds (one week) or longer once the policy is stable. The checker accepts any whole number up to 31557600 seconds.
Does MTA-STS help my emails reach the inbox?
No. MTA-STS protects mail sent to your domain from being read or redirected in transit. Inbox placement for mail you send depends on SPF, DKIM, DMARC and your sending behavior.
Useful next steps
Free tools from our sister products
Connect a mailbox.
Your domain's score lands today.
It costs nothing and doesn't depend on anyone else being on the platform. Warmup runs free on every plan, forever.
Start freeFix it once. Terlido keeps watching.
Start free