Client Side Forensic Utility With Zero Data Upload
Email Header Analyzer
Follow a message back through every server that touched it. Headers never leave your browser.
Analyze your email headers
The executive triage, the recorded route, the authentication claims, the platform headers, the server map and the report downloads appear here once you paste headers, choose a file or load a sample. Your input stays on this device.
The analyzer rebuilds the hop timeline with transit delays, scores SPF, DKIM and DMARC, compares the DKIM body hash from a complete EML file and shows where the visible sender, the envelope sender and the reply address disagree.
Paste the full headers or choose the original EML or Outlook MSG file
Pasted headers rebuild the route and the authentication scorecard. A complete EML file adds the RFC 6376 DKIM body hash comparison in both simple and relaxed canonicalization, with stored LF line endings normalized to the CRLF form the signer used, which removes the most common cause of a false mismatch. A mail client that rewraps text, converts encodings or adds a footer can still cause one, so resolve a mismatch against the copy in the original mailbox. The MIME structure of an EML is also read for attachments, remote images, open tracking pixels, links rewritten by Safe Links, Proofpoint or Mimecast, AMP for Email content and read receipt requests, while the body text itself is never displayed or exported. An Outlook MSG file is read as the compound file it is: the stored transport headers feed the same route and authentication analysis, and the Outlook properties add the unsent flag, submit and delivery times, creator and last modifier, recipients and attachment names. In Gmail use Show original; in Outlook drag the message to a folder to save it as MSG, or save it as EML.
Zero Upload Local Browser Processing
Supported inputPasted RFC 5322 headers, a complete EML file or an Outlook MSG file
Size limits256 KiB of pasted headers, a 10 MiB EML file or a 25 MiB MSG file
StandardsRFC 5322, RFC 8601, RFC 6376 and RFC 9989
Platforms readMicrosoft 365, Exchange, Google Workspace, gateways, sending services and archivers
Processed on your device. Your input is not uploaded. Optional usage measurement stays off unless you allow Analytics. It sends GDF only the tool name and fixed action labels, such as analysis completed or report prepared. No input, result, filename or visitor identifier is sent. Google and advertising scripts do not load on this page. Use Cookie settings below to change your choice. Clear removes the selected input and results from this page; it does not erase downloads you save.
Local Browser Execution With Zero Data Upload
GDF Free Tools analyze files and email headers in your browser on your own computer. Your selected files, pasted headers and extracted results are not uploaded to GDF or an outside analysis service. The page and parser download to your browser; inspection runs locally.
Pasted headers and EML files are read in this page only. Country lookups use a DB-IP Lite table served from this site and read in your browser, so no address leaves the device. Reverse DNS and city level location are available only through the Enrich this mapping button, which names the outside services and the exact addresses before anything is sent and returns you to the standard report if you cancel.
Applying Tool Outputs in Defensible Forensic Workflows
Use a working copy for inspection and preserve the original evidence. The report records the inspected input hash, inspection time and tool version so you can document what you examined. Check important findings and the tool’s limits as part of your examination. Metadata and email headers alone do not establish authenticity.
Server clocks, display names and authentication claims are recorded statements inside the message. They are powerful when read together and misleading when read alone, which is why the triage card places them side by side before the detail.
What the analyzer establishes
The hop timeline reads every Received header oldest first, resolves each recorded timestamp to UTC and computes the transit delay between servers, so a hop stamped before its predecessor or a delay of hours stands out at once. Server names, visible IP addresses and the recorded dates stay beside each hop with the original header text one click away.
The authentication scorecard reports the SPF, DKIM and DMARC results written by the receiving server, and the DKIM body hash card states whether the supplied body still matches the signed value. The sender identity card places the From address, the envelope sender, the Reply To address and the Message ID domain together, because a reply redirected to another domain or a display name that contains a different address is the pattern behind most business email compromise losses.
Platform headers are grouped and explained rather than left as a wall of X headers. Microsoft 365 fields such as AuthAs, the Exchange Online Protection receipt record and the Unsent flag, Google Workspace fields and the ARC chain each appear with a plain English reading, and a signature table recognizes the security gateways, sending services, hosting providers and archivers that touched the message, from Proofpoint and Mimecast to Amazon SES and Smarsh. A world map served from this site shades the countries the recorded server addresses belong to, using a country table read in your browser.
An Outlook MSG file stores the message as MAPI properties rather than as the bytes that crossed the network. The analyzer reads the compound file in the browser, takes the stored transport headers when Outlook kept them and reconstructs labelled header fields from the properties when it did not, which is normal for mail that never left the Exchange organization. The Outlook message properties card then states the message class and flags, the sender and any mailbox it was sent on behalf of, the recipients, the attachment names and sizes, and the client submit, delivery and last modification times with the creator and last modifier. The unsent flag is called out because an item carrying it never left the mailbox it was saved from. Body, HTML and RTF content are never read; only their presence is recorded.
Every exported report carries the SHA 256 of the exact bytes analyzed, whether that is the EML file, the MSG file or the pasted text encoded as UTF 8, and states which it was.
What it cannot establish alone
A recorded pass is the receiving server’s claim at delivery time. Authentication Results headers can be forged by anyone who controls a hop, so trust depends on how the message was received and preserved. The local DKIM body hash comparison tells you whether the body you supplied still produces the fingerprint written in the DKIM header. That is a consistency check, not a verified signature, because anyone composing a message can write a matching fingerprint into a header of their own; it does not fetch the signing domain’s public key, recheck SPF, retrieve DNS records or locate a sender. Header only input cannot check a message body.
When you want more than the offline country table, Enrich this mapping asks before sending the recorded public server addresses to Cloudflare DNS over HTTPS for reverse DNS and to ipapi.co for location. The dialog lists every address and service, nothing else from the message is sent, and the report records the approval time and providers beside each result. Reverse DNS names are published by the address owner and geolocation is a third party estimate of where the server sits, not where a person was.
Server clocks drift and some hosts write the wrong zone, so a route that appears out of order deserves examination rather than a conclusion. Those are precisely the questions a full email examination answers with server logs, mailbox exports and the original transport records. The methods are described in RFC 8601, RFC 6376 and RFC 9989.
Free consultation
Is a disputed email at the center of your matter
A failed DMARC result, a mismatched Reply To or a body hash that no longer matches changes how a message can be relied upon. A senior examiner can tell you on the first call what the headers show, which mailbox and server records to preserve and how to move the originals securely. Our examiners have testified in federal and state courts on email evidence. This tool never attaches your input or report to the inquiry.
Version 1.1.0. Email Header Analyzer is free to use. Browse free tools. © 2026 Global Digital Forensics, Inc. All rights reserved.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .