Paste raw email headers to analyze SPF/DKIM/DMARC and delivery path.
Email Header Analyzer parses raw email headers and shows the full delivery path: every relay server, transit time, SPF/DKIM/DMARC verdicts. Diagnoses spam issues, phishing attempts, delivery delays.
DMARC compliance requires Header.From to align with the DKIM signature domain OR the SPF return-path domain. Relaxed = same organizational domain (eTLD+1). Strict = exact match.
Drop your email — we will re-run this check every 7 days and alert you if anything degrades (SSL expiry, DNS change, header regression). Free.
One-click unsubscribe in every email. We never share email addresses. By subscribing you agree to our privacy policy.
Decode the email delivery path and verify authentication
Visualize all servers the email passed through with timestamps and delays at each hop.
Instant check of authentication results: pass, fail, softfail, neutral. Detects spoofed emails and config issues.
Extracts X-Spam-Score, X-Spam-Status and other anti-spam markers to analyze why emails land in spam.
Email headers contain metadata about origin, routing, and authentication of a message. The Received headers trace the delivery path from sender to recipient — read bottom-up. Authentication-Results shows whether SPF, DKIM, and DMARC checks passed. X-Spam-Score indicates spam filter results. Analyzing headers helps diagnose delivery failures and detect phishing or spoofed emails.
In Gmail: open email → menu "⋮" → "Show original". In Outlook: File → Properties → Internet Headers. In Apple Mail: View → Message → All Headers.
SPF fail means the sending server IP is not listed in the domain allowed IPs. This may signal spoofing or an incorrectly configured SPF record.
SPF checks whether the sender IP is authorized for the domain. DKIM verifies a digital signature on the email content. DMARC combines both mechanisms and defines a handling policy.
Signs: SPF fail or softfail, DKIM fail, DMARC fail with reject/quarantine policy, mismatch between From: domain and Received: headers, suspicious X-Originating-IP.
Each server in the delivery chain adds a timestamp to the Received: header. The difference between timestamps is the hop delay. Delay >10s is suspicious, >60s indicates a queue problem.
Longer-form reading on this topic from the knowledge base.
Alerts on MX / SPF / DKIM / DMARC changes — guard against silent email infrastructure breakage.