TLS-RPT Record Checker
Check the TLS-RPT record that tells sending mail servers where to send reports about TLS failures. The tool reads the TXT record at _smtp._tls.<domain>, checks that it starts with v=TLSRPTv1, exists only once and lists valid mailto: or https: destinations in rua, as defined in RFC 8460.
Frequently asked questions
What is TLS-RPT?
SMTP TLS Reporting (RFC 8460) lets a domain ask sending mail servers for daily reports about the TLS connections they made to its MX hosts, including failures caused by MTA-STS or DANE policies. It does not change delivery, it only gives you visibility.
What does a valid record look like?
For example v=TLSRPTv1; rua=mailto:tlsrpt@example.com published as TXT at _smtp._tls.example.com. The version must come first, and rua lists one or more destinations separated by commas.
Which destinations are allowed?
mailto: addresses, which receive the reports as gzip compressed JSON attachments, and https: URLs, which receive them as HTTP POST requests. Other schemes are not defined and are reported as invalid.
Do I need TLS-RPT without MTA-STS?
It is most useful together with MTA-STS or DANE, because the reports show policy failures before you switch to enforce. On its own it still shows whether senders can negotiate TLS with your servers.
Who sends TLS reports?
Large providers such as Google and Microsoft send them once a day for domains that publish a record. Smaller servers often do not, so missing reports do not mean nobody delivers mail to you.
Why does the tool warn about an unknown tag?
RFC 8460 defines only v and rua. Other tags are ignored by senders, so they do no harm, but they often point to a typo such as ruf, which belongs to DMARC.