Free tool · 04 / SEND
MTA-STS checker.Record, policy, MX coverage and TLS reporting, no signup.
Checks a domain's MTA-STS record, policy file, MX coverage and TLS reporting.
We look this up and don't keep it.
Try: · ·
An example: a made-up domain in testing mode whose policy misses one MX host.
yourcompany.example: MTA-STS testing, 1 problem.
Record at _mta-sts
v=STSv1; id=20261101T090000
Policy file
version: STSv1 mode: testing mx: *.mailhost.example max_age: 604800
MX hosts
mx1.mailhost.example, mx2.mailhost.example, backup.othermail.example
TLS reporting at _smtp._tls
v=TLSRPTv1; rua=mailto:tls-reports@yourcompany.example
- Record found, id=20261101T090000. Change the id whenever you change the policy, so senders fetch it again.
- Mode testing: senders report failures (if you publish TLS reporting) but still deliver. Google suggests about two weeks in testing before you enforce.
- max_age 604800: senders may cache the policy for 7 days.
- Not covered by the policy's mx patterns: backup.othermail.example. With enforce, senders won't deliver to it.
- TLS reports go to mailto:tls-reports@yourcompany.example.
Valley sends from your own Gmail or Microsoft inbox, so your domain's mail setup is the one that counts. See how Valley does it ↗
NEXT STEP
Fed up with securing inboxes nobody writes back from.The other half is who, and what you say.
Book a demo ↗$500 a month for your first seat, $200 for each seat after that.
The policy
What goes in an MTA-STS policy?The fields RFC 8461 defines, and their rules.
An MTA-STS policy is a text file at https://mta-sts.yourdomain/.well-known/mta-sts.txt with four fields: version (STSv1), mode (enforce, testing or none), one or more mx patterns naming your mail servers, and max_age, how long senders may cache it, up to 31557600 seconds.
| Field or record | What it holds | Rule |
|---|---|---|
| _mta-sts TXT | v=STSv1; id=… | id: 1 to 32 letters and digits; change it when the policy changes |
| version | STSv1 | Required, once |
| mode | enforce, testing or none | Required, once |
| mx | Your MX host names; *.example.com matches one label | At least one, unless mode is none |
| max_age | Seconds senders may cache the policy | Required, at most 31557600 |
| Policy host | https://mta-sts.yourdomain | A valid certificate for mta-sts; senders don't follow redirects |
| _smtp._tls TXT | v=TLSRPTv1; rua=mailto:… | Reports by mailto: or https: |
From RFC 8461: SMTP MTA Strict Transport Security (MTA-STS) ↗ · RFC 8460: SMTP TLS Reporting ↗, read 17 Nov 2026
How it works
How this tool works.And what it can't see.
Type a domain. Our server reads its _mta-sts and _smtp._tls TXT records and its MX hosts, and fetches the policy from https://mta-sts.yourdomain/.well-known/mta-sts.txt, the way a sending server must: over HTTPS with a valid certificate, and without following redirects. We don't keep the domain or what we fetched.
The checks follow RFC 8461 and RFC 8460: the record's format and id, the policy's version, mode, max_age and mx patterns, whether every MX host matches a pattern (a wildcard covers exactly one label), and whether TLS reports have somewhere to go.
What it can't see: whether each MX server actually offers STARTTLS with a certificate matching its name. That needs a connection on port 25, which our servers can't open.
Built by Valley.
Sources
- RFC 8461: SMTP MTA Strict Transport Security (MTA-STS) ↗read 17 Nov 2026
- RFC 8460: SMTP TLS Reporting ↗read 17 Nov 2026
- Google Workspace Admin Help: About MTA-STS and TLS reporting ↗read 17 Nov 2026
MTA-STS
Make senders encrypt mail to you.Record, policy, testing, then enforce.
MTA-STS tells sending servers to use encrypted, authenticated connections when they deliver to you. Here's how the parts fit.
- 01
Three parts, all required
RFC 8461 needs a TXT record at _mta-sts starting v=STSv1 with an id, and a policy file at https://mta-sts.yourdomain/.well-known/mta-sts.txt, served as text/plain from a host with a valid certificate for the mta-sts name. Senders must not follow redirects to find it.
From RFC 8461: SMTP MTA Strict Transport Security (MTA-STS) ↗, read 17 Nov 2026
- 02
mx patterns are strict
RFC 8461's own example: the pattern *.example.com matches mail.example.com, but not example.com or foo.bar.example.com. A wildcard covers exactly one label, so an MX host two labels deep needs its own pattern, or it's not covered.
From RFC 8461: SMTP MTA Strict Transport Security (MTA-STS) ↗, read 17 Nov 2026
- 03
Test first, with reporting on
Google suggests starting with testing mode for about two weeks before enforcing, and asks for a max_age between 86400 (one day) and 31557600. Publish a TLS reporting record at _smtp._tls (v=TLSRPTv1 with a mailto: or https: rua) so you hear about failures before they block mail.
From Google Workspace Admin Help: About MTA-STS and TLS reporting ↗ · RFC 8460: SMTP TLS Reporting ↗, read 17 Nov 2026
- 04
Gmail follows it
Google says Gmail messages from your domain comply with MTA-STS when sent to external servers with a policy in enforced mode.
Encrypted delivery protects the mail. What's in it, and who it goes to, decides whether anyone replies. See how Valley does it ↗
From Google Workspace Admin Help: About MTA-STS and TLS reporting ↗, read 17 Nov 2026
Questions
Questions people ask.
- What is MTA-STS?
- A standard (RFC 8461) that tells sending mail servers to deliver to your domain only over encrypted connections, to servers with valid certificates.
- How do I check MTA-STS?
- Type your domain here. You'll see the _mta-sts record, the policy file, whether each MX host matches it, and your TLS reporting record.
- Where does the MTA-STS policy file go?
- At https://mta-sts.yourdomain/.well-known/mta-sts.txt, served as text/plain from a host with a valid certificate.
- What is the difference between MTA-STS testing and enforce?
- In testing, senders report failures but still deliver; in enforce, senders that support MTA-STS won't deliver if the connection fails the policy.
- What is the maximum max_age for MTA-STS?
- 31557600 seconds, about a year, per RFC 8461. Google's guide asks for at least 86400, one day.
- What is TLS-RPT?
- SMTP TLS Reporting (RFC 8460): a TXT record at _smtp._tls telling senders where to report TLS failures, by mailto: or https:.
- Does Gmail support MTA-STS?
- Yes. Google says Gmail complies with MTA-STS when sending to external servers whose policy is in enforced mode.
- Is this MTA-STS checker free?
- Yes. It's free and needs no signup. We look up the domain you type and don't keep it.
Keep going
Try one of these next.
- SPF, DKIM and DMARC checkerEmail outreachChecks a domain's SPF, DKIM and DMARC records against Gmail and Yahoo's sender rules.Open the tool
- MX lookupEmail outreachShows a domain's MX records and who handles its email, for one domain or 500 at once.Open the tool
- DNS lookupEmail outreachEvery common DNS record for a domain, from Cloudflare and Google side by side.Open the tool
- DMARC report readerEmail outreachReads a DMARC aggregate report: who sends as your domain, and why each one fails.Open the tool
- Cold email domain finderEmail outreachSending domain ideas close to your brand, each checked against its registry.Open the tool