TLS-RPT record
Learn what a TLS-RPT record is, how the _smtp._tls TXT names a report destination, and what rua= mailto and https addresses do.
TL;DR
A TLS-RPT record tells senders where to send reports about TLS failures on mail to your domain. It is one TXT record at _smtp._tls. It does not turn TLS on. MTA-STS and DANE do that. TLS-RPT only collects the failures.
_smtp._tls.{domain}_smtp._tls.example.com. TXT "v=TLSRPTv1; rua=mailto:tls-reports@example.com"Senders that support TLS reporting aggregate failures for this domain and post them to every URI in rua=. The reports cover MTA-STS and SMTP DANE, which is why the record sits next to those policies and not on the MX hostname.
| Tag | Required | Meaning |
|---|---|---|
v=TLSRPTv1 | Yes | Must be first. |
rua= | Yes | Comma-separated mailto: or https: destinations. |
_smtp._tls.example.com. TXT "v=TLSRPTv1; rua=mailto:tls-reports@example.com,https://example.com/tls-reports"The TLS-RPT checker looks for v=TLSRPTv1 at that name and flags a record that has no rua=. It does not receive or parse the report files themselves.
A mailto: destination is the usual choice. An https: destination has to accept a POST of the report. An address on another domain may need that domain to publish an authorization record before some senders will deliver there, the same idea as DMARC rua= on an outside domain.
dig _smtp._tls.example.com TXTEnter _smtp._tls.example.com in the lookup above.
Related: MTA-STS Record · DANE Record · DMARC Record · TXT Record · TLS-RPT Checker