Generate a valid _smtp._tls TXT record (v=TLSRPTv1) with mailto and optional https report URIs so receiving MTAs can send you reports when STARTTLS to your MX fails. Free, client-side only.
_smtp._tls.<domain> (for example _smtp._tls.example.com).Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
SMTP TLS Reporting (RFC 8460) lets receiving domains publish a DNS record that tells sending mail servers where to send reports when a TLS session to the MX cannot be established or validated. Reports are JSON summaries, not full message content.
DMARC rua covers SPF/DKIM authentication and alignment failures for the From domain. TLS-RPT covers transport-layer TLS failures when delivering to your MX (certificate problems, STARTTLS not offered, policy mismatches). They solve different layers and both are useful.
As a TXT record on host _smtp._tls.<your-domain>. Example host: _smtp._tls.example.com. Only one TLSRPTv1 record should exist for the domain.
MTA-STS publishes a policy that requires TLS (and lists allowed MX hosts). TLS-RPT tells you when senders fail that policy or otherwise cannot complete STARTTLS. Deploy them together: generate an MTA-STS policy, then add TLS-RPT so you can see failures.
v=TLSRPTv1; rua=mailto:tlsrpt@example.com or with multiple destinations: v=TLSRPTv1; rua=mailto:tlsrpt@example.com,https://reporting.example.com/v1/tlsrpt
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.