An email header analyzer organizes pasted routing fields, address literals, dates and authentication declarations locally. It contacts no sender, link or DNS service and verifies no signature. Begin with a specific question about the supplied evidence.
How to use the email header analyzer
Open the original message’s full headers or source and preserve line breaks when pasting. Analyze headers parses that text. Ordinary forwarding can substitute the forwarding message’s headers for the original delivery record.
Read more
Gmail’s More menu offers Show original; see Google’s instructions. Outlook’s message-details or Internet-headers view varies by version; use Microsoft’s instructions. Sender-name screenshots are not full headers.
Load example supplies fictional reserved domains and documentation addresses. Its two relay times differ by eight seconds after conversion. A sample pass string is illustrative, not successful authentication verification.
Limits are 65,536 characters, 2,048 lines, 512 fields and one hundred Received records. Oversized input is rejected. The first empty line ends the header section; subsequent body content is omitted from analysis and exports.
Read the email header analyzer results
Field, hop and address counts describe inventory, not safety. Duplicate From or Subject fields remain visible. Parser notes and All original fields let you compare interpretations with the supplied source.
Read more
Email header analyzer route records
SMTP receivers usually prepend Received records. Reading bottom upward follows the listed sequence, so the tool reverses source order rather than sorting timestamps. RFC 5321 describes trace records.
Each hop links to its numbered source field and extracted from, by and with clauses. Parenthesized comments and quoted strings remain relevant parsing boundaries. Hostnames are readable hints, not verified router identities.
Pasted fields cannot establish who inserted a record. Compare trusted provider logs when the boundary matters; an earlier relay claim may originate outside your provider’s control.
Email header analyzer clock comparisons
Supported dates retain their supplied text and interpreted UTC value. Numeric offsets are applied: 11:00 +0100 and 10:00 +0000 represent the same instant.
Adjacent interpreted dates produce reported differences, not measured network RTT. Negative differences remain flagged rather than replaced with zero; clock disagreement or altered records may explain them.
Missing, impossible or ambiguous dates remain uninterpreted. Weekday mismatches and leap-second notation retain notes. Supported legacy zones and numeric offsets follow RFC 5322 conventions, without guessing a local zone.
Authentication assertions in the email header analyzer
Authentication-Results and ARC-Authentication-Results show claimed services and result clauses such as SPF, DKIM and DMARC. Every declaration is unverified: pass text does not become a green safety verdict.
RFC 8601 explains the trust arrangement around Authentication-Results. Pasted text cannot confirm its origin. SPF checks, DKIM signatures, DMARC alignment and ARC chains are not recalculated by this header-only parser.
Email header analyzer IP inventory
IPv4 and IPv6 literals are extracted from Received, Received-SPF and X-Originating-IP. Repeated addresses are grouped with source references. A Subject-only address is not treated as routing evidence.
A private address can describe an internal transfer. A public address can belong to a relay, gateway or hosting provider. Documentation addresses identify examples. None of these categories proves who wrote the message. The header analysis performs no geolocation lookup and makes no claim to locate a person or their device.
Email header analyzer message fields and subjects
Summary fields include sender, recipient, reply, return-path, subject, date and message identifiers. Their roles differ; a different reply address alone is not proof of fraud.
Supported MIME B and Q encoded Subject words receive readable previews. Originals remain available; malformed encoding, unsupported character sets and decoded controls retain source text with notes.
Markup is shown as text, not rendered HTML. Directional controls receive visible escapes. Full mailbox-address parsing and missing transfers remain outside scope.
Privacy and email header analyzer limitations
Headers can expose recipients, internal hosts and message identifiers. Working text stays in component memory without URL parameters, browser storage, API submission or tool analytics. Normal site requests remain separate.
Read more
Clear empties input and result; editing invalidates old analysis, and leaving discards working state. Cleanup does not guarantee memory erasure from the browser or operating system.
Copy report deliberately exports original header fields and parsed evidence, excluding body content after the separator. It is not automatically redacted. Review names and identifiers before sharing; Clear cannot retract clipboard copies.
This header analysis is an evidence reader, not a complete email standards validator or a phishing verdict service. It cannot inspect a mail provider's private logs, reconstruct missing transfers, establish the original SMTP connection or verify cryptographic signatures from a header-only paste. Hostnames and IP addresses remain unqueried until you independently choose another tool.