SMTP TLS report reader
Summarize uncompressed SMTP TLS JSON reports and export policy/failure observations.
Your inputs
Your results
Ready when you areYour results will appear here.
How it works
Read RFC 8460 JSON transport reports locally, summarize each reported policy’s successful and failed sessions, and export policy and failure-detail tables. Zero denominators remain unavailable and inconsistent detail totals are identified.
Read the source reference ↗A few things to know
Does not probe SMTP, validate certificates, verify report authenticity or prove delivery. Uncompressed JSON only: 2 MB, 1,000 policies, 10,000 failure details; safe integer counts. Unknown result types are preserved, not interpreted as known failures.
When to use this tool
SMTP TLS reporting describes transport-session observations sent by a reporting organization. This reader turns supported JSON policy summaries and failure details into tables without probing a server or uploading the report. Successful and failed sessions are not delivered-message or inbox-placement counts. Each policy uses its own denominator for failure share, while zero totals remain unavailable. Failure-detail totals that disagree with summaries are flagged rather than silently rewritten. Operational hostnames and report text are displayed as text, and unfamiliar failure categories are retained for investigation.
- Read an uncompressed JSON TLS transport report locally.
- Compare reported policy session counts and failure shares.
- Export policy and failure-detail rows for investigation.
How to use smtp tls report reader
Supply a complete JSON report
Paste or upload uncompressed UTF-8 JSON with reporting organization, report ID, date range and policies. Decompress gzip before supplying it.
Inspect policy and count observations
Review success/failure sessions and the per-policy share. Counts must be nonnegative safe integers, and the date range must be ordered.
Check details against summaries
Download the policy and failure tables. Review mismatched detail totals and unfamiliar result types with the reporting context, rather than changing counts to make them agree.
A transport report with 5,629 sessions
Inputs
The fictional policy reports 5,326 successful sessions, 303 failed sessions and 303 certificate-expired failures.
Result
Failure share is approximately 5.3828% for that policy. Detail totals agree with its failed-session summary.
What it means
Those observations do not say how many messages reached a mailbox or how many recipients saw an email.
Common mistakes to avoid
Equating sessions with delivered messages
Transport sessions and message delivery are different measurements.
Treating a report as a certificate test
No server connection, certificate verification or policy installation occurs.
Discarding unfamiliar failure categories
The reader retains their reported text. Interpretation requires the source report and protocol context.
Frequently asked questions
Definitions, edge cases, and practical next steps for this tool. Search all tool FAQs ↗
Which reports does this accept?
Supported uncompressed RFC 8460-shaped JSON with organization-name, report-id, date-range, policy metadata and session summaries. It does not read DMARC XML or gzip.
What does failure share divide by?
Failed sessions divided by successful plus failed sessions for that policy. Counts from different policies are not substituted into its denominator.
What if a policy has zero sessions?
Its share is unavailable, not 0% or a passing result. The zero counts remain visible.
Can the counts be fractional or negative?
No. Nonnegative safe integers are required. Unsafe aggregate sums are rejected rather than losing exact count precision.
Are mismatched detail totals repaired?
No. They are flagged without changing the policy summary or reported detail counts. Investigate incomplete or overlapping observations with their reporting context.
What happens to unknown result types?
They are retained literally in the detail export. The reader does not invent an explanation or treat an unfamiliar label as a known certificate error.
Does it test SMTP or authenticate the report?
No. There are no SMTP connections, DNS changes, geolocation requests or authenticity guarantees. It only summarizes supplied JSON.
What limits apply?
One UTF-8 source below 2 MB, at most 1,000 policies and 10,000 failure-detail records. Decompress reports yourself before selecting the file.
Sources and method
Use the references below to check definitions and platform guidance. The model’s scope and limits are explained above. Read our editorial standards.