Free tool
MTA-STS tells other mail servers that your domain accepts mail only over verified TLS, so a message to you cannot be quietly downgraded to plain text or routed to a fake server. This free MTA-STS checker tests both halves of the setup: the _mta-sts TXT record and the policy file it points to.
Want TLS-RPT, BIMI and DMARC checked in the same pass? Run the domain scanner.
DNS Record
Finds the v=STSv1 TXT record at _mta-sts.yourdomain.com and reads its id
Policy File
Checks the policy file at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt
Recommendations
Lists what to fix next, marked critical, warning or info
Step 1
Type the domain that receives your mail, such as yourdomain.com. A pasted https:// prefix or trailing slash is stripped for you.
Step 2
Click Check MTA-STS or press Enter. The checker looks up the TXT record at _mta-sts.yourdomain.com and the policy file it points to.
Step 3
DNS Record shows the raw v=STSv1 record and its policy id. Policy File shows the URL senders fetch, with a link to open it.
Step 4
Work through Issues Found, Warnings and Recommendations, then click New Check once your DNS change has propagated.
Finds the TXT record that contains v=STSv1, shows it as published and reads the id. A missing id is an error, and an id outside 1 to 32 characters is a warning.
Checks the policy at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt over HTTPS and reads its version, mode, mx and max_age lines. The result links to the file so you can open it yourself.
Recommendations marked critical, warning or info, from a missing record or policy to adding TLS-RPT. The checker does not look up TLS-RPT or validate DNSSEC itself.
A sending server that supports MTA-STS first looks up a TXT record to learn that your domain has a policy, then downloads the policy over HTTPS. Both have to be in place, and the policy has to match your real MX records.
A TXT record at _mta-sts. It holds the version and an id of 1 to 32 letters and digits. A timestamp works well as the id.
Host: _mta-sts.yourdomain.com Type: TXT Value: v=STSv1; id=20261027T120000;
A plain text file served at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt. This example is for a Google Workspace domain:
version: STSv1 mode: testing mx: aspmx.l.google.com mx: *.aspmx.l.google.com max_age: 86400
| Field | What it does |
|---|---|
| version | Always STSv1. |
| mode | testing, enforce or none. See the rollout below. |
| mx | One line per MX host. A wildcard covers one label only: *.aspmx.l.google.com matches alt1.aspmx.l.google.com but not aspmx.l.google.com, so list both. Microsoft 365 domains use *.mail.protection.outlook.com. |
| max_age | How long senders cache the policy, in seconds, up to 31557600 (about a year). |
Senders still deliver when TLS or the certificate fails, and report the failure through TLS-RPT. Start here.
Senders refuse to deliver to an MX host that fails TLS validation or is not listed in the policy.
Tells senders to drop any cached policy. Use it to switch MTA-STS off without breaking delivery.
TLS-RPT (RFC 8460) is a TXT record that asks sending servers to email you a daily JSON summary of successful and failed TLS sessions to your domain. Google and Microsoft both send them. Without it, testing mode tells you nothing.
Host: _smtp._tls.yourdomain.com Type: TXT Value: v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com
This checker does not read the TLS-RPT record. The domain scanner does, alongside MTA-STS, DMARC and BIMI.
| Error | Why it happens | Fix |
|---|---|---|
| Policy host has no valid HTTPS certificate | Senders only accept a policy served with a publicly trusted certificate that covers mta-sts.yourdomain.com. A certificate for the apex or www, a self-signed one or an expired one fails. | Issue a certificate for mta-sts.yourdomain.com from your host or a public CA and serve the full chain. |
| Wrong content type | The policy must be served as text/plain. Some hosts send text/html or application/octet-stream for files in .well-known. | Set Content-Type: text/plain for /.well-known/mta-sts.txt. |
| mx lines do not match MX records | In enforce mode senders refuse any MX host that no mx line matches. Common after a mail provider change, or when a wildcard is expected to cover the bare host. | Compare dig +short MX yourdomain.com with the mx lines and add one for every host. |
| id not changed after a policy edit | Senders keep the cached policy for max_age seconds and only fetch it again when the id changes. | Change the id in the _mta-sts TXT record every time you edit the policy file. |
| Redirects or a broken CNAME | Senders do not follow HTTP redirects, so a 301 to www or another path fails. A CNAME on mta-sts to a hosting provider is fine only if that host serves your certificate and the file. | Serve the file directly with a 200. If a provider hosts it, check their certificate covers mta-sts.yourdomain.com. |
| More than one v=STSv1 record | If _mta-sts returns two records that start with v=STSv1, senders treat the domain as having no policy. | Keep exactly one MTA-STS TXT record. |
A policy fetch error means a sender found your TXT record but could not download a valid policy. Repeat the sender's steps from a terminal:
dig +short TXT _mta-sts.yourdomain.com
curl -sv https://mta-sts.yourdomain.com/.well-known/mta-sts.txt
dig +short MX yourdomain.com
FAQ
MTA-STS (Mail Transfer Agent Strict Transport Security, RFC 8461) lets a domain tell sending mail servers that its MX hosts support TLS and that mail should only be delivered over a verified, encrypted connection. It protects mail coming in to your domain from downgrade and interception attacks, where an attacker strips STARTTLS or points the sender at a fake server.
Enter the domain in the checker above and click Check MTA-STS. It looks up the TXT record at _mta-sts.yourdomain.com and links to the policy file at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt. To test by hand, run dig +short TXT _mta-sts.yourdomain.com, then curl -sv https://mta-sts.yourdomain.com/.well-known/mta-sts.txt and confirm a 200 response, a valid certificate and a body that starts with version: STSv1.
It is a plain text file with one key: value pair per line. A working example: version: STSv1, mode: testing, mx: aspmx.l.google.com, mx: *.aspmx.l.google.com, max_age: 86400, each on its own line. version, mode and max_age appear once; add one mx line for every MX host or wildcard pattern your domain uses.
In testing mode, senders that support MTA-STS still deliver mail when TLS or the certificate fails, but report the failure through TLS-RPT. In enforce mode they refuse to deliver to an MX host that fails validation or is not listed in the policy. None tells senders to drop any cached policy, and is how you switch MTA-STS off safely.
max_age is how long, in seconds, senders cache your policy. The maximum is 31557600 (about a year). Use a short value such as 86400 (one day) while in testing mode so mistakes expire quickly, then raise it to one or two weeks (604800 or 1209600) or longer once the policy is in enforce mode and stable.
It is not required, but without it you cannot see what testing mode is telling you. TLS-RPT is a TXT record at _smtp._tls.yourdomain.com, for example v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com. Providers such as Google and Microsoft then send a daily JSON report of successful and failed TLS sessions to that address. Publish it before or alongside your MTA-STS policy.
Fetch the policy the way a sender does: curl -sv https://mta-sts.yourdomain.com/.well-known/mta-sts.txt. The certificate must be valid for mta-sts.yourdomain.com, the response must be a 200 with no redirect, the Content-Type must be text/plain, and the body must start with version: STSv1. TLS-RPT reports name the failure type, for example sts-policy-fetch-error, sts-policy-invalid or sts-webpki-invalid, which tells you which of those checks failed.
Senders cache the policy for max_age seconds and only fetch it again when the id in the _mta-sts TXT record changes. Every time you edit the policy file, change the id too, for example to a new timestamp such as 20261027T120000. The id can be 1 to 32 letters and digits.
Not directly. MTA-STS secures mail that other servers send to your domain, so it does not change inbox placement for the cold email you send out. For outbound placement, SPF, DKIM and DMARC on the sending domain, warmed-up mailboxes and low bounce and complaint rates matter far more. MTA-STS is worth adding to the domains where you receive replies.
Inboxkit sets up SPF, DKIM and DMARC automatically and watches blacklists and DNS on every sending domain.