DMARC Troubleshooting

Why DMARC fails even when SPF or DKIM passes

Understand domain alignment, read authentication results and fix sender identity mismatches without weakening your email security.

Practical email deliverability guide

Clear explanations, real-world troubleshooting steps, and the checks that matter before you change your sending configuration.

What a DMARC alignment failure actually means

Seeing spf=pass or dkim=pass in a message header can look reassuring. But DMARC has an additional requirement: at least one authenticated domain must align with the domain shown to the recipient in the visible From: address. A message may therefore pass SPF or DKIM while still receiving dmarc=fail. This guide shows how to investigate that discrepancy without changing DNS records blindly.

Think of authentication and alignment as two separate questions. Authentication asks whether a domain authorized or signed a message. Alignment asks whether that authenticated domain is connected to the address the recipient sees. DMARC passes when either SPF or DKIM both passes authentication and aligns; it does not require both mechanisms to pass.

Read the three domains before editing DNS

Start with the actual delivered message. Open its full headers, then identify these domains:

  1. Header From: the address shown to recipients, such as news@example.com.
  2. Envelope sender / Return-Path: the domain used for SPF, sometimes an ESP-controlled bounce domain such as bounces.vendor.example.
  3. DKIM signing domain: the d= value in a valid DKIM-Signature, such as mail.example.com.

Read the receiver's Authentication-Results header to see what it concluded. Do not assume the first Authentication-Results line was added by your final recipient's mailbox provider; messages can contain multiple such headers from different hops.

Example
From: Updates <news@example.com>
Return-Path: <bounce@mailer.vendor.test>
Authentication-Results: mx.receiver.test;
  spf=pass smtp.mailfrom=mailer.vendor.test;
  dkim=pass header.d=mailer.vendor.test;
  dmarc=fail header.from=example.com

Both authenticated identities belong to vendor.test, while the visible From domain is example.com. They do not align; neither pass can satisfy DMARC for example.com. Domains shown here are illustrative.

Relaxed vs strict alignment

DMARC has separate SPF and DKIM alignment modes: aspf and adkim. Unless the published DMARC policy sets them to s, the defaults are relaxed (r). Under relaxed alignment, subdomains can align when they share the same organizational domain. Under strict alignment, the authenticated domain must match the Header From domain exactly.

Header FromAuthenticated domainRelaxedStrict
example.commail.example.comCan alignDoes not align
example.comexample.comAlignsAligns
example.comvendor.testDoes not alignDoes not align

This explains why a previously working subdomain may start failing when alignment settings are tightened. Domain boundaries also depend on the public suffix list, so don't reduce every case to simply matching the final two labels.

Check SPF alignment without creating extra SPF records

SPF validates the sending IP against the domain used in the SMTP envelope, generally the smtp.mailfrom identity. It does not directly authenticate the visible From address. If your email platform uses its own bounce domain, SPF can pass but fail alignment. Configure a provider-supported custom return-path or bounce domain under your organizational domain when available.

Keep one SPF TXT policy per hostname and merge authorized senders into that record carefully; multiple competing SPF records can produce permerrors. Do not add an unrelated server hostname or a broad +all rule just to make a test green. Any change should follow your sending provider's exact DNS instructions, and should be verified after DNS propagation.

Check DKIM alignment and selector setup

DKIM signs selected message headers and body content with a private key; the receiver verifies against the public key at selector._domainkey.signing-domain. A cryptographically valid signature is not necessarily aligned. Compare the valid DKIM signature's d= domain with the Header From domain. If your platform signs with its own domain, enable custom-domain DKIM signing if supported.

For example, a DKIM signature using d=mail.example.com may align in relaxed mode with a From address at example.com. A signature using d=service.vendor.test will not. A message can also carry several DKIM signatures; only one valid and aligned signature is needed for DKIM to satisfy DMARC. Verify selector DNS values and use the correct key for the specific sending system.

A safe six-step troubleshooting workflow

  1. Capture one fresh sample: send to a mailbox where you can view full headers; save the time, message ID, and exact sender address.
  2. Confirm the receiver's DMARC verdict: locate trusted Authentication-Results lines and identify the Header From domain.
  3. Compare identities: note SPF smtp.mailfrom, all passing DKIM header.d values, and the published adkim/aspf modes.
  4. Fix the right mechanism: request provider-supported custom DKIM or return-path configuration; avoid unrelated DNS edits.
  5. Send another test: recheck authentication and alignment using a fresh message rather than expecting historical reports to change.
  6. Monitor the results: inspect DMARC aggregate reports, bounce patterns, and mailbox-provider diagnostics over time. If failures persist, give your provider sanitized headers and the sending account's configuration details.

Do not paste account passwords, API keys, private DKIM keys, or customer email content into support tickets or public tools. Redact identifiers as needed but preserve the domain relationships and relevant headers.

DMARC policy isn't the same as placement

A DMARC pass establishes that the message met an alignment rule; it does not promise inbox placement. Providers also assess abuse signals, user complaints, message quality, sending patterns and engagement. Conversely, a DMARC fail can lead to different treatment depending on policy and receiver handling; the p= value in DNS requests handling but doesn't dictate every receiver's final outcome.

If your domain has a strict rejection policy, correct genuine authentication issues promptly. Do not weaken the policy in production simply to mask a faulty sender. Coordinate policy changes with the domain owner and review aggregate reporting before tightening enforcement.

Frequently asked questions

Why does DKIM pass but DMARC fail?

The signing domain may be different from the visible From domain. Check header.d and the published adkim setting. Another possibility is that the passing signature belongs to an unaligned forwarding or intermediary service.

Do SPF and DKIM both need to pass DMARC?

No. DMARC passes when either SPF or DKIM both authenticates successfully and aligns with the Header From domain.

Does changing the DMARC record fix authentication?

No. The DMARC record publishes policy and alignment preferences. Repair SPF authorization or DKIM signing identities at the sending system; validate the result with fresh headers.

Will email warmup repair a DMARC failure?

No. Warmup can help you manage an appropriately gradual sending process, but DNS and message authentication must be configured correctly first.

Warm up only after your mail authentication is ready

InboxWarmup supports a measured, manual sending warmup process. Correct DNS and sending-provider configuration first; no warmup service can guarantee inbox placement.

Explore InboxWarmup plans