● 100% free · no sign-up

Inboxlogy Free Tools

Email Header Analyzer

Paste the raw headers of any email and instantly see its SPF, DKIM and DMARC results, the full relay path, and every sender detail. 100% in your browser — nothing is uploaded.

In Gmail: ⋮ → "Show original". In Outlook: File → Properties → Internet headers. Nothing is uploaded — parsing happens in your browser.

How it works

  1. Copy the raw headers

    In Gmail open the message menu and choose Show original. In Outlook open message properties and copy the internet headers. Take everything from the first Received line down to the Subject.

  2. Paste them in

    Parsing happens in your browser, so nothing leaves your machine. The tool splits folded header lines, orders the relay hops, and pulls out authentication results, timestamps and sender identifiers.

  3. Read the chain

    You see the full path with per-hop delays, the SPF, DKIM and DMARC verdicts the receiver recorded, and whether the signing domain actually matches the From domain a recipient sees.

How to read Received headers and Authentication-Results

Received headers stack newest at the top, so read from the bottom up to follow the message in order. Each hop records the connecting host, the HELO name it claimed, its IP, the server that accepted it and a timestamp. Only hops written by servers you trust are reliable; anything added before your boundary MTA can be forged. Timestamps show where a message sat.

Authentication-Results is written by the receiving domain and is the authoritative verdict. It records spf=pass with smtp.mailfrom, dkim=pass with header.d, and dmarc=pass with header.from. Compare header.d against header.from to judge alignment, because a signature that passes for an ESP's domain does nothing for yours. When mail is forwarded or passes through a mailing list, ARC-Authentication-Results preserves the original verdict so the final receiver can see what the first one saw.

Common mistakes

Trusting hops you do not control

Everything below your boundary MTA is sender-supplied text. A forged Received line can invent a respectable origin, so start at the first hop your own infrastructure added and work upward from there.

Reading dkim=pass as DMARC pass

A valid signature only helps if its d= domain aligns with the From domain. Many platforms sign with their own domain, so dkim=pass sits next to dmarc=fail. Always check the two values together.

Pasting only part of the headers

Copying from the Subject line down loses every Received hop and the authentication results. Without the full block there is no relay path, no verdicts, and no way to tell where a delay or a rewrite happened.

Ignoring the X- headers

X-Forefront-Antispam-Report carries Microsoft's SCL and BCL scores, and X-Spam-Status carries filter scores elsewhere. These explain spam placement when SPF, DKIM and DMARC all pass and the message still lands in junk.

Frequently asked questions

How do I see the raw headers of an email?

In Gmail, open the message, click the three-dot menu and choose Show original. In Outlook on the web, open the message menu and select View message details. In the desktop Outlook client, open the message, use File then Properties, and copy the internet headers box.

How can I tell if an email is spoofed from the headers?

Check Authentication-Results first. If dmarc=fail or the SPF and DKIM domains do not match the From domain, the message is unauthenticated and likely spoofed. Then compare the From header with Return-Path and Reply-To, and find the first Received hop added by your own mail provider to see the real connecting IP.

Which IP in the headers is the real sender?

The one in the lowest Received header that your own mail infrastructure wrote, which records the host that actually connected from the public internet. Received lines below that point are supplied by the sender and can be fabricated. Note that for forwarded mail this IP is the forwarder, not the original sender.

What does Authentication-Results tell me?

It records how the receiving server evaluated the message: the SPF result and the envelope domain checked, the DKIM result and signing domain, and the DMARC verdict with the From domain. It is the receiver's own verdict, so it is ground truth for production authentication.

Why does my test email show dkim=pass but dmarc=fail?

Because the signature is not aligned. DMARC requires the DKIM d= domain to match your From domain's organizational domain, and many sending platforms sign with their own. The signature verifies, alignment fails, and with no aligned SPF either, DMARC fails. Set up DKIM for your own domain in the platform's settings.