Skip to content
DMARC Pulse

MTA-STS and TLS-RPT check

MTA-STS Checker: test your MTA-STS policy and TLS-RPT

Enter a domain to validate its MTA-STS record and policy file, compare the policy with your real MX hosts and check the TLS-RPT reporting record.

We look up _mta-sts.<domain> and _smtp._tls.<domain>, then fetch the policy over HTTPS.

Example result

Sample data, not a live check. Run the tool above to see your own result.

Result for

acme.example

Looks good

mode=enforce v=TLSRPTv1

DNS records

_mta-sts.acme.exampleTXT
v=STSv1; id=20261101T000000
_smtp._tls.acme.exampleTXT
v=TLSRPTv1; rua=mailto:tls-reports@acme.example

Policy file

URL
https://mta-sts.acme.example/.well-known/mta-sts.txt
Version
STSv1
Mode
enforce
Cache time (max_age)
2592000 30 days
MX patterns
aspmx.l.google.com *.aspmx.l.google.com
1
aspmx.l.google.com
aspmx.l.google.com
5
alt1.aspmx.l.google.com
*.aspmx.l.google.com
10
alt2.aspmx.l.google.com
*.aspmx.l.google.com

What we found

  • MTA-STS record found (id 20261101T000000)

    The TXT record is valid. Change the id every time you change the policy file.

  • Valid policy in enforce mode

    Senders that implement MTA-STS won’t deliver to a server that fails the MX or certificate checks.

  • All 3 MX hosts match the policy

    Every MX record matches an mx pattern.

  • TLS-RPT record found

    Senders that support TLS-RPT send reports to the addresses in rua.

MTA-STS and TLS-RPT generator

Fill this in to get the TXT record, the policy file and where to host it, plus the TLS-RPT record. You publish them yourself.

List every server in your MX records, one per line. A wildcard covers exactly one label, as in *.yourprovider.com.

How long senders keep the policy. Start short and raise it once everything works.

A mailbox or https:// endpoint that receives the reports.

Why start in testing

In testing mode, senders that support TLS-RPT report TLS failures but can still deliver your mail, so a wrong host or an expired certificate doesn’t stop mail while you fix it. In enforce mode, senders that implement MTA-STS refuse to deliver to servers that fail these checks: mail waits in their queues until the problem is fixed, and can bounce. Stay in testing until your TLS-RPT reports show no failures.

What to do with the result

No MTA-STS record was found

If “MTA-STS lookup failed” appears, the DNS query timed out or the server returned an error such as SERVFAIL, so this result does not show whether the record exists. If it keeps failing after a new check, look at the domain's authoritative DNS servers. We keep each result for 15 minutes, so check again after that.

Otherwise, senders find no policy for your domain. Delivery continues as before, encrypted only when both servers can do it. To deploy MTA-STS, use the generator on this page in testing mode. Publish the policy file first and the TXT record second.

If the Policy file section appears, the file is online, but senders can only discover it through the record at _mta-sts.example.com. Before you publish that record, fix any error shown for the file and check its mode: with mode: enforce the record activates the policy, so use testing until TLS-RPT reports show no failures.

The TXT record or the policy file has an error

Senders act as if you had no policy when the TXT record is invalid or the file cannot be fetched. A sender holding an unexpired cached policy must still apply it (RFC 8461, sections 3.1 and 3.3).

  • Record: keep one v=STSv1 record at _mta-sts.example.com, with an id of 1 to 32 letters and digits.
  • File: open https://mta-sts.example.com/.well-known/mta-sts.txt. It must answer 200 with no redirect and a certificate valid for that name.
  • Fields: rebuild the file with the generator, upload it, then publish the new id.

Caution: a repaired file in mode: enforce applies as soon as senders fetch it. Stay in testing until TLS-RPT failure reports come back clean.

An MX host is not covered by the policy

The table shows a server from your MX records that matches no mx line. In enforce mode, senders that apply MTA-STS will not deliver to it. If no other host passes, mail waits in their queues and can bounce. In testing mode, they can still deliver.

  1. Confirm that the host really receives your mail. If it is a leftover from a migration, remove it from your MX records after confirming that the other hosts accept your domain.
  2. Otherwise add an mx line for it. *.example.com covers one label only, so a.b.example.com needs its own line.
  3. Upload the file first, then publish a new id.

The policy is valid in testing or none mode

In testing, senders may deliver even when a check fails. Those that support TLS-RPT report the failure, if you publish that record.

  1. Read the reports until they show no failures.
  2. Test each MX host, because senders may never reach a backup (RFC 8461, section 8.4). Run openssl s_client -brief -starttls smtp -connect mail.example.com:25 -verify_hostname mail.example.com and look for Verification: OK.
  3. Change the file to mode: enforce, then publish a new id. From then on, those senders refuse a host that fails.

In none, the domain has no active policy. To retire MTA-STS, keep the record and file online until every earlier max_age has passed (section 8.3).

The policy is valid in enforce mode

The record and file are valid, and your MX hosts match the policy. Senders that apply MTA-STS now refuse a host that fails the name check, offers no encryption or shows an invalid certificate. This tool compares host names only, so it cannot see the last two.

  • Set certificate expiry alerts on every MX host, backups included. An expired certificate can stop mail from those senders.
  • Before you change MX hosts, add the new ones to the file, publish a new id and wait for that TXT record’s TTL (how long resolvers may cache it). Keep the old hosts listed until the move ends (RFC 8461, section 8.1).

Explained

What MTA-STS does

SMTP encrypts mail between servers with STARTTLS only when both sides offer it, and an attacker on the network path can strip that offer or impersonate your server. MTA-STS (RFC 8461) lets your domain publish a policy that tells senders your mail servers support TLS and which hosts are legitimate. Senders that implement it check the policy before delivering to you.

It covers mail arriving at your domain. SPF, DKIM and DMARC answer a different question: who may send as your domain.

What an MTA-STS policy needs

  1. A TXT record at _mta-sts.yourdomain with v=STSv1; id=…. The id is 1 to 32 letters and digits and changes whenever the policy does.
  2. A policy file at https://mta-sts.yourdomain/.well-known/mta-sts.txt, served over HTTPS with a valid certificate, status 200 and no redirects.
  3. In that file: version: STSv1, a mode of testing, enforce or none, one mx line for each mail server, and max_age in seconds, up to 31557600.

How TLS-RPT fits in

TLS-RPT (RFC 8460) is a TXT record at _smtp._tls.yourdomain, such as v=TLSRPTv1; rua=mailto:tls-reports@yourdomain. Senders that support it send reports on TLS failures to that address, usually once a day. Those reports are how you know testing mode has found nothing to fix.

Frequently asked questions

What is MTA-STS?
MTA-STS (SMTP MTA Strict Transport Security, RFC 8461) lets a domain publish, over HTTPS, a policy requiring encrypted delivery to named mail servers. In enforce mode, senders that implement it won’t deliver to a server that fails the policy.
Where does the MTA-STS policy file go?
At https://mta-sts.yourdomain/.well-known/mta-sts.txt, served directly with status 200 and a certificate valid for mta-sts.yourdomain. Senders don’t follow redirects for this file.
Should I start in testing or enforce?
Start in testing with a TLS-RPT record published, and move to enforce when reports show no failures. In enforce mode, a wrong mx pattern or an expired certificate can delay or bounce mail from senders that implement MTA-STS.
What is TLS-RPT and do I need it?
TLS-RPT (RFC 8460) is a TXT record at _smtp._tls.yourdomain that tells senders where to report TLS failures. It’s optional, but without it testing mode gives you no feedback.
When do I change the id in the TXT record?
Every time the policy file changes. Update the file first and the TXT record second. Senders compare the id to notice a new policy, so an unchanged id can leave the old policy in their cache.

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.

Related tools