trustyourinbox

Free MTA-STS validator. Read down to your MX.

Enter your domain. We read the MTA-STS record, fetch the policy file over HTTPS, match its mx lines against your live MX records, and look for a TLS-RPT record.

kanbello.xyzEnforced 100
kanbello.xyz, shown as an exampleversion: STSv1 mode: enforce mx: aspmx.l.google.com mx: *.aspmx.l.google.com max_age: 604800
mode: enforceEnforce modeServers that honor the policy refuse a connection that fails its TLS checks.Enforcing
max_age: 6048007 daysHow long servers keep the policy before fetching it again.Long enough
3 MX hostsYour mail serversEach one matched by an mx: line.3 of 3 covered

What we read. And what we leave alone.

Two records from public DNS, the policy file over HTTPS, and your MX records to compare it with.

Read

The records _mta-sts and _smtp._tls

The TXT record that starts v=STSv1 and carries the policy's id. Then the TLS-RPT record, which asks sending servers to report the connections that fail.

Fetched

The policy file mta-sts.yourdomain.com/.well-known/mta-sts.txt

Fetched over HTTPS with no redirects, as RFC 8461 requires. We read its mode, its max_age and every mx: line, and match each of your live MX hosts against them.

Not tested

Your servers' TLS STARTTLS on port 25

We do not connect to your mail servers, so we cannot see whether each one offers TLS with a valid certificate for its name. In enforce mode, a sending server refuses one that does not.

Questions. Short answers.

What the checks, the score and the words on this page mean.

Isn't MTA-STS just a DNS record?

No. The DNS record only says a policy exists. The policy is a file served over HTTPS at mta-sts.yourdomain.com/.well-known/mta-sts.txt, and a sending server needs both.

Testing or enforce?

In testing, a sending server that finds a problem still sends the mail, and reports it if you publish TLS-RPT. In enforce, it refuses the connection. Read the reports in testing, then switch. MTA-STS and TLS-RPT.

What does MX coverage mean?

Every server in your MX records has to match an mx: line, by its full name or by a wildcard such as *.example.com, which covers one label. In enforce mode, a sending server will not use an MX host no line matches.

What does the score mean?

Enforce mode with every MX host covered scores 100. A short max_age, or MX that could not be compared, 75. Testing mode 60. A record without its file, or a file without its record, 35. Mode none, an invalid policy, or an MX host left out in enforce mode, 25. No policy, no score.

Do you keep my result?

No. We count that the tool ran and which kind of result it gave, so we can see what people run into. The domain, the records and the policy are not kept.

How many checks can I run?

Ten an hour from one network. The limit keeps the tool fast for everyone.