# Email Header Analyzer

Paste the full headers of an email to see where it really came from and how it travelled: sender, recipient, subject and message ID, the SPF, DKIM and DMARC results the receiving server recorded, the DKIM signatures, and every server hop in order with its time and the delay between hops. Warnings point out failed authentication and mismatched Reply-To and Return-Path domains.

## Frequently asked questions

### How do I get the headers of an email?

In Gmail, open the message, choose More and Show original. In Outlook, open the message and choose File, Properties, or View, Message source on the web. In Apple Mail, choose View, Message, All Headers. Copy everything from the first line down to the message text, or the whole source, and paste it here.

### What does the analyzer show?

The main fields such as From, To, Subject, Date and Message-ID, the authentication results recorded by the receiving server for SPF, DKIM, DMARC and others, the domains and selectors of DKIM signatures and a table of every server the message passed, oldest first, with timestamps and the delay at each step.

### How is the route read?

Each server adds a Received header at the top, so the analyzer reads them from the bottom up. The first row is the server where the message started, the last row the server that delivered it to the mailbox. Delays between rows show where a message waited.

### How can I tell whether an email is spoofed?

Look at the authentication results: a dmarc=fail or a spf or dkim failure means the message could not prove that it comes from the domain in From. A Reply-To on an unrelated domain and a first hop from an unexpected server are further signs. The analyzer warns about all of these.

### What does a negative delay mean?

That one server's clock was behind another's. Times in Received headers come from each server's own clock, so small differences are normal. The analyzer warns when a step goes back more than a minute.

### Are the message body and attachments needed?

No. Only the header block is analyzed; everything after the first empty line is ignored. You can paste the full source if that is easier.

### Which authentication result is used?

The topmost Authentication-Results header, which the server that delivered the message to your mailbox added. Lower ones were added on the way and can be forged by the sender. If there is none, a Received-SPF header is used for SPF.

### Are encoded subjects decoded?

Yes. Subjects and names written as MIME encoded words, such as =?UTF-8?B?...?=, are decoded so that accents and other scripts appear as text.

### Why is my Return-Path different from the From address?

Newsletters and many services send with their own bounce address in Return-Path, which is normal. It matters for DMARC only when neither SPF nor DKIM aligns with the From domain, which is why the analyzer mentions it as a note, not an error.

### Are the headers stored?

No. They are analyzed for this request only, and the result does not echo the pasted text.

Your ad here?

[Email us](mailto:hi@dennn.is?subject=Advertising%20on%20OneClick%20Pro)

[Ad 433 tools for your AI agents through one MCP server.](https://multitaskai.com/?ref=oneclickpro)
