Markdown

TLS-RPT

TLS-RPT is the Acronym for SMTP TLS Reporting

An email reporting standard that tells sending servers where to report problems with encrypted delivery to a domain. The domain publishes a TXT record at _smtp._tls, such as v=TLSRPTv1; rua=mailto:tls-reports@example.com, and senders including Google and Microsoft send a daily JSON report of successful and failed TLS sessions, with the reason for each failure. It is defined in RFC 8460.

Why TLS-RPT Matters

When a sender cannot negotiate TLS with a domain’s MX hosts, the failure is normally visible only in the sender’s logs. TLS-RPT surfaces expired or mismatched certificates, missing STARTTLS support, and policy errors to the receiving domain. Because it only reports and never changes delivery, it is safe to publish before any enforcement.

What TLS-RPT Reports Include

  • Policy: The MTA-STS or DANE policy the sender applied, or a note that none was found.
  • Summary: Total successful and failed sessions for the day.
  • Failure details: Result types such as certificate-expired, starttls-not-supported, or sts-policy-fetch-error, with the MX host, IP address, and session count.

Related Standards

TLS-RPT is the reporting companion to MTA-STS and DANE, and it is what makes an MTA-STS testing period useful. Build the record and check any domain with the TLS-RPT Builder.

Articles Tagged TLS-RPT

View Additional Articles Tagged TLS-RPT