TLS-RPT: reports about failed encrypted deliveries

A one-line record that makes senders tell you when they could not deliver mail to you securely.

SMTP TLS Reporting (TLS-RPT, RFC 8460) asks sending servers to report back when they had trouble setting up an encrypted connection to your mail servers. Without it, failed or insecure deliveries happen silently. It's one TXT record:

_smtp._tls.example.com.  TXT  "v=TLSRPTv1; rua=mailto:tls-reports@example.com"

Senders that support it, including Google and Microsoft, send a daily JSON report listing successful and failed TLS sessions to your domain, with the reason for each failure.

What the reports catch

  • An expired or wrong certificate on one of your mail servers.
  • MTA-STS problems: a policy that can't be fetched, or an MX host missing from it. Essential while MTA-STS is in testing mode.
  • DANE validation failures, if you publish TLSA records.
  • Downgrade attempts, where STARTTLS wasn't offered on a connection that should have had it.

Good to know

  • Only one TLS-RPT record per domain. With two, senders ignore both.
  • Several report addresses go in one rua=, separated by commas. https:// endpoints are allowed too.
  • The record is harmless: it changes nothing about how mail is delivered. There's no reason not to publish it.
  • Reports only arrive when senders actually deliver to you, so a domain that receives little mail gets few reports.