Runs locally in your browser

Email header analyzer

Paste a raw email header to inspect routing, authentication results and key metadata. Your header stays in your browser.

Parsed

What can email headers reveal?

Raw headers contain routing and authentication metadata added by mail systems as a message travels from sender to recipient. They can show Received hops, Authentication-Results, SPF, DKIM and DMARC outcomes, message IDs, dates and the apparent sender.

Privacy

This analyzer runs entirely in your browser. The pasted header is not sent to EmailValidly or stored by the service.

Put the result to work

Read a received message’s evidence in context

Headers contain metadata recorded as mail passes through servers. This local parser extracts selected fields and reported authentication outcomes. It does not independently verify signatures or establish that every header line is trustworthy.

  1. Copy the raw headers

    Use your mail client’s original-message or source view. The visible message text is not enough.

  2. Inspect the reported fields

    Review From, Date, Message-ID, hop count and available authentication results.

  3. Check who added the result

    Trust depends on your receiving system. An attacker can insert misleading headers earlier in the route.

Worked examples

What the evidence tells you

Illustrative scenarios, not live results for the addresses or records shown. Open a scenario to see the next action.

01Authentication-Results reports dkim=pass
Receiver-reported result

The parser displays a reported pass; it does not recompute the signature.

Next action Confirm the header belongs to your trusted receiver.

02No Authentication-Results found
Field unavailable

Missing output may mean the pasted header is incomplete or uses another format.

Next action Copy the full raw header.

03Several Received lines
Multiple recorded hops

The tool counts entries, not a verified network path or latency timeline.

Next action Read the source carefully before attributing an origin.

Use it with a purpose

Where this tool fits

Diagnosing a delivery complaint

Inspect actual authentication outcomes rather than relying only on DNS publication.

Reviewing a suspicious message

Compare the visible sender with metadata while avoiding links or attachments in the message itself.

Before you decide

Questions about this tool

Are my headers uploaded?

No. Parsing runs in your browser. Headers may contain personal data, so avoid sharing them publicly.

Is this a phishing verdict?

No. It is a metadata parser, not a complete security assessment.

Does the first reported pass settle authenticity?

No. The origin and trust boundary of the header matter.