# MTA-STS checker

> Checks a domain's MTA-STS record, policy file, MX coverage and TLS reporting. Free, no signup. We look this up and don't keep it.

**MTA-STS checker. Record, policy, MX coverage and TLS reporting, no signup.** Use it at https://tools.joinvalley.co/mta-sts-checker

## 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: |

Sources: [RFC 8461: SMTP MTA Strict Transport Security (MTA-STS)](https://www.rfc-editor.org/rfc/rfc8461) (read 2026-11-17), [RFC 8460: SMTP TLS Reporting](https://www.rfc-editor.org/rfc/rfc8460) (read 2026-11-17)

## How it works

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.

## 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.

### 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.

Sources: [RFC 8461: SMTP MTA Strict Transport Security (MTA-STS)](https://www.rfc-editor.org/rfc/rfc8461) (read 2026-11-17)

### 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.

Sources: [RFC 8461: SMTP MTA Strict Transport Security (MTA-STS)](https://www.rfc-editor.org/rfc/rfc8461) (read 2026-11-17)

### 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.

Sources: [Google Workspace Admin Help: About MTA-STS and TLS reporting](https://knowledge.workspace.google.com/admin/security/about-mta-sts-and-tls-reporting) (read 2026-11-17), [RFC 8460: SMTP TLS Reporting](https://www.rfc-editor.org/rfc/rfc8460) (read 2026-11-17)

### 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. [Valley](https://www.joinvalley.co/?utm_source=tools_suite)

Sources: [Google Workspace Admin Help: About MTA-STS and TLS reporting](https://knowledge.workspace.google.com/admin/security/about-mta-sts-and-tls-reporting) (read 2026-11-17)

## Sources

- [RFC 8461: SMTP MTA Strict Transport Security (MTA-STS)](https://www.rfc-editor.org/rfc/rfc8461) (read 2026-11-17)
- [RFC 8460: SMTP TLS Reporting](https://www.rfc-editor.org/rfc/rfc8460) (read 2026-11-17)
- [Google Workspace Admin Help: About MTA-STS and TLS reporting](https://knowledge.workspace.google.com/admin/security/about-mta-sts-and-tls-reporting) (read 2026-11-17)

## 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.

## Related tools

- [SPF, DKIM and DMARC checker](https://tools.joinvalley.co/spf-dkim-dmarc-checker): Checks a domain's SPF, DKIM and DMARC records against Gmail and Yahoo's sender rules.
- [MX lookup](https://tools.joinvalley.co/mx-lookup): Shows a domain's MX records and who handles its email, for one domain or 500 at once.
- [DNS lookup](https://tools.joinvalley.co/dns-lookup): Every common DNS record for a domain, from Cloudflare and Google side by side.
- [DMARC report reader](https://tools.joinvalley.co/dmarc-report-reader): Reads a DMARC aggregate report: who sends as your domain, and why each one fails.
- [Cold email domain finder](https://tools.joinvalley.co/cold-email-domain-finder): Sending domain ideas close to your brand, each checked against its registry.

## Next step

Want replies, not just clean copy? Valley finds buyers showing real buying signals and messages them across email and LinkedIn. [Valley](https://www.joinvalley.co/?utm_source=tools_suite)

Shelf: [04 Email outreach](https://tools.joinvalley.co/email-outreach)

---

Tools by Valley, made by [Valley](https://www.joinvalley.co/?utm_source=tools_suite). HTML version: https://tools.joinvalley.co/mta-sts-checker
