MTA-STS and TLS-RPT Checker

Check whether a domain enforces encrypted mail delivery with MTA-STS.

Email security Live check from this server, against public hosts only.

About the MTA-STS and TLS-RPT Checker

By default, mail servers encrypt connections with STARTTLS only opportunistically, so an attacker in the path can strip encryption. MTA-STS (RFC 8461) lets a domain publish that its mail servers support TLS with valid certificates, and that senders must refuse to deliver otherwise.

The checker reads the _mta-sts TXT record, downloads the policy from https://mta-sts.<domain>/.well-known/mta-sts.txt, validates mode, MX patterns and max_age, compares the patterns with the actual MX records, and checks the TLS-RPT reporting record (RFC 8460).

How to use it

  1. Enter the domain that receives the mail.
  2. Run the check.
  3. Review the record, the policy and whether the MX hosts match it.

Frequently asked questions

What is the difference between testing and enforce mode?

In testing mode, senders deliver even if TLS fails but report the failure through TLS-RPT. In enforce mode they refuse delivery to servers without valid TLS. Start with testing, watch the reports, then switch to enforce.

Why is MTA-STS needed if I already use STARTTLS?

STARTTLS alone can be downgraded: an attacker can remove the STARTTLS offer and senders fall back to plain text. MTA-STS tells senders in advance that TLS is mandatory and which servers are valid.

What is TLS-RPT?

TLS Reporting (RFC 8460) is a TXT record at _smtp._tls.<domain> with an address where sending servers report failed TLS connections. It shows problems before they cost you mail.

All free tools