Knowledge base
MTA-STS and TLS-RPT
Make sure mail to your domain is delivered encrypted, and get told when it is not.
Mail between servers is usually encrypted with STARTTLS, but by default encryption is optional. An attacker who can interfere with the connection can strip it and read mail in transit. MTA-STS and TLS-RPT close that gap for mail sent to your domain.
MTA-STS
MTA-STS (Mail Transfer Agent Strict Transport Security) lets you tell senders: only deliver to these mail servers, and only over TLS with a valid certificate. It has two parts:
- A TXT record at
_mta-sts.example.com:v=STSv1; id=20261116. Change theidwhenever the policy changes. - A policy file served over HTTPS at
https://mta-sts.example.com/.well-known/mta-sts.txt:
version: STSv1
mode: enforce
mx: mail.example.com
max_age: 604800
Start with mode: testing, which reports problems without blocking delivery, then move to enforce. The HTTPS host needs a valid certificate, which is the fiddly part; hosted MTA-STS handles it for you.
TLS-RPT
TLS-RPT (SMTP TLS Reporting) asks senders to report daily on TLS connections to your mail servers, including failures such as expired certificates or a mismatched MX. It is a TXT record:
_smtp._tls.example.com TXT "v=TLSRPTv1; rua=mailto:tls-reports@example.com"
Use it with MTA-STS: reports tell you whether enforcing would break anything before you switch to enforce, and warn you afterwards if something changes.
See it on your own domain.
Check your DMARC, SPF and DKIM setup in seconds, then let us watch your reports for you.
Start free