TLS-RPT (SMTP TLS Reporting) is a DNS-published setting that tells other mail servers where to send daily JSON reports about encrypted delivery to your domain, including certificate errors, expired certificates and policy mismatches.
Why it matters
Encrypted mail transport can fail silently: the sender may fall back to plain text or defer the message, and you would not know. With MTA-STS in enforce mode, failures mean rejected or delayed mail, so reports are the safety net that shows what senders actually experience. They are also useful alone, to find a certificate that expired on a secondary mail server.
Example
Record:
_smtp._tls.example.com. IN TXT "v=TLSRPTv1; rua=mailto:tls-reports@example.com"
A report is a compressed JSON file containing the policy that applied, counts such as total-successful-session-count and total-failure-session-count, and failure types like certificate-expired or starttls-not-supported, along with the sending and receiving MX hosts.
Common mistakes
- Publishing TLS-RPT but never reading the reports.
- Confusing it with DMARC reports; they cover transport encryption, not sender authentication.
- Pointing reports at an address on a different domain without the proper setup, so they are dropped.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.