Email Header Analyzer
Trace delivery, authentication, and delays from raw message headers.
Related Tools
SPF Checker
Check a domain's SPF record. Follows every include and counts the 10-lookup limit.
Use tool →DMARC Checker
Check a domain's DMARC policy. Tags explained in plain English, reporting verified.
Use tool →SPF, DKIM & DMARC Generator
Generate SPF, DKIM, and DMARC DNS records for Google Workspace, Microsoft 365, or custom setups.
Use tool →Email Compatibility
Check HTML email code for rendering issues across Gmail, Outlook, and Apple Mail.
Use tool →How to Analyze Email Headers
Open the email you want to investigate and find the raw headers. In Gmail, click the three dots menu and choose "Show original." In Outlook, open message properties. Copy the full header text and paste it above. The analyzer traces every server hop your message took, checks SPF, DKIM, and DMARC authentication, and flags any delays or issues in the delivery chain.
If you've used Microsoft's Message Header Analyzer or Google's Admin Toolbox Messageheader, this is the same job without the ecosystem lock-in. Paste headers from any client, analyze any message. Nothing gets uploaded, because the parsing happens in your browser.
What Email Headers Tell You
Every email carries a trail of metadata that records its journey from sender to recipient. Each server that handles the message adds a "Received:" header with its name, IP address, and timestamp. Reading these headers reveals the complete delivery path, how long each hop took, and whether the message was delayed, rerouted, or relayed through unexpected servers. This is essential for diagnosing delivery problems, identifying spoofing attempts, and understanding why emails end up in spam.
Understanding SPF, DKIM, and DMARC
SPF verifies that the sending server's IP address is authorized by the domain's DNS records. DKIM adds a cryptographic signature to the message that proves it wasn't altered in transit. DMARC ties SPF and DKIM together with a domain policy that tells receiving servers what to do when authentication fails. All three working together is the standard for legitimate email delivery. When any of them fails, the message is more likely to be flagged as spam or rejected entirely.
Reading a Failed Authentication-Results Line
The Authentication-Results header is where the receiving server writes down its verdict. A healthy one looks like spf=pass dkim=pass dmarc=pass. When something's off, the failure names the fix.
spf=softfail means the sending IP isn't in the domain's SPF record. Common after adding a new sending service without updating DNS. Check the record with our SPF Checker, which also counts the 10-lookup limit that silently breaks overloaded records. dkim=fail usually means the signature didn't verify: either the message was modified in transit (footers appended by mailing lists do this constantly) or the DNS key doesn't match. Look up the key with the DKIM Checker. dmarc=fail means neither SPF nor DKIM passed in alignment with the From domain, and the domain's policy decides what happens next. See what that policy actually says with the DMARC Checker.