A DMARC failure looks alarming in a report, but it almost always comes down to one of a few well-understood causes. This guide explains what “failing DMARC” really means, then walks through each cause and its fix — in the order worth checking them.
The one rule behind every DMARC failure
A message passes DMARC when either SPF or DKIM does two things at once:
- Authenticates — the check itself passes, and
- Aligns — the domain it authenticated matches your
From:domain.
If neither SPF nor DKIM manages both, the message fails DMARC. That’s it. Every “dmarc fail” you’ll ever see is some version of authentication broke, or authentication passed but didn’t align. The second one trips up almost everyone, so start there.
”SPF pass but DMARC fail” — the alignment trap
This is the single most common confusion. Your report shows SPF pass, yet DMARC fails. How?
SPF authenticates the envelope sender — the MAIL FROM address
the sending server offers in the SMTP conversation, which reaches the mailbox as
Return-Path if it is visible at all. It is not the From: address your
recipients see. Send through a marketing platform or ESP and the envelope is
usually a domain of the platform’s own — sendgrid.net, say, until you set up a
bounce domain of yours — while your From: stays you@yourdomain.com. SPF
passes for their domain — but that domain doesn’t
align with yours, so it earns you nothing under
DMARC.
Fix: get alignment, not just authentication. Either
- configure a custom Return-Path / bounce domain on your sending platform (usually a CNAME on a subdomain of yours), so SPF authenticates your domain, or
- rely on aligned DKIM instead (below) — often the easier path with ESPs.
You only need one aligned mechanism, so a correctly aligned DKIM signature makes the SPF-alignment problem moot.
Cause 1 — a sending service you never authorized
If a legitimate service (CRM, help desk, invoicing tool, newsletter) sends as your domain but you never set it up for authentication, it will fail. Every such source shows up in your aggregate reports.
Fix: for each real source, add its SPF include: and publish its DKIM key
(most providers give you a selector and a CNAME/TXT to add). Then confirm it
aligns to your From: domain.
Cause 2 — SPF is broken
Even when SPF should align, the record itself can fail:
- Too many DNS lookups. SPF allows a maximum of 10 terms that query DNS;
the eleventh is a
permerror, which counts as a failure. Chainedinclude:s blow past this. SPF record syntax covers which terms cost a lookup and how to total them, and the SPF record checker expands a record term by term. - More than one SPF record. A domain must have exactly one
TXTSPF record. Two records is also apermerror. - A missing sender. The sending IP simply isn’t covered by any mechanism.
Fix: keep a single record, get the lookup count to ten or below, and make
sure every real sender is represented. Prune the include:s for services you no
longer send through first, then give a heavy sender its own subdomain, which
comes with its own budget. A subdomain only buys you anything once that sender’s
Return-Path actually uses it — moving the include: by itself authorizes
nothing — and it stays aligned because DMARC accepts any subdomain of yours by
default; aspf=s turns that off and demands an exact match. Replacing an
include: with the ip4: and ip6: ranges behind it — “flattening” — gets you
under the limit too, but you have taken on the maintenance: those ranges are the
provider’s to renumber without telling you, and an IPv6 range you left out of
the copy fails SPF for every message the provider sends from it — survivable on
mail that also carries an aligned DKIM signature, not on mail that doesn’t.
Example of a clean record:
v=spf1 include:_spf.google.com include:sendgrid.net -all
Cause 3 — DKIM isn’t signing (or is signing wrong)
DKIM fails when the signature can’t be verified: the key isn’t published, the selector is wrong, the provider isn’t signing at all, or the message was modified in transit (some mailing lists rewrite bodies and break the signature).
Fix: publish the exact selector record your provider specifies — find your
DKIM selector covers digging it out of a
message you already have, and the DKIM record checker
reads back what is published — confirm the provider has DKIM enabled (it’s
often off by default), and check that the
signature’s d= domain aligns with your From: domain. Aligned DKIM is the
most robust way to pass DMARC because, unlike SPF, it survives most forwarding.
Cause 4 — forwarding
Auto-forwarded mail — someone forwards from @yourdomain to a personal Gmail —
breaks SPF, and it is worth being precise about why, because the usual
explanation is backwards.
Plain forwarding breaks SPF because the envelope doesn’t change. The forwarder
relays your original MAIL FROM from its own IP address, and
that IP is not in your SPF record, so the check fails. Nothing was rewritten;
that is the problem.
Forwarders that do rewrite the envelope — the technique is called SRS — make SPF pass, for their domain. Which then fails alignment, because the domain that passed is no longer yours. So SRS is not a fix for DMARC either; it just moves the failure one step along.
Some forwarders also modify the message — a footer, a rewritten subject — which breaks DKIM on top. Either way the result is a DMARC failure for mail you did legitimately send.
Fix: there’s no perfect fix, but aligned DKIM survives forwarding that doesn’t modify the message, and ARC lets participating receivers honor a prior “pass” — read what it does and doesn’t buy before relying on it. Don’t tighten your policy based on forwarding failures alone: they never reach zero, so waiting for them to is not a plan.
Cause 5 — a subdomain with no record
Mail from news.yourdomain.com is governed by that subdomain’s DMARC — or, if
it has none, by your organizational policy’s subdomain tag (sp=), or by p=
itself when no sp= is published. A forgotten subdomain sending unauthenticated
mail will fail either way.
Fix: publish DMARC (and SPF/DKIM) on active subdomains, and treat sp= on your
main policy as the exception rather than the default —
subdomains already inherit p=. For names that don’t resolve at all, np= covers
them specifically; the tag reference has both.
How to diagnose which one it is
Don’t guess — the answer is in the data. DMARC aggregate reports list every source sending as your domain and show, per source, whether SPF and DKIM authenticated and whether they aligned. Read the DKIM column first: one aligned pass is the whole test, so a source whose SPF passes unaligned beside an aligned DKIM signature is not failing and is not a cause. For the sources that did fail, that two-by-two (auth × alignment) tells you which one applies:
- SPF pass but not aligned → the alignment trap, above. Don’t recognize the source? Identify it before you authorize it — an unaligned pass fits someone spoofing you as well as it fits a service a colleague signed up for, and only the second one is Cause 1
- SPF permerror → Cause 2
- DKIM fail or no signature → Cause 3
- Passes for known mail but fails only on forwarded paths → Cause 4
- A
header_fromon a subdomain you weren’t thinking about → Cause 5. Every record carries theFrom:domain it was counted against, so a forgotten subdomain names itself
Learn to read them in how to read a DMARC aggregate report.
One report is one receiver’s view of one day, and most of these causes only separate out over a run of them — a source failing everywhere looks nothing like a source failing on one path. Keeping that comparison going across every source and every domain is the job DMARC Analyzer does, self-hosted.
Quick checklist
- Is at least one of SPF or DKIM aligned to your
From:domain? - Exactly one SPF record, at 10 DNS-querying terms or fewer?
- DKIM enabled at every provider, with the correct selector published?
- Every legitimate sender in your reports accounted for?
- A deliberate
sp=and records on active subdomains?
What next
Once failures are down to only the sources you expect, you’re ready to move from monitoring toward enforcement — safely, in stages. See from monitoring to enforcement, and if you haven’t yet, publish your first DMARC record in monitoring mode first.
On this page
- The one rule behind every DMARC failure
- ”SPF pass but DMARC fail” — the alignment trap
- Cause 1 — a sending service you never authorized
- Cause 2 — SPF is broken
- Cause 3 — DKIM isn’t signing (or is signing wrong)
- Cause 4 — forwarding
- Cause 5 — a subdomain with no record
- How to diagnose which one it is
- Quick checklist
- What next
On this page
- The one rule behind every DMARC failure
- ”SPF pass but DMARC fail” — the alignment trap
- Cause 1 — a sending service you never authorized
- Cause 2 — SPF is broken
- Cause 3 — DKIM isn’t signing (or is signing wrong)
- Cause 4 — forwarding
- Cause 5 — a subdomain with no record
- How to diagnose which one it is
- Quick checklist
- What next