Inspect the header, not the message body
Make the technical details readable
Paste the original header text. Analysis runs locally only when you choose Analyze headers.
Up to 128 KiB, 2,000 lines and 500 fields, including at most 128 Received and 32 combined authentication-result fields. Each value is limited to 8,192 UTF-16 units, counting retained folding whitespace and line breaks. The first empty line ends the headers; content after it is not analyzed.
Ready for a header you want to understand.
A readable declaration, not a verdict
Results describe the text supplied. SPF, DKIM and DMARC outcomes are reported declarations, not new checks of DNS or signatures.
Headers can contain addresses, subjects, IPs and internal server names. No history, saving, copy button or export is provided here.
Hiding or leaving this page clears its input and results and stops local work. This is not a promise to erase every browser-memory copy or protect a compromised device, extension or replacement interface.
Read each source separately
Follow the recorded evidence
Analyze a header to separate addresses, recorded authentication results and the Received declarations into a readable report.
No messages are sent and no destination is visited.
Message and address declarations
Recorded authentication results
Each entry remains separate. Neither its position nor its service name proves it is trusted.
Received fields: earlier declarations first
Reversed source order, not sorted timestamps. Differences compare adjacent declared dates, not independently measured queue time.
DKIM signature metadata
Domain, selector and algorithm as written; signatures and message bodies are not verified.
Keep the trust boundary in view
Anyone able to edit a copied header can change its contents. Use the original message in your receiving mailbox and provider records when investigating a real incident.
A different Reply-To, a missing result or a negative timestamp difference is a clue to review, not proof of fraud or delivery failure.