Email Header Analyzer
Inspect reported authentication results, alignment signals and the routing trace in an email header.
Run a diagnostic
The analysis script has not loaded. If the button stays disabled, reload the page and check JavaScript or caching settings.
Email headers stay in your browser. Public DNS results may be cached for 5 minutes. Public DNS TXT checks may use Google Public DNS when the server resolver returns no TXT records. Email headers are not sent to that DNS service.
How to use and interpret this tool
Paste the original raw headers or open an .eml file, then locate Authentication-Results, the visible From domain and the Received chain. Compare spf=, dkim= and dmarc= with their reported identities rather than treating any pass as aligned.
How to read the findings
Check which receiving system added Authentication-Results. An upstream header can be forged or copied; the trusted receiving hop matters. Read Received lines from bottom toward the top to understand routing, without assuming every timestamp is reliable.
Limitations and next steps
This tool interprets header claims locally. It does not cryptographically verify DKIM signatures, prove the message is genuine, or send the email to Skysnag for inspection.
Need continuous authentication protection?
Method and limitations
Analyze email headers and Authentication-Results for SPF, DKIM, DMARC and relay hops without uploading message content. Public DNS checks cannot prove inbox delivery or message-level authentication.
Frequently asked questions
Can headers prove DKIM verification?
Authentication-Results records what a receiving system reported; a pasted header alone cannot establish that the reporting system is trustworthy.
Can SPF pass while DMARC fails?
Yes. SPF can pass for a Return-Path domain that is not aligned with the visible From domain; DMARC needs aligned SPF or aligned DKIM.
Educational diagnostics, not a guarantee of deliverability or provider approval.