Toolsky

Free Online Tools & Utilities for Every Task.

Email Header Decoder

Parse raw email headers into a human-readable format to analyze sender info, routing hops, and security flags.

Every email carries a hidden travel diary. Before the message reached your inbox, it passed through a chain of servers, and each one stamped its passage into the email headers — a block of technical lines recording who sent it, which servers handled it, when, and whether its identity checks passed. The trouble is that raw headers are nearly unreadable. The Email Header Decoder on ToolSky parses raw email headers into a human-readable format, so you can analyse sender information, routing hops and security flags without squinting at the raw block.

What Is Actually Inside an Email Header

The familiar fields are the tip: From, To, Subject and Date. Beneath them sits the evidence. Received lines form the routing chain — every server that touched the message adds one at the top, so reading them from bottom to top reconstructs the journey from sender to you, complete with timestamps that reveal where delays happened. Authentication-Results records the verdicts of the three email authentication systems: SPF (was the sending server authorised for that domain?), DKIM (does the message carry a valid cryptographic signature from the domain?) and DMARC (do the results align with the domain's policy?). Message-ID gives the message its unique fingerprint, and fields like Return-Path and Reply-To show where bounces and replies really go — which are not always the address shown in the From line. The header format itself is defined by the internet standard RFC 5322, maintained by the RFC Editor.

What Decoding Them Gives You

  • A readable summary: sender, recipient, subject and date extracted from the raw block and presented clearly.
  • The routing path: the chain of servers the message passed through, in order, so you can see its journey across providers and countries.
  • Security flags surfaced: SPF, DKIM and DMARC results made visible, so authentication failures stand out instead of hiding in jargon.
  • Delay diagnosis: timestamps hop by hop, showing exactly where a message sat for six hours before arriving.

Headers tell you how a message travelled; whether the sender domain itself has a clean reputation is a different question, answered by the Email Blacklist Check.

How to Decode Email Headers

  1. Open the suspicious or interesting email in your mail app and find the option to view the original message or full headers (in Gmail it is "Show original"; in Outlook, message properties/details).
  2. Copy the entire header block — everything above the message body.
  3. Paste the raw headers into the Email Header Decoder.
  4. Run the decode and read the parsed summary: sender details, subject, date and the authentication results.
  5. Walk the routing hops from bottom (origin) to top (delivery) and compare the timestamps to find delays.
  6. Compare the technical sender (Return-Path, originating server) with the friendly From address; in honest mail they belong to the same organisation.

Two Investigations This Makes Easy

The "urgent invoice" that was not. An accounts assistant receives an invoice request apparently from the company's CEO. The decoded header tells another story: SPF fails, the Return-Path points to an unrelated domain, and the earliest Received line traces to a server in a network the company has never used. The From name was genuine-looking; the headers were not. That combination — failed authentication plus mismatched return path — is a practical working definition of spoofing, and the correct action is to verify by phone and delete.

The email that took nine hours. A client insists they sent a contract at 9 a.m.; it arrived at 6 p.m. The hop timestamps show the message left the sender's provider instantly, then sat at one intermediary relay for almost the entire gap before delivery. Nobody is lying and nothing was "lost in your spam" — the delay is localised to a single server, which turns an argument into a factual support ticket. Administrators run exactly this analysis with header tools; a decoder makes it accessible to anyone, and pairing it with the Email Validator covers the address side of a deliverability puzzle.

Reading Headers Without Fooling Yourself

Only trust the hops added by your own provider. Everything below the first Received line added by a server you control could, in principle, have been fabricated by the sender. The chain is trustworthy from the point your infrastructure first stamped it — treat earlier entries as claims, not facts.

Authentication results beat appearances. Display names and logos are trivially copied. A message that fails SPF and DKIM while claiming to be your bank should be judged on those failures, not on how professional the HTML looks.

Softfail is not pass. An SPF "softfail" (~all) means the sender's domain does not fully commit to its own policy. It is a yellow flag: common with legitimate but loosely configured senders, and also with forgeries.

Absence of headers analysis tools is normal. Most people never see headers until something goes wrong — a phishing scare, a deliverability mystery, a compliance request. That is precisely when a structured decode matters: under pressure, raw header blocks are worst-case reading. For the web-side equivalent of this kind of inspection, the HTTP Headers Parser does the same job for HTTP responses.

Frequently Asked Questions

Where do I find the full headers of an email?

In Gmail, open the message, click the three-dot menu and choose "Show original." In Outlook, open the message and check its properties or details for "Internet headers." Other clients have a similar "view source" or "show original" option.

What does SPF fail mean in a decoded header?

It means the server that sent the message is not on the list of servers authorised to send for that domain, according to the domain's SPF record. Combined with a request for money or credentials, treat it as strong evidence the message is forged.

Can email headers be faked?

The lower part of the Received chain (entries the sender's side added) can be fabricated, and display names are cosmetic. The entries stamped by your own provider and the authentication results it recorded are the parts you can rely on.

How do I tell where an email was delayed?

Compare the timestamps on consecutive Received lines, reading bottom to top. The biggest gap between two neighbouring stamps is where the message waited, and the servers named on either side of the gap identify whose queue it was.

What is the difference between From and Return-Path?

From is the author address shown to you. Return-Path is where delivery failures (bounces) are sent, set by the sending system. In legitimate mail they usually share a domain; a wild mismatch is a classic spoofing indicator.

Does decoding headers expose the email's content?

No. Headers are the envelope and routing information only. You paste the header block, not the message body, so your analysis never needs to involve the content itself.

Why do legitimate emails sometimes fail authentication?

Forwarding breaks SPF naturally (the forwarder is not authorised for the original domain), and mailing lists can invalidate DKIM by modifying messages. A single fail is a clue to investigate, not automatic proof of fraud — context and the full set of flags matter.

The Envelope Tells the Truth

An email's content can say anything; its headers record what actually happened. Decode them, and questions that feel like guesswork — is this genuine, where was it delayed, who really sent it — get evidence-based answers in under a minute.