Skip to main content
Email100% FreeInstant

Email Header Analyzer: Trace Where an Email Came From

This free email header analyzer reads the raw headers of a message and shows the route it took, the delay at each hop and the SPF, DKIM and DMARC results. Your headers are processed in your browser and never uploaded.

By Debmedia Technologies LLP · Kolkata, India · Updated

What Is an Email Header Analyzer?

An email header analyzer reads the hidden technical headers of a message and shows the path it took from the sender to you. Every server that handles an email adds a Received line, so the headers form a trail. They also carry the results of the SPF, DKIM and DMARC checks that prove whether the sender is genuine.

This email header analyzer turns the wall of text into a clear table of hops and a list of checks. Use it to investigate spam, phishing, delivery delays or a message that looks suspicious.

How to Use This Email Header Analyzer

  1. Open the message and copy its full headers. In Gmail choose Show original, and in Outlook open the message properties.
  2. Paste the text into the box above.
  3. Press Analyze headers.
  4. Read the checks first, then the route table and the key headers.

What the Analysis Shows

SectionWhat it tells you
Authentication checksWhether SPF, DKIM and DMARC passed, failed or were missing.
Consistency checksWarnings when From, Return-Path and Reply-To use different domains.
Route tableEach server the message passed, with its address, protocol, time and delay.
Key headersFrom, To, Subject, Date, Message-ID and other important fields.

The message format itself is described in RFC 5322, the email message format.

Warning Signs in Headers

  • SPF or DKIM fails. The server that sent the mail was not allowed to, or the message was altered.
  • DMARC fails. The visible From address does not line up with the authenticated domain, a classic sign of spoofing.
  • Different Reply-To domain. Replies would go somewhere other than the shown sender.
  • Long delays. Gaps of many minutes between hops suggest queues or greylisting.
  • Unexpected origin. An address from a country or provider that does not match the claimed sender.

How Much to Trust the Headers

A sender can invent any header at the start of the chain. Only the lines added by servers you trust, such as your own mail provider, are reliable. Read the route from the bottom up and rely most on the hops closest to you.

Investigate Further

Look up the public addresses in the route with the IP owner lookup, find their hostnames with the reverse DNS tool and check the sending domain with the domain address finder. Your headers are analysed in your browser and never uploaded.

Tips for Better Results

Paste the complete headers, not only the first lines. Missing lines can hide authentication results.

Frequently Asked Questions

In Gmail open the message, choose the three-dot menu and pick Show original. In Outlook open Properties or View message source. Copy everything above the message body.
Each server adds a Received line at the top, so the newest hop is first in the raw text. The tool reverses them, so hop 1 is the one closest to the sender.
They give strong clues. Failed SPF, DKIM and DMARC checks and a mismatch between From and Return-Path are warning signs, but only the first hops added by your own provider can be fully trusted.
Yes. The analysis runs in your browser and nothing is sent to our server. Headers can contain addresses, so avoid sharing them publicly.

Disclaimer: results come from live requests and can change as records and servers change. We cannot guarantee that every answer matches what every visitor sees.