SPF Passes but DMARC Fails? DMARC Alignment Explained

SPF passes but DMARC fails: DMARC alignment explained – InboxWizards guide

Written by

in

Your email headers show spf=pass. Maybe dkim=pass as well. And yet dmarc=fail. It looks contradictory, but it’s one of the most common results we see, and it comes down to one idea: alignment.

Passing isn’t the same as aligning

SPF and DKIM each check a domain, but not necessarily the domain your recipient sees.

  • SPF checks the Return-Path (also called the envelope sender or bounce address), a hidden address used for bounces.
  • DKIM checks the domain in the signature’s d= tag, which is whoever signed the email.
  • DMARC cares about the From address, the one people actually see.

DMARC passes only when SPF or DKIM passes and the domain it passed for matches the From domain. That match is alignment.

A typical example

You send a newsletter from [email protected] using an email marketing platform. The headers show:

Return-Path: [email protected]
DKIM-Signature: d=platform-example.com; s=k1
From: [email protected]

spf=pass (mail.platform-example.com)
dkim=pass (platform-example.com)
dmarc=fail (yourdomain.co.uk)

Both checks passed, but for the platform’s domains, not yours. Neither aligns with yourdomain.co.uk, so DMARC fails. In your DMARC reports this shows up as SPF and DKIM passing under auth_results but failing under policy_evaluated.

Relaxed vs strict alignment

Your DMARC record controls how closely the domains must match, with aspf for SPF and adkim for DKIM:

  • Relaxed (r, the default): subdomains count. DKIM signed by mail.yourdomain.co.uk aligns with a From address at yourdomain.co.uk.
  • Strict (s): the domains must match exactly.

Most businesses should stay on relaxed. Strict alignment breaks easily and adds little protection for most senders.

How to fix it

Fix DKIM first

Set up custom DKIM in every platform that sends as your domain: it’s usually called “domain authentication” or “branded sending domain”. Once the signature reads d=yourdomain.co.uk, DKIM aligns. This is the most reliable fix, because DKIM survives forwarding and SPF doesn’t. See why DKIM fails if it doesn’t verify.

Add a custom Return-Path if you can

Many platforms let you set a custom bounce domain, such as bounce.yourdomain.co.uk. With relaxed alignment, SPF then aligns too, which gives you a second route to DMARC passing.

Watch for forwarding

When email is forwarded, SPF usually fails because the forwarding server isn’t in your SPF record. Aligned DKIM is what keeps forwarded mail passing DMARC.

A note on the 2026 DMARC update

The updated DMARC standard published in 2026 (RFC 9989) changes how receivers work out your organisational domain, replacing a published list of domain suffixes with a lookup of DMARC records up your domain tree. For a typical business with a DMARC record at _dmarc.yourdomain.co.uk, alignment works exactly as before. Keep a DMARC record on your main domain and you’re covered.

Why it matters

Until every legitimate sender aligns, you can’t safely move your DMARC policy beyond p=none. Once you do, Gmail and Microsoft will start rejecting or junking the senders that don’t.

Get every sender aligned

Send a test email to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass for your domain, or let our DMARC service find every platform sending as your domain and get each one aligned before you move to enforcement.

5.0 from 12 Google reviews