Primary use
TLS-RPT lookup
Fetch the live SMTP TLS reporting record instead of assuming report visibility is configured correctly.
Free TLS reporting checker
Free TLS reporting checker and TLS-RPT lookup
Run a free TLS reporting checker to validate the live TLS-RPT DNS record for any domain, confirm report destinations, and review warnings before transport-security changes. Use it alongside MTA-STS when SMTP TLS visibility matters.
Run a free lookup
Check the live TLS-RPT record for a domain
Enter the root domain. This checker validates the live TLS reporting TXT record, shows aggregate-report destinations, and surfaces warnings worth reviewing before the next transport change.
Best fit
Use this when transport reporting needs a quick health check
TLS-RPT lookups are most useful after DNS changes, during MTA-STS rollout, and during security reviews when teams need to confirm report visibility before they trust the transport telemetry path.
- Validate report destinations after DNS updates
- Pair report visibility checks with MTA-STS rollout
- Give security and messaging teams one shared transport-report view
Upgrade path
Connect transport visibility to sender-domain operations
TLS-RPT is more valuable when transport checks sit beside MX, SPF, DKIM, and DMARC reviews in a repeatable sender-domain workflow.
- Review transport reporting and auth posture together
- Keep DNS and reporting drift visible across launch windows
- Shorten incident diagnosis when mail security posture changes
Key details
Critical tag
rua destinations
Confirm where aggregate transport reports are meant to arrive before relying on them operationally.
Operational fit
Transport review
Use it with MTA-STS when transport policy and report visibility change together.
Output
Record + issues
Review the live TXT value, report endpoints, and any warnings in one troubleshooting view.
When to use this tool
See the live TLS-RPT record
Confirm the public record instead of relying on an intended DNS change that may not be visible yet.
Verify report routes
Check whether the rua destination still points at the mailbox or workflow expected to receive transport reports.
Support transport rollout
Use TLS-RPT alongside MTA-STS so teams have both policy and visibility as transport posture changes.
What this returns
A TLS reporting checker should answer visibility questions quickly
The value is not just whether a TXT record exists. It is whether the live record looks valid, whether report destinations are still correct, and whether the team can trust the transport-reporting path.
Record
Live TXT value
Review the exact TLS-RPT record visible in public DNS.
Reports
rua destinations
Confirm the aggregate report endpoints before relying on transport telemetry.
Warnings
Review notes
Catch malformed or weak setup details before transport reviews depend on them.
Workflow
MTA-STS pair
Use this with transport policy checks so discovery and visibility are reviewed together.
Operational use
Best used after DNS changes and during transport-security reviews
Searchers usually need TLS-RPT lookup because report visibility matters right now, not as a generic reference. Treat it as an operating step in transport and domain-health review.
After DNS edits
Re-run the lookup after changing TXT records so the team knows the correct report endpoints are publicly visible.
With MTA-STS rollout
Validate the reporting path alongside transport policy so security and messaging owners can see failures as the rollout progresses.
During transport review
Give the team one shared view of whether SMTP TLS reporting is still configured the way the operating model expects.
Related tools
TLS reporting record generator
Generate a clean TLS-RPT record when the current one needs to be rebuilt.
Open toolMTA-STS checker
Validate transport policy discovery and hosting alongside TLS-RPT visibility.
Open toolMX lookup
Review routing and transport-reporting posture together when mail infrastructure changes.
Open toolDomain monitor
Pair TLS-RPT checks with broader sender-domain health before production launches.
Open toolFAQ
What does a TLS reporting checker validate?
A TLS reporting checker validates the RFC 8460 TLS-RPT DNS record so you can confirm the version tag and report destinations used for SMTP TLS failure reporting.
Why use TLS-RPT if it does not enforce TLS by itself?
TLS-RPT adds visibility. It helps teams see when SMTP TLS delivery problems are happening so they can correct certificate, policy, or transport issues before they become recurring outages.
When should teams run a TLS reporting lookup?
Run it after DNS changes, alongside MTA-STS rollout, and whenever report visibility is part of the transport-security operating model.
What if the record is valid but no reports arrive?
That usually means the rua destination is not being monitored correctly, the mailbox route is broken, or transport issues are not occurring frequently enough to produce reports yet.