Free header guide and PDF
Read an email header: what yours says and what to do next
For: anyone holding a wall of header text they cannot read yet. A test send of your own, a reader who forwarded you the headers of your newsletter, or one message that keeps going to spam.
- Read your own headers with our free email header analyzer.
- Seven steps and a field table to read any header yourself.
- The steps and the field table as a PDF.

The 60-second answer
An email landed in spam, arrived late, or failed a check, and someone told you to look at the headers. Paste the headers of that one email, and the row that matches lights up below. Every row is on this page, and the guide under it shows you how to read any header yourself.
Read the Authentication-Results line first. The receiving server writes it, and it records whether SPF, DKIM and DMARC passed.
A pass only counts for DMARC when it is for your own From domain. DMARC needs SPF or DKIM to both pass and align with the From domain, so SPF and DKIM can pass while DMARC fails.
Read the Received lines from the bottom up. The bottom one is where the message started, and a big gap between two times shows where it waited.
Every explanation on this page comes from the Email Almanac, our own library of more than 4,000 answers about email. You do not have to buy anything to read it.
- You get one email.It comes from Review My Emails, with the PDF link inside.
- Your PDF is the whole guide.The steps and the field table, ready to print.
- Nothing else, unless you ask.No newsletter unless you tick the box. Unsubscribe in one click, any time.
Free tool
Check yours with our free tool.
Paste your headers into our free email header analyzer to see your SPF, DKIM and DMARC results. Then read what yours mean in the steps on this page.
Open the free email header analyzerThe guide
How to read any email header, in 7 steps
One line each. Tick them as you go. Open a step for the full explanation.
- 1
Why:your inbox shows From, To, Subject and Date, and hides the rest. In Gmail it is "Show original".
Read the full explanation
Your inbox shows From, To, Subject and Date, and hides the rest. In Gmail on the web, open the message, open the three-dot menu and pick "Show original". In Outlook on the desktop, go to File, then Properties, and read the "Internet headers" box. In Apple Mail, go to View, then Message, then Raw Source. In Yahoo Mail, open the three-dot menu and pick "View raw message". A bounce message can carry a copy of the original headers too.
- 2
Why:
spf=,dkim=anddmarc=. Anything other than pass did not succeed.Open the free email header analyzer
Read the full explanation
The receiving server adds this line after it checks the message, and it records whether SPF, DKIM and DMARC passed. The first part names the server that ran the checks. Then
spf=,dkim=anddmarc=each carry a result: pass, fail, softfail, neutral, none, permerror or temperror. Anything other than pass did not succeed, and the reason is often in the brackets that follow. If you find more than one Authentication-Results line, each server on the way added its own. The one that counts is the one added by the final receiving server. The most recent sits at the top. - 3
Why:DMARC passes only when SPF or DKIM passes for a domain that matches the From domain.
Check your SPF recordCheck your DMARC record
Read the full explanation
Three addresses are in play. From is the address the reader sees, and its domain is the one DMARC checks. Return-Path is the envelope sender, where bounces go, and it is the domain SPF checks. The
d=in the DKIM signature is the domain DKIM alignment compares with From. The envelope and the header can differ for good reasons, for example when an email marketing tool sends from its own bounce address while showing your brand. DMARC passes only when SPF or DKIM passes for a domain that matches the From domain. In the Authentication-Results line,smtp.mailfromis the domain SPF checked,header.iorheader.dthe domain DKIM checked, andheader.fromthe From domain DMARC checked. An "Authenticated by" note in your inbox is not a DMARC pass. It shows the first positive result it finds, without checking alignment. - 4
Why:
d=is the signing domain,s=the selector used to look up the public key.Read the full explanation
d=is the signing domain,s=is the selector used to look up the public key in DNS, andh=lists the headers that were signed. SPF and DKIM measure different things. SPF checks that the sending IP may send for the Return-Path domain. DKIM checks a signature over the message, so a DKIM pass means the message arrived unchanged from the signing domain. They fail independently. - 5
Why:a hop of seconds followed by a hop of hours shows where the message waited.
Read the full explanation
Every server that handles the message adds a Received line at the top. The bottom one is where the message started, the top one is the last server. Each line shows from (the server that sent it on), by (the server that took it), with (the protocol, where ESMTPS means encrypted) and a time. Compare the times between hops. A hop of seconds followed by a hop of hours shows where the message waited. A wait of 5 to 15 minutes, sometimes up to an hour, can be greylisting, a normal delay for a sender a server does not know yet.
- 6
Why:Message-ID is the reference you use to trace one message through your email marketing tool.
Read the full explanation
Message-ID is a unique ID for each message, in the form
<unique-string@sending-domain>, made when the message leaves. It is the reference you use to search logs or trace one message through your email marketing tool. List-Unsubscribe tells the inbox how to unsubscribe the reader without opening the message, and List-Unsubscribe-Post makes it one click. Feedback-ID lets Gmail break your spam complaints down by campaign in Postmaster Tools. An email marketing tool fills it in with its own IDs. - 7
Why:forwarding often breaks SPF and DKIM. ARC keeps the original results.
Read the full explanation
Forwarding often breaks SPF and DKIM. ARC keeps the original results. Each server in the forwarding chain adds three headers: ARC-Authentication-Results (the results as that server saw them), ARC-Message-Signature and ARC-Seal, numbered i=1, i=2 and so on, so the final receiver can trace the results back.
See every row of the table
What your header means
| Your header | Do this first |
|---|---|
All three pass. spf=pass, dkim=pass and dmarc=pass, and nothing below matched | Authentication is not what moved this email. It proves the mail came from your domain, while where it lands rests on reputation, complaints, engagement, volume and content. Look at your reputation next, starting with the free blocklist check |
A pass, but not for your domain. dmarc=fail while spf=pass or dkim=pass | SPF or DKIM passed for a domain that does not match your From domain, so alignment failed. The usual cause is an email marketing tool using its own bounce domain and signing domain. Ask it to sign with your own domain (custom DKIM), or to use your domain in the Return-Path. What happens to failing mail meanwhile depends on your DMARC policy, p=none, quarantine or reject |
SPF failed. spf=fail or spf=softfail | The server that sent it is not in the SPF record for the Return-Path domain. fail means not authorized, softfail means probably not authorized and often that the record needs updating. Add the sending service to your SPF record. If the IP shown should be allowed, your record is out of date. Check it with the free SPF checker |
SPF could not be read. spf=permerror or spf=temperror | permerror means something in the SPF record is broken: most often more than 10 DNS lookups, two SPF records on one domain, or a typo. temperror means the DNS lookup timed out, the record itself is usually fine, and a single one usually clears on its own. Check the record with the free SPF checker, and read our guide "SPF permerror and the 10 lookup limit" |
DKIM failed. dkim=fail | The signature did not verify. Either the DKIM signing is set up wrong or the message was changed on the way. If you have DKIM set up, compare the header with your DNS: a mismatch means a setup problem. Failures usually come from a DNS record that is missing, expired or does not match the signature |
No DKIM signature. dkim=none, or no dkim= result at all | The message carried no DKIM signature. Your email marketing tool adds the signature once DKIM is set up, and the part you set up is the DNS record with the public key. Without DKIM, a forward that breaks SPF leaves nothing to pass DMARC, because DKIM survives forwarding and SPF often does not |
Nothing published to check. spf=none, spf=neutral or dmarc=none, or no dmarc= result at all | none means a check had nothing to run against, often because it was not set up at all. spf=none means no SPF record was found for the domain. neutral (?all) is treated as if no SPF policy exists. Publish what is missing. A DMARC record can start at p=none, which changes no delivery and sends you reports. Check your records with the free SPF checker and DMARC checker |
| A long wait between two hops. Authentication passed, but two Received times in a row are 15 minutes or more apart | The hop where the time jumps is where the message waited. The by server on that line is the one that took it. A wait of 5 to 15 minutes, sometimes up to an hour, can be greylisting, a normal delay for a sender the server does not know yet. A wait of hours is worth asking about |
| No Authentication-Results line found. | Paste the full headers again. The line is added by the receiving server, and your inbox hides it until you open the full headers, such as Gmail's "Show original". Some servers write an older Received-SPF line instead, which carries the SPF result only |
The header fields at a glance
| Field | What it tells you |
|---|---|
| Authentication-Results | The receiving server's SPF, DKIM and DMARC results |
| Received | One line per server, read from the bottom up, with a time on each |
| From | The sender the reader sees, and the domain DMARC checks |
| Return-Path | The envelope sender, where bounces go, and the domain SPF checks |
| DKIM-Signature | The signing domain (d=), the selector (s=) and the signed headers (h=) |
| Received-SPF | An older line with the SPF result only, plus the IP and envelope sender checked |
| Message-ID | A unique ID for this one message |
| List-Unsubscribe / List-Unsubscribe-Post | How the inbox unsubscribes the reader, and whether it takes one click |
| Feedback-ID | Ties spam complaints in Gmail's Postmaster Tools back to a campaign |
| X-Spam-Status / X-Spam-Score | Some servers' own spam score, sometimes with the rules that fired. Not every inbox adds it |
| ARC-Seal, ARC-Message-Signature, ARC-Authentication-Results | The results each forwarding server saw, chained in order |
See how it plays out for a real business
Worked example 1, a pass that is not yours. Dee Livery sends the monthly newsletter for Brinewater Brewing from news@brinewater.example through an email marketing tool. A reader, wren@mailbox.example, says it went to spam and sends the headers. The top Authentication-Results line reads spf=pass smtp.mailfrom=bounce-7f3@mail.example.net, dkim=pass header.d=example.net and dmarc=fail header.from=brinewater.example. That is the row "A pass, but not for your domain". SPF and DKIM both passed, but for the tool's domain, so neither lines up with brinewater.example and DMARC fails. Nothing is wrong with Wren. Dee asks the tool to sign with brinewater.example, and the next test shows dmarc=pass.
Worked example 2, a softfail that still passed. Hedda Line, who writes Brinewater's emails, also looks after its new online shop, and order receipts go out from hedda@brinewater.example through the shop's own platform. Hedda sends a test receipt, opens the full headers and finds spf=softfail smtp.mailfrom=brinewater.example, dkim=pass header.d=brinewater.example and dmarc=pass. That is the row "SPF failed". The shop's server is not in Brinewater's SPF record yet, which a softfail often means. DMARC still passed, because DMARC needs only one of SPF or DKIM to align, and DKIM did. Hedda adds the shop to the SPF record and checks it with the free SPF checker.
Worked example 3, a reminder that arrived late. Brinewater's tasting-night reminder reaches Wren almost three hours after Dee sent it. The Authentication-Results line shows all three passing. Dee reads the Received lines from the bottom up. The first two hops are two seconds apart. The next one, where the receiving server took the message, is stamped 2 hours and 47 minutes later. That is the row "A long wait between two hops". The wait sits on that hop. It is longer than greylisting usually takes, so Dee takes the hop names to the SOS line.
Who we are
About Review My Emails
Review My Emails is email list cleaning and validation that tells you which addresses to keep, which to watch and which to stop sending to, and why.
Most checkers answer one question: does this address exist? We answer the next one: should you send to it? An address can be perfectly valid and still be quietly damaging your sender reputation. Valid is not safe.
The company was founded in 2020 and is based in Bolton, United Kingdom. Our founder is Yanna-Torry Aspraki, an email deliverability specialist who has worked in deliverability since 2015.
Your next step. Want every field laid out for you? Paste the same headers into the free email header analyzer at reviewmyemails.com/tools/email-headers, or the whole message into the free email source analyzer at reviewmyemails.com/tools/email-source-analyzer. To fix what your row points at, use the free SPF checker (reviewmyemails.com/tools/spf-checker), the DMARC checker (reviewmyemails.com/tools/dmarc-checker) and the blocklist check (reviewmyemails.com/tools/blacklist-checker). Still not sure what your header is telling you? Ask the free SOS line at reviewmyemails.com/sos. A real person answers, with no pitch.
List cleaning does not fix SPF, DMARC, MX or blocklist problems. Those live in your sending setup, and they are a different job. A blocklist listing measures your sending, so it is never a reason to suppress anyone on your list. And nobody can promise you the inbox, so we do not.
Yanna-Torry Aspraki, Review My Emails
Email SOS Hotline, free
Stuck? We are here.
For those problems there is the Email SOS Hotline, our free help line. Tell Yanna-Torry what is going on and she will tell you what she would do. She reads every message herself and replies within 48 to 72 hours, with no pitch.
Ask the free SOS lineWords used
- Email header
- the block of details at the top of every message that records how it was sent, routed and checked
- Envelope
- the addresses used while the message travels, which control routing and bounces. The reader never sees them
- Return-Path
- the envelope sender, where bounces go, and the domain SPF checks
- Authentication-Results
- the line the receiving server adds with its SPF, DKIM and DMARC results
- Alignment
- the check that the domain SPF or DKIM passed for matches the From domain
- Received line
- the stamp each server adds as it handles the message, one per hop
- ARC
- headers a forwarding server adds to keep the original authentication results
Where this came from: the Review My Emails Email Almanac.
- What is DKIM-Signature header?
- What is greylisting delay?
- What is the “From” header and what does it mean?
- What is the “Message-ID”?
- How do “softfail (~all)” vs “fail (-all)” vs “neutral (?all)” behave?
- What are the DMARC policies (p=none, p=quarantine, p=reject)?
- What is “alignment” in DMARC and how is it checked?
- What happens when DMARC fails?
- What is identifier alignment in DMARC?
- What domain is checked for DKIM alignment? (d= domain vs From)
- Why does alignment sometimes fail even if SPF/DKIM passes?
- Why do some emails show “Authenticated by XYZ” even with DMARC fail?
- Why does authentication not equal deliverability?
- Can you have SPF and DKIM pass but DMARC fail?
- What is an email header?
- What is the difference between envelope and header?
- How do I view full email headers in different clients (Gmail, Outlook, etc.)?
- What key information can I find in email headers (e.g., Received, Authentication-Results, Message-ID)?
- What do “Received” headers mean?
- What is a “Return-Path”?
- How can headers help troubleshoot deliverability problems?
- What is ARC-Seal, ARC-Message-Signature, and ARC-Authentication-Results?
- What is “Authentication-Results” and how to read it?
- What is the difference between SPF and DKIM results in headers?
- What is “Received-SPF”?
- What are “List-Unsubscribe” headers?
- What is “Feedback-ID”?
- What information is usually included in a bounce message (DSN)?
- How do you trace message hops with headers?
- How to troubleshoot SPF “permerror” or “temperror”?
- What is the Authentication-Results header?
- What information does it contain?
- How can I use this header to troubleshoot authentication?
Founded in 2020, based in Bolton, United Kingdom.
reviewmyemails.com/resources/read-an-email-header?c=web-p10-r11pdf · v1