Senderward

TLS-RPT reports explained

Updated

TLS-RPT (SMTP TLS Reporting, RFC 8460) is the receiving side's counterpart to DMARC reports. Servers that deliver mail to your domain send you a daily JSON report on how many connections to your MX servers used TLS successfully, and why the others failed. It matters most when you use MTA-STS or DANE, because then a TLS failure means mail is not delivered.

Why you want it

Mail between servers is encrypted with STARTTLS, but by default a sender falls back to plain text when TLS fails, and nobody notices. With MTA-STS in enforce mode (or DANE), the sender refuses to deliver instead. Either way, you only find out that a certificate expired or an MX host changed if someone tells you. TLS-RPT is how they tell you.

Setting it up

One TXT record at _smtp._tls under your domain:

_smtp._tls.example.com  TXT  "v=TLSRPTv1; rua=mailto:[email protected]"

Use a mailbox or report service that can take a daily gzip attachment per sending organisation. Reports often arrive even when nothing failed, because they also count successful sessions.

What a report looks like

The email subject has the form Report Domain: example.com Submitter: example.net Report-ID: <...>, with a .json.gz attachment (media type application/tlsrpt+gzip). A report normally covers one UTC day. Shortened:

{
  "organization-name": "Example Net",
  "date-range": {"start-datetime": "2026-11-14T00:00:00Z",
                 "end-datetime": "2026-11-14T23:59:59Z"},
  "contact-info": "[email protected]",
  "report-id": "2026-11-14T00:00:00Z_example.com",
  "policies": [{
    "policy": {
      "policy-type": "sts",
      "policy-string": ["version: STSv1", "mode: enforce",
                        "mx: mx1.example.com", "max_age: 86400"],
      "policy-domain": "example.com"
    },
    "summary": {"total-successful-session-count": 5326,
                "total-failure-session-count": 12},
    "failure-details": [{
      "result-type": "certificate-expired",
      "sending-mta-ip": "198.51.100.7",
      "receiving-mx-hostname": "mx1.example.com",
      "receiving-ip": "203.0.113.10",
      "failed-session-count": 12
    }]
  }]
}

What the failure types mean

result-typeMeaningUsual fix
starttls-not-supportedThe MX did not offer STARTTLS.Enable TLS on the MX, or look for a firewall or proxy that strips STARTTLS.
certificate-host-mismatchThe certificate does not cover the MX hostname.Use a certificate with the MX name, or point MX at the name your provider's certificate covers.
certificate-expiredThe certificate on the MX has expired.Renew it, and automate renewal.
certificate-not-trustedSelf-signed, or the chain is incomplete.Use a certificate from a public CA and serve the full chain.
validation-failureSome other validation error.Read additional-information or failure-reason-code in the report, if given.
sts-policy-fetch-errorThe sender could not fetch https://mta-sts.example.com/.well-known/mta-sts.txt.Check DNS for mta-sts., the web server and its HTTPS certificate.
sts-policy-invalidThe policy file has a syntax error.Fix the file: version, mode, mx and max_age lines.
sts-webpki-invalidThe certificate of the policy host is not valid.Fix the certificate on mta-sts.example.com.
tlsa-invalid, dnssec-invalid, dane-requiredDANE: the TLSA record does not match, DNSSEC validation failed, or DANE was required but could not be used.Update TLSA records before changing a certificate or key, and check DNSSEC.

How to read the numbers

Check your domain

Free TLS-RPT check by Lookproof. Opens on lookproof.dev.

Senderward checks your domain's DMARC, SPF, DKIM, MX, MTA-STS and TLS-RPT every day and emails you, with the fix, when something gets worse. $7 per domain per month, 14 days free. See pricing

Sources