Step 1
Paste raw headers
Copy the original message headers from Gmail, Outlook, Apple Mail, or your mail server logs.
An email header analyzer parses raw email headers so you can trace the delivery path, verify SPF, DKIM, and DMARC results, and spot routing delays or delivery issues. Paste headers below to inspect each mail hop entirely in your browser.
Want this automated? MailParse receives inbound email and turns headers, MIME parts, and auth results into structured JSON.
Need to validate sender DNS policy too? Run the SPF Record Checker.
Step 1
Copy the original message headers from Gmail, Outlook, Apple Mail, or your mail server logs.
Step 2
The parser unfolds the headers, extracts Received hops, and calculates how long each handoff took.
Step 3
Confirm SPF, DKIM, and DMARC, then use flagged delays or missing headers to diagnose delivery problems.
An email header analyzer reads the raw SMTP headers from a message, maps each Received hop, and surfaces authentication results like SPF, DKIM, and DMARC so you can diagnose routing or deliverability issues.
Each mail server that handles a message adds a Received header. Reading them from oldest to newest shows the path the email took, which servers touched it, and how long each hop took.
You can usually see the receiver's verdict in Authentication-Results or Received-SPF headers. These results tell you whether SPF, DKIM, and DMARC passed, failed, or were missing when the message was evaluated.
Large delays can indicate greylisting, queue backlogs, upstream throttling, DNS issues, or retry behavior between mail servers. Comparing hop timestamps helps you find where the delay started.
No. This tool parses the headers entirely in your browser so you can inspect routing and authentication data without sending the raw headers to a server.
MailParse receives emails, validates SPF, DKIM, and DMARC, and delivers structured JSON to your app or webhook.