Skip to content
DMARC Pulse

Email header analyzer

Header Analyzer for Email

Paste the full headers of a message to trace its path, spot delays and understand why SPF, DKIM or DMARC passed or failed.

Analyzed in your session only. Headers are never stored.

Example result

Sample data, not a live check. Run the tool above to see your own result.

Result for

acme.example

Looks good

spf=pass dkim=pass dmarc=pass

Details

From
Acme <billing@acme.example>
To
you@example.net
Return-Path
<bounce@acme.example>
Date
Mon, 02 Nov 2026 10:15:03 +0000
Message-ID
<1042@acme.example>
SPF
acme.example
DKIM
acme.example
DMARC
acme.example

What we found

  • SPF passed (acme.example)

  • DKIM passed (acme.example)

  • DMARC passed (acme.example)

  • Return-Path aligned with From (acme.example)

    SPF can count towards DMARC for this message.

  • DKIM signed by acme.example, aligned with From

    This is what lets DMARC pass even when mail is forwarded.

Delivery path

Total delay: 3s
1
app.acme.example198.51.100.12
mail-out.acme.example
ESMTP
—
2
mail-out.acme.example203.0.113.25
mx.example.net
ESMTPS
3s

DKIM signatures

d=acme.example · s=google · a=rsa-sha256

What to do with the result

SPF, DKIM and DMARC all show pass

The pasted header reports an aligned pass. This analyzer reads that text; it does not repeat authentication. Trust only results inserted by your receiving provider, because senders can forge header fields. Aligned means the verified domain matches the one your recipients see. The result covers one message at one receiver. A DMARC pass does not decide inbox placement, because each receiver applies its own filtering.

Test a message from every service that sends as example.com. Then read your aggregate reports to find senders you forgot. These are XML summaries that receivers send to your rua address. If you are at p=none, move to p=quarantine only when all your legitimate senders pass.

DMARC shows fail or none

dmarc=none means the receiver found no DMARC record for the From domain. Publish this TXT record at _dmarc.example.com:

v=DMARC1; p=none; rua=mailto:dmarc@example.com

dmarc=fail means a record exists and no passing check aligned with From. Compare that domain with Return-Path and each d= under DKIM signatures. If those belong to your email service, add your domain in its settings. Publish the DKIM key before you turn signing on, then test again.

Lines that say aligned only compare names, and they do not prove a check passed. With adkim=s or aspf=s in your record, the domains must be identical.

SPF or DKIM shows a result other than pass

The domain in parentheses under What we found is the one tested.

  • spf=fail or softfail: that domain’s SPF record does not authorize the sending IP. If the domain is yours, add the sender to the existing record, because a second record causes permerror. Forwarding often breaks SPF, so check DKIM first.
  • spf=permerror: the record is invalid, for example more than 10 DNS lookups. Run the SPF Checker.
  • dkim=fail: the message changed in transit or the key does not match. Test s= and d= in the DKIM Checker.
  • none: no SPF record exists, or the message has no DKIM signature.
  • temperror: a temporary DNS problem. Test again before changing anything.

One hop took more than five minutes

A hop is one handoff between two mail servers. The tool flags a gap over five minutes between two Received lines and names the server that accepted the message after the wait. The server in that row’s From column held the message, or the named server refused it for a while.

Search the From server’s logs for the Message-ID shown in Details. Look for 4xx replies, which are temporary refusals. A gap that matches that server’s retry interval points there. Each server stamps its own clock, so confirm the delay with a second test before changing anything.

No headers found, or dashes instead of results

No headers found means the text had no Name: value lines. That usually happens when you paste a message body. Copy the raw source of the message instead.

Dashes in all three labels mean the text has no usable Authentication-Results header. The verdict can still read Looks good, so disregard it here. The receiving server writes that header, so copy from the recipient’s inbox and avoid your Sent folder. Start the paste at the first header, because the tool stops at the first blank line. If the header is still missing, test another mailbox.

Explained

How to get the headers

  • Gmail: open the message → ⋮ → Show original → copy.
  • Outlook: open the message → … → View → View message source.
  • Apple Mail: View → Message → All Headers.

Reading the email header analyzer results

Hops are listed from the first server to the last. The Authentication-Results header, added by the receiving server, records SPF, DKIM and DMARC. For DMARC, what matters is whether SPF or DKIM passed for the same domain as the From address.

Frequently asked questions

Are my headers stored?
No. They are analyzed in your request and shown once. Nothing is saved to our database.
Why are there several Received headers?
Each server that handles the message adds one at the top. Reading them bottom-up gives the path from sender to recipient.
What causes a long delay between hops?
Greylisting, queues on the sending side, spam filtering appliances or temporary delivery failures with retries.
DKIM passed but DMARC failed — why?
The DKIM signature probably belongs to your email service’s domain, not yours. Enable custom DKIM signing with your own domain.

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.

Related tools