MTA-STS checker
Check whether a domain tells other mail servers to insist on encrypted delivery, and whether its policy file is right.
Results for lookupowl.com
MTA-STS: Not set up
lookupowl.com has no MTA-STS policy.
Mail can still arrive, but a sender can't be told to insist on TLS. This is a recommendation, not a fault.
- none
- testing
- enforce
How to set it up
- Serve a text file at
https://mta-sts.lookupowl.com/.well-known/mta-sts.txt, starting in testing mode:Addversion: STSv1 mode: testing mx: *.mx.cloudflare.net max_age: 86400 - Publish the record:Add
_mta-sts.lookupowl.com. 300 IN TXT "v=STSv1; id=20261116T000000;" - Add TLS reporting so you hear about problems, then move to enforce.
Structured result (JSON) · 1.7 KB
{
"domain": "lookupowl.com",
"asOf": "2026-11-16T19:45:32.721Z",
"verdict": "none",
"txt": {
"name": "_mta-sts.lookupowl.com",
"present": false,
"viaCname": null,
"records": [],
"version": null,
"id": null,
"idLooksLikeDate": null,
"issues": []
},
"policy": null,
"mxMatch": [
{
"host": "route1.mx.cloudflare.net",
"priority": 51,
"matched": false,
"by": null,
"cert": {
"checked": false,
"valid": null,
"starttls": null,
"tlsVersion": null,
"nameMatches": null
}
},
{
"host": "route3.mx.cloudflare.net",
"priority": 76,
"matched": false,
"by": null,
"cert": {
"checked": false,
"valid": null,
"starttls": null,
"tlsVersion": null,
"nameMatches": null
}
},
{
"host": "route2.mx.cloudflare.net",
"priority": 77,
"matched": false,
"by": null,
"cert": {
"checked": false,
"valid": null,
"starttls": null,
"tlsVersion": null,
"nameMatches": null
}
}
],
"extraPatterns": [],
"noMail": false,
"certificates": "not-checked-yet",
"tlsRpt": {
"present": false,
"rua": []
},
"readiness": {
"toEnforce": "not-yet",
"steps": [
{
"id": "record",
"ok": false
},
{
"id": "file",
"ok": false
},
{
"id": "mx",
"ok": null
},
{
"id": "certificates",
"ok": null
},
{
"id": "reports",
"ok": false
}
]
},
"notChecked": [],
"issues": []
}More in Email · Records and policies
Next step
- TLS-RPT checkerWhere do delivery failure reports go?Check lookupowl.com in TLS-RPT checker
- Email health checkThe whole mail setup in one reportCheck lookupowl.com in Email health check
- SSL checkerIs the certificate on the policy host valid?Open in SSL checker
What MTA-STS does
Email between servers is encrypted when both sides agree to it, and a network attacker can make them disagree. Server A asks for encryption, the attacker strips the request, and the message travels in the clear. MTA-STS (RFC 8461) closes that gap. A domain publishes a promise: mail to me must use TLS, and it must go to these servers.
The promise has two halves that must agree. A short DNS record at _mta-sts.example.com says a policy exists and gives it an id. The policy itself is a small text file served over HTTPS at https://mta-sts.example.com/.well-known/mta-sts.txt. Most people have never seen that file, so this page shows it, line by line.
MTA-STS only protects mail from senders that support it. The big mailbox providers do, so it covers a large share of the mail you receive, but it is not a promise about every sender.
What this checker reads
Type a domain, or an email address and we use only the part after the @. We never store the address. Then we do these things, in this order.
- Read the TXT record at
_mta-sts.<domain>. It must be one record that starts withv=STSv1and has anidof up to 32 letters and digits. A CNAME to another domain is allowed, and we say where it leads. - Fetch the policy file from
mta-sts.<domain>over HTTPS. RFC 8461 forbids following a redirect, so a redirect counts as a failure. The file must answer 200, be served astext/plain, stay under 64 KB and come with a certificate that is valid for that name. - Read the file line by line:
version,mode, one or moremxlines andmax_age. Each line gets a mark and one plain sentence, and a line we cannot read is shown exactly as it is. - Look up the domain's MX records and match each mail server against the
mxpatterns, wildcards included. We show which line matched each server, and which patterns match nothing. - Look for a TLS reporting record, because without reports you will not hear about delivery problems when you move to enforce.
Testing mode and enforce mode
The mode line has three values. In none the policy is switched off. In testing, senders report problems but still deliver the message, so a mistake costs you nothing but a report. In enforce, a sender that cannot reach a listed server over valid TLS holds the message back or sends it back.
Start in testing. When the report shows no failures for a week or two, change the mode to enforce and change the id in DNS so senders fetch the new file. When a domain is in testing mode, this page shows the steps left before you can move on.
The rules a policy file has to follow
| Line | Rule | Example |
|---|---|---|
version | Must be STSv1. It is the only version. | version: STSv1 |
mode | One of none, testing or enforce. | mode: testing |
mx | A mail server name, or *. and a name for every server one level below it. Add one line per pattern. | mx: *.mail.example.com |
max_age | How long senders keep the policy, in seconds, up to 31557600 (about a year). One day or more is usual. | max_age: 86400 |
A wildcard stands for exactly one label. *.example.com matches mx1.example.com but not a.mx1.example.com and not example.com itself. Names are compared without regard to upper and lower case.
Problems we find most often
- The record exists but
mta-sts.<domain>does not resolve, or answers 404. Senders that cannot fetch the policy ignore MTA-STS, so nothing is blocked, but the protection is not there. - A mail server in your MX records matches no
mxline. In enforce mode senders refuse to deliver to it, so this is the most serious row on the page. - The file redirects to another address, usually from a hosting service or a www prefix. Serve it directly at the fixed address.
- The file is served as
text/html, often by a static site host. Senders may ignore it. - More than one MTA-STS record at
_mta-sts. Senders then treat the domain as having no policy at all. - A policy in enforce mode and no TLS-RPT record. You would fail silently, because nothing tells you about the rejected mail. Use the TLS-RPT checker next.
What this checker cannot see yet
A full MTA-STS check also connects to each mail server on port 25 and looks at its certificate: does it start TLS, is the name on the certificate one of your mx patterns, has it expired. We do not make that connection yet, so the certificate cells read "Not checked yet". That is not a fail. Before you move to enforce, check each server yourself, for example with the SSL checker, which can test STARTTLS on port 25.
Nobody can see from outside whether a sender fetched your policy or used it. Only your own reports can tell you that. For the other parts of mail trust, see the SPF checker, the DMARC checker and the DKIM checker.
Questions people ask
What is the difference between testing and enforce?
In testing mode senders report problems but still deliver the message. In enforce mode they refuse to deliver when TLS fails or the mail server is not on your list. Run in testing first, watch the reports, then switch.
Why does the record have an id?
The id changes whenever the policy file changes. Senders cache the policy for max_age seconds and only fetch it again when they see a different id. An id made from the date and time, such as 20261115T000000, is easy to keep fresh.
Do I need TLS-RPT as well?
You can run MTA-STS without it, but you should not. TLS-RPT is how senders tell you that a delivery failed. Without it, enforce mode fails silently. Check the record with the TLS-RPT checker.
What does a wildcard in an mx line match?
One label, and only at the front. *.example.com matches mail.example.com. It does not match example.com, and it does not match a.mail.example.com. If your servers sit at different depths, add one line for each pattern.
Why must the policy file not redirect?
RFC 8461 says senders must not follow redirects when they fetch the policy. A redirect would give whoever controls the target a way to rewrite your policy. Serve the file straight from mta-sts.<your domain>.
Does MTA-STS replace DANE?
No. Both protect against downgrade attacks, in different ways. DANE needs DNSSEC and publishes certificate facts in DNS. MTA-STS needs a web server and a normal certificate. Some domains run both. We do not check DANE yet.
Does this checker store the email address I type?
No. If you type an address, only the part after the @ is used. It is cut before the lookup, it is not stored, and the result address carries only the domain.
Use it from AI, the API or the command line
Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is mta_sts_check. Please be kind to the rate limits.
curl "https://lookupowl.com/api/v1/tools/mta-sts-check?q=gmail.com"claude mcp add --transport http lookupowl https://lookupowl.com/mcp