Email header analyzer

Read mail routes, timestamps and authentication claims with private, local analysis.

Paste email headers

0 / 65,536

Up to 65,536 characters. Text after the first blank line is ignored.

Analyze headers locally in this tab. Pasted content is not sent to a lookup service.

Ready for local analysis.

Header analysis

No headers analyzed yet

Paste full email headers above and choose Analyze headers to see the result.

What we will show

Sending path
Recorded authentication
Header trust boundary
Key details

Read the route, then inspect the claims

  1. Paste original headers

    Preserve field folding and exclude the message body.

  2. Parse fields and hops

    Keep source references and bottom-up Received order.

  3. Compare reported clocks

    Show supported UTC dates and retain negative differences.

  4. Review authentication claims

    Inspect reporting services without treating pass text as verification.

The diagram explains a header-only analysis. Relay order and authentication declarations remain supplied evidence, not independently verified delivery facts.
On this page

Learn more about Email header analyzer

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.

Email header analyzer questions

Can an email header analyzer find the sender’s IP?

An email header analyzer can identify address literals in supported routing fields. It cannot prove that one belongs to the human sender. Webmail may expose provider infrastructure, relays may hide earlier hops, and untrusted fields may be fabricated. Use the source-field references to understand where an address appeared, then ask the relevant provider for evidence if identity is important.

Why does the email header analyzer show no Received records?

Your copied text may be incomplete, may begin with an empty line, or may contain only a message summary. The email header analyzer does not invent missing records. Return to the original-message view and copy the actual headers. If the records truly are absent, that absence is the result; it does not establish a direct delivery path.

Why does a successful authentication assertion still say unverified?

The email header analyzer did not run the asserted check. Even a correctly formatted Authentication-Results field needs a trusted origin before its claims can be relied upon. Keep the authentication-service identifier and original message with any support request. Do not interpret a displayed success as proof that attachments, links or payment instructions are safe.

Can I analyze an exported message or a forwarded conversation?

Paste its header section into the header analysis, within the stated limits. A full message body is ignored after the first blank line, but nested messages and attachments are not recursively inspected. A forwarded conversation's outer headers describe that forwarding event. Obtain the original message as a separate source when you need its own delivery history.

What should I do after finding a suspicious difference?

Use the header analysis to prepare a focused question: identify the numbered field, preserve its original value, and state what conflicts with your expectation. If you administer the receiving domain, compare the message with delivery logs and authentication results from your own systems. If you are a recipient, contact your mail provider through its usual support channel rather than replying to an untrusted address in the message.

The header analysis was developed against the linked standards and synthetic examples covering folding, duplicate fields, comments, date boundaries, encoded subjects and deceptive authentication text. Those checks validate parsing behavior; they do not certify arbitrary email as authentic. Source review date: September 28, 2026.

Should I paste the whole email body?

Use the original header block needed for your question. Message bodies, attachments and unrelated conversation text add personal information without establishing an additional mail-routing hop. Review any copied report before sharing addresses, message identifiers or internal hostnames.

Why can the hop timestamps appear out of order?

Received fields contain declarations made along a delivery path. Clock differences, time zones, omitted fields and untrusted additions can complicate ordering. A negative apparent interval deserves inspection of the raw fields; it is not by itself proof of tampering or a measured network delay.