Email and Cyber Security · #27

Online MTA-STS and TLS-RPT Checker

Reads the DNS records for MTA-STS and TLS-RPT and checks a pasted policy text against the MX targets.

  • Live DNS query (Cloudflare DNS over HTTPS)

Tool

Content of mta-sts.txt. If empty, the policy is marked as not verified.

The query goes directly from your browser to a fixed public resolver (Cloudflare 1.1.1.1, DNS over HTTPS); only the domain name and record type are sent. Eretek servers do not relay or log the query.

What does this tool do?

MTA-STS (RFC 8461) tells sending servers to deliver mail to your domain only over TLS with a valid certificate; TLS-RPT (RFC 8460) has TLS problems during delivery reported. The setup has two parts: TXT records in DNS and the policy file at https://mta-sts.domain/.well-known/mta-sts.txt.

The tool queries the DNS records live. It does not download the policy file itself, because that would mean Eretek sending a request to your server. If you open the file in your browser and paste its content, the MX match is checked.

How to use it

  1. Enter the domain.
  2. Optionally open https://mta-sts.<domain>/.well-known/mta-sts.txt in your own browser and paste its content into the policy field.
  3. Press Run.

Fields

Domain
MTA-STS policy text (optional)
Content of mta-sts.txt. If empty, the policy is marked as not verified.

Worked example

InputValue
Domaincontoso.com
MTA-STS policy text (optional)
version: STSv1
mode: enforce
mx: contoso-com.mail.protection.outlook.com
max_age: 604800

Expected result: _mta-sts TXT (id=20261116T090000) and _smtp._tls TXT exist; the policy is in enforce mode and covers the MX target.

The policy id must change whenever you edit the policy file; otherwise senders keep using the cached old policy for max_age. Run in testing mode for a few weeks and watch TLS-RPT reports before enforce.

Method and assumptions

v=STSv1 and id are expected in _mta-sts.domain TXT, v=TLSRPTv1 and rua (mailto: or https:) in _smtp._tls.domain TXT; each must be a single record.

In the pasted policy, version, mode (enforce/testing/none), max_age (at most 31,557,600 s) and mx lines are read. Each MX target must match an mx pattern (exact name or wildcard in the leftmost label).

Using the result and troubleshooting

If an MX target is missing from the policy, delivery to it fails in enforce mode; update the policy first, then change the id.

With Microsoft 365 you can use *.mail.protection.outlook.com as the mx line.

Limits and common mistakes

  • The policy file is not fetched; its HTTPS certificate and availability are not verified.
  • Whether senders have cached the policy is not visible.

Frequently asked questions

Why not fetch the policy file automatically?

This tool does not send requests from Eretek servers to targets entered by users. When you open the file in your browser, the request goes from your connection and stays under your control.

Related tools and service

  • MX Record LookupShows which servers receive mail for a domain, in which order, and their addresses.
  • DMARC Record CheckerReads the _dmarc record and interprets its policy, reporting and alignment settings.

Related service: Email Security and Phishing Protection

Cybersecurity online tools · See all online tools