TLS-RPT JSON Report Analyzer
Analyze a real TLS reporting JSON file locally; distinguish reports from a live SMTP probe.
Run a diagnostic
Accepted: TLS-RPT JSON (.json) or gzip-compressed JSON (.json.gz). XML is not accepted.
Report files remain in your browser; no reports are uploaded by these workflows.
Email headers stay in your browser. Public DNS results may be cached for 5 minutes. Public DNS TXT checks may use Google Public DNS when the server resolver returns no TXT records. Email headers are not sent to that DNS service.
How to interpret this result
Analyze a real TLS reporting JSON file locally; distinguish reports from a live SMTP probe.
No. Only an actual report from a sending organization provides evidence of observed TLS sessions.
No sample results are used for your scan.
Evidence this tool can evaluate
Import SMTP TLS reporting JSON to inspect reported connection successes, failures, MX hosts and reporting intervals. Detail-level counts are checked for invalid values and inconsistent totals.
What to do with the findings
Group failures by MX host and failure category, compare against MTA-STS and certificate configuration, and confirm findings with fresh SMTP tests. Reports describe observations, not guaranteed delivery.
Need continuous authentication protection?
Method and limitations
Interpret RFC 8460 TLS reports, failure categories, policy domains and reporting time windows. Public DNS checks cannot prove inbox delivery or message-level authentication.
Frequently asked questions
Does a published TLS-RPT DNS record mean reports were received?
No. Only an actual report from a sending organization provides evidence of observed TLS sessions.
Educational diagnostics, not a guarantee of deliverability or provider approval.