TLS Reporting (TLS-RPT)
Why TLS-RPT Matters
TLS-RPT complements MTA-STS by providing feedback about TLS connection issues in email delivery. Without TLS-RPT, you would not know if sending servers are experiencing TLS failures when connecting to your mail servers, potentially causing email delivery problems.
The reports reveal certificate issues (expired, untrusted, wrong hostname), TLS configuration problems, and MTA-STS policy failures. This data helps you detect and fix email security issues before they cause widespread delivery failures. It is especially valuable when transitioning MTA-STS from testing to enforce mode.
TLS-RPT is straightforward to deploy - a single DNS TXT record specifying where to send reports. The reports are JSON formatted and can be processed by DMARC/email security reporting services. Like DMARC aggregate reports, they provide passive monitoring without affecting email delivery.
Checking Your Setup
A DNS health checker verifies the _smtp._tls TXT record for TLS-RPT configuration. The record format is: v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com. Reports are sent by participating email providers.