Authentication under review
ExampleThe reasoning, in plain English
Do this first
Free authentication guide and PDF
For: anyone whose mail just failed SPF, DKIM or DMARC. A bounce that names authentication, a dmarc=fail in a header, or a DMARC report full of failures you cannot explain.

The 60-second answer
Your mail failed a check and you want to know why. Pick which check failed and how your mail reaches people, or paste the Authentication-Results line from a message, and the row that matches lights up below. Every row is on this page, and the steps under it show you how to read the verdict yourself.
Read the receiver's verdict before you change anything. Open the raw message and find the Authentication-Results line. It shows spf=, dkim= and dmarc=, each with a result such as pass, fail or permerror.
DMARC needs more than a pass. SPF or DKIM has to pass for a domain that matches the From your readers see. That is how SPF and DKIM can both pass while DMARC fails.
Passing all three is the floor, not the inbox. Authentication proves the mail is really from you, and placement is decided after that. A failed check is not a bad address either, so cleaning your list will not fix it.
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.
Which case are you?
Pick which check failed and how your mail travels. The card shows why and what to do first.
Answer here and your row lights up, with what to do first. The PDF has every row and the full guide.
Authentication under review
ExampleThe reasoning, in plain English
Do this first
To read the results in your own headers, paste them into our free email header analyzer. Open the free email header analyzer
The guide
One line each. Tick them as you go. Open a step for the full explanation.
Why:the Authentication-Results line added by the final receiving server is the one that counts.
Open the free email header analyzerThe email header guide
Every message carries an Authentication-Results header, added by the receiving server, with a result for SPF, DKIM and DMARC. In Gmail, open the message, click the three-dot menu and choose "Show original". In Outlook on the web, choose "View message source". If several servers added a line, the one that counts is the line added by the final receiving server. The "Authenticated by" label some inboxes show is not the same as DMARC passing, so read the line itself.
Why:SPF and DKIM each vouch for a domain. DMARC asks whether it is the one in your From line.
Each check answers a different question, and the table below says what each one proves and what it does not. The short version: SPF and DKIM each vouch for a domain, and DMARC asks whether that domain is the one your readers see in the From line.
Why:for DKIM, none means no signature was attached.
Each check ends in a result: pass, fail, softfail, neutral, none, permerror or temperror. For SPF, softfail means the sending server is discouraged but not hard-blocked, and permerror usually means the record has a syntax problem or too many DNS lookups. For DKIM, none means no signature was attached. A temperror means the receiver could not get an answer from your DNS at that moment. One usually clears on its own. If it keeps coming back across many receivers, check your DNS host.
Why:DMARC passes only when SPF or DKIM passes and also aligns with your From domain.
DMARC passes only when SPF or DKIM passes and also aligns, which means the domain that passed matches your From domain. SPF is compared using the Return-Path domain. DKIM is compared using the d= domain in the signature. In relaxed mode, the default, a subdomain such as mail.lighthouse-letterpress.example still matches lighthouse-letterpress.example. A service that sends for you uses its own domains by default, so it breaks alignment until you set it up to sign with yours.
Why:forwarding breaks SPF. A mailing list that adds a footer breaks DKIM too.
Forwarding breaks SPF, because the receiver sees the forwarder's server, not yours. Plain forwarding usually leaves DKIM intact, but a mailing list that adds a subject tag or a footer breaks it. With both broken, DMARC fails, and under a p=reject policy the forwarded copy may be refused. ARC is a sealed record of the original checks that travels with the message. Forwarders and lists add it, not you. It only helps where the receiving provider trusts it.
Why:an authentication failure arrives suddenly and hits all your mail at once.
An authentication failure tends to arrive suddenly and hit all your mail at once, often right after a DNS edit, a DKIM key change, an SPF edit or a change to your email marketing tool's setup. A reputation problem slides over days or weeks. Moving to a new email marketing tool means new DKIM keys. Publish the new selector next to the old one, and remove the old one only after the old tool has stopped sending.
Why:where it lands is decided after that, on reputation, complaints, engagement and list quality.
Authentication proves the mail really came from your domain. Where it lands is decided after that, on reputation, complaints, engagement and list quality. A DMARC pass only means you are not turned away on identity before those other signals are checked.
Your plan
Why your check failed
| What you see | Do this first |
|---|---|
SPF fails or softfails. spf=fail or spf=softfail, or a bounce that says "SPF check failed" or "sending IP not authorized" | The server that sent the mail is not on your SPF list. Usually a new sending service was never added, or your email marketing tool changed its servers. Check the record for the Return-Path domain, not the From. Cleaning the list will not fix this one. Check your record with our free SPF checker |
SPF permerror. spf=permerror, or "too many DNS lookups" | The record itself is broken. Most often it needs more than 10 DNS lookups, or the domain has two SPF records. Remove services you no longer use first, and merge two records into one. Cleaning the list will not fix this one. Read our guide "SPF permerror and the 10 lookup limit: get back under, step by step" |
DKIM fails. dkim=fail, dkim=permerror or dkim=none, or "bad signature", "key not found" or "body hash did not verify" | Key not found means the receiver found no key at the selector named in the signature. Bad signature means it found the key but the signature did not match, often after a key change, a damaged key in DNS, or a relay that changed the message. dkim=none means no signature was attached at all. Cleaning the list will not fix this one. Read our guide "DKIM keys: how to swap one without breaking your mail" |
SPF and DKIM pass, but DMARC fails. spf=pass, dkim=pass, dmarc=fail | An alignment problem. The domains that passed are not the one in your From. The usual fix is to set your email marketing tool to sign with your own domain, using the records it gives you. The other is a custom Return-Path on your domain. Cleaning the list will not fix this one. Check your policy with our free DMARC checker |
| It fails only on forwarded or mailing list mail. Your own sends pass, but copies that went through a forward, an alias or a list fail | This is expected. Forwarding breaks SPF, and lists that change the message break DKIM as well. You do not set up ARC yourself. The forwarder or the list does. Keep DKIM solid, because it survives simple forwarding, and watch your DMARC reports. Cleaning the list will not fix this one. |
All three pass, but mail still lands in spam. spf=pass, dkim=pass, dmarc=pass | Your authentication is working, so the fix is not in your records. Passing proves the mail is really from you. It does not decide the inbox. Look at reputation and engagement next. Read our guide "Your emails are going to spam. Here is how to get them back." |
You only have a bounce code. 5.7.26, 5.7.27 or 5.7.30, or a 550 or 554 that names SPF, DKIM or DMARC | At Gmail, 5.7.26 means the message failed authentication, 5.7.27 points to SPF and 5.7.30 to DKIM. Under a p=reject policy a failing message is refused outright, which is why it comes back as a bounce. The address is fine, so keep the reader. Read the words in the bounce before you change anything. Then read the header of a test send to see which check failed, and use the row that matches. Cleaning the list will not fix this one. |
| Check | What it proves | What it does not prove |
|---|---|---|
| SPF | The server that handed over the message is on your domain's list of allowed senders | It checks the hidden Return-Path address, not the From your reader sees, so on its own it does not stop someone faking your name |
| DKIM | The message carries a signature from the signing domain and was not changed on the way | It does not check that the signing domain matches your visible From |
| DMARC | SPF or DKIM passed for a domain that matches your From. It also tells the receiver what to do when that fails, with p=none, p=quarantine or p=reject | It is an identity check, not a quality verdict. It does not put mail in the inbox |
| BIMI | Your logo can show next to your mail in inboxes that support it, once DMARC is at p=quarantine or p=reject | It is a trust signal, not a deliverability signal. Spam filters do not see the logo |
Worked example. Dee Livery sends the Lighthouse Letterpress newsletter from news@lighthouse-letterpress.example. Last week she moved it to a new email marketing tool. This week a block of Gmail readers bounce with 550 5.7.26. That is row 7, so before she touches anything she sends herself a test and opens "Show original". The line reads spf=pass, dkim=pass, dmarc=fail. Both checks passed, but for the new tool's own domains, not hers. That is row 4, an alignment problem. Her readers did nothing wrong, and suppressing them would have fixed nothing. Dee adds the DKIM records the new tool gives her, so it signs with d=lighthouse-letterpress.example. She leaves the old tool's selector in place until nothing sends from it. Her next test shows dmarc=pass, and she checks her policy with the free DMARC checker.
Who we are
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. Check your records with our free tools. The SPF checker at reviewmyemails.com/tools/spf-checker counts your lookups and names what is included. The DMARC checker at reviewmyemails.com/tools/dmarc-checker reads your policy and alignment. Paste a header into the email header analyzer at reviewmyemails.com/tools/email-headers, or a whole raw message into the email source analyzer at reviewmyemails.com/tools/email-source-analyzer. Cleaning your list will not fix a failed check, because the addresses are not the problem. Still stuck? 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
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 lines= tag of a DKIM signature that tells the receiver where to find your keyFounded in 2020, based in Bolton, United Kingdom.
reviewmyemails.com/resources/why-did-email-authentication-fail?c=web-p10-r16pdf · v1
Spotted something out of date?