Topic · Transport Security

TLS-RPT

SMTP TLS Reporting allows domains to receive aggregate reports about TLS delivery successes and failures.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

A _smtp._tls TXT record advertises a reporting destination for JSON reports.

02 / What can go wrong

What can go wrong

Reports are diagnostic and do not themselves require TLS encryption. Report delivery depends on sender support and functioning collectors.

03 / What to check or do

What to check or do

Review certificate, policy and DNS failures and correlate them with MTA-STS changes.

Practical scenario

Practical scenario

The transport report shows a spike in certificate-hostname failures on a secondary MX. Ordinary mailbox testing might miss it because the primary MX continues to accept mail. TLS-RPT helps pinpoint failures that happen only under certain failover paths.

Verification checklist

  1. Parse the JSON report and verify its date range.
  2. Group error categories by reporting organization and receiving MX host.
  3. Correlate spikes with certificate deployment or MTA-STS policy changes.
  4. Use multiple senders’ evidence before calling an issue globally resolved.
Practical diagnosis

How to investigate TLS-RPT

Signal to investigate
Reports show failures for a destination despite successful manual SMTP tests.
Evidence to collect
Group JSON policy and failure records by receiver, MX host and result type.
Common wrong conclusion
TLS-RPT measures attempts by reporting senders, not an exhaustive global delivery count.

How to interpret the evidence

TLS-RPT provides aggregated observations from senders implementing reporting. Its JSON can describe the policy seen, success counts and specific failure categories. It is especially useful when only some destinations or secondary mail exchangers fail, because one successful manual probe may miss a path used by other senders.

What to change and how to verify it

Parse the JSON with report date ranges intact and group by reporter, MX and failure reason. Correlate changes with certificates, TLS policies and DNS updates. Do not treat a single reporter's data as a complete delivery census, and confirm fixes across several reporting cycles.

Illustrative diagnostic — substitute your authorized domain or host
dig +short TXT _smtp._tls.example.com
Educational example; not validated against your live infrastructure.
Illustrative example — do not copy directly to production
_smtp._tls.example.com TXT "v=TLSRPTv1; rua=mailto:[email protected]"
NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.

Authoritative reference ↗