Blazalek.com

How to check DMARC alignment in Authentication-Results

An email can show SPF pass, DKIM pass, and DMARC fail in the same header, because each pass belongs to a domain that may not be the one in From. DMARC requires at least one authenticated identity to align with the author domain. This walkthrough isolates each result, checks it against the author domain under strict alignment, and shows what a valid fix looks like.

By

On this page

To check DMARC alignment in an Authentication-Results header, identify the exact domain validated by each passing mechanism and compare it with the domain found in the visible From header. A passing SPF or DKIM verdict attaches to a specific authenticated identifier, and that domain does not automatically match the author domain in From. DMARC passes only when at least one passing check aligns with that author domain. A pass on one path can’t lend its authentication to a matching domain on the other path. The analysis below assumes a single author domain, a discovered DMARC policy, and an evaluation that reached a definitive result, following the standard decision procedure in RFC 9989.

You only need one passing and aligned path for DMARC to succeed; SPF and DKIM do not both need to align (identifier alignment). The following sections break down that comparison using a controlled synthetic example.

Which Authentication-Results field can you trust?

Always inspect the complete, raw headers of the received email. You must know which Authentication-Results field was written by a host the recipient mailbox system actually trusts. A plausible service name in that field says nothing about where it came from. If you can’t tell which receiving gateway wrote the header, check with the recipient’s mail admin before trusting the output. That is my diagnostic recommendation, and it follows from the header’s own trust requirements.

Next, check the alignment modes in effect during message evaluation. The aspf tag governs SPF alignment, while the adkim tag controls DKIM alignment. Both settings default to relaxed (r), whereas strict (s) mode requires an exact domain match with case differences ignored. A lone fail token never indicates whether the receiver applied relaxed or strict alignment (alignment-mode tags). If you want to review the core mechanics first, consult the guide on what DMARC alignment means.

Two passes and no strict match

Here is a header snippet with the reserved domains example.com and example.net that shows how alignment works in practice. It’s an incomplete fragment with invented results, not a message anyone observed and not a test that was cryptographically reverified.

For this walkthrough, assume a standard message with a single From author and a valid, non-empty MAIL FROM address. The destination environment trusts mx.example.net as its evaluation gateway. The author domain publishes a valid DMARC policy specifying strict modes aspf=s and adkim=s. Both policy discovery and authentication checks run to completion without error, and the single DKIM signature displayed is the only signature on the message. These are premises I’m supplying: the fragment itself proves neither the policy modes nor the evaluator’s trustworthiness.

From: Operations notices <notices@ops.example.com>
Return-Path: <batch-42@returns.ops.example.com>
Authentication-Results: mx.example.net;
    spf=pass smtp.mailfrom=returns.ops.example.com;
    dkim=pass header.d=example.com header.s=ops2026;
    dmarc=fail header.from=ops.example.com

The author domain to test against is ops.example.com. It comes from the From header and appears in the evaluation summary as header.from (DMARC result identity).

For SPF, locate the smtp.mailfrom domain tied to spf=pass. DMARC evaluates the envelope identity from MAIL FROM, which means a separate HELO pass cannot satisfy this path. The Return-Path header corroborates that domain here, though it does not replace a genuine SMTP session log or trusted evaluation output. (Empty bounce paths fall outside this walkthrough.) See the RFC 7208 definition of the MAIL FROM identity and the RFC 9989 rules on identifier alignment.

For DKIM, header.d is the signing domain from d=, and it applies only to the DKIM result it sits next to. The entry header.s=ops2026 identifies the selector; neither that selector in header.s nor the agent identifier in header.i serves as the comparison domain for DMARC. RFC 8601 outlines these authentication result properties, while RFC 6376 covers DKIM signature tags.

What to compareEvidence in this synthetic fragmentUnder the supplied strict modesContribution to DMARC
Author domainFrom and header.from: ops.example.comTarget for both comparisonsIdentifies the author domain; doesn’t itself prove authorization
SPF-authenticated domainspf=pass for returns.ops.example.comaspf=s: different from ops.example.comNo aligned SPF pass
DKIM-authenticated domaindkim=pass for example.comadkim=s: different from ops.example.comNo aligned DKIM pass

Neither check matches the domain exactly. Under strict alignment, parent domains and subdomains don’t match the author domain, so dmarc=fail is the expected result. Both underlying checks passed, but neither yielded an aligned identifier under the DMARC decision procedure.

RFC 9989 uses DNS Tree Walk to determine the organizational domain (checked 8 September 2026, standard published May 2026). Two domains with the same ending do not automatically share an Organizational Domain, and a record published at the author domain doesn’t automatically make that domain the Organizational Domain. I’m describing the current specification here, not asserting that any particular receiver has adopted it. No discovery evidence has been supplied to decide this example under relaxed mode, and switching the modes is not the repair being proposed (Organizational Domain discovery).

What a successful change would look like

Keep the same author domain, strict alignment settings, and unaligned SPF envelope address. Now suppose the sender signs directly as d=ops.example.com, and the receiving gateway verifies that signature as authentic. The relevant output lines become dkim=pass header.d=ops.example.com and dmarc=pass header.from=ops.example.com. The verified signing domain now matches the author domain, allowing DMARC to pass on this path alone (identifier alignment). This is a conditional verification target for a separately generated synthetic message: no repair has been performed and no result has been observed.

Now look at what happens if that signature fails verification. Suppose another test message carries that same matching signing domain but produces dkim=fail. Because SPF remains unaligned and no other aligned signature exists, DMARC still fails. A matching domain string cannot replace a passing cryptographic validation. These facts don’t tell you why DKIM failed. Altering d= on a previously captured message or modifying Authentication-Results text in a mailbox does not resolve anything; fixing the stream requires valid cryptographic signing on new outbound messages and fresh receiver verification (DMARC decision procedure).

What to preserve from the received message

Treat this as a read-only diagnostic step: preserve the complete source, the trusted result/domain pairs and the modes that applied at evaluation time. Current DNS records cannot prove what an earlier evaluation observed, a limitation RFC 7208 highlights regarding evaluation timing and later policy changes. When sender identity or policy context is incomplete, contact the relevant sending or receiving administrator for verification.

If the header analysis contradicts the reported DMARC verdict, verify that the email source is complete and evaluate every DKIM signature independently, as any valid aligned signature satisfies the requirement. Keep a missing applicability or an incomplete evaluation apart from an ordinary alignment failure: none, temperror, and permerror are not interchangeable with fail (DMARC decision procedure).

A subsequent passing test validates only the specific route tested, not every sender across the organization. Passing DMARC does not guarantee inbox delivery or message safety, and a failure on its own proves neither rejection nor malicious intent (DMARC result limits). For a complete troubleshooting walkthrough, open the DMARC alignment incident guide.

Frequently asked questions

Do SPF and DKIM both have to align for DMARC to pass?

No. A single passing authentication path that aligns with the author domain satisfies DMARC. You do not need both SPF and DKIM to align for the message to pass.

Which domain does DMARC compare on the DKIM path?

The d= domain reported in the header.d field. Receiving servers evaluate the domain that signed the message, ignoring the selector in header.s and the optional identity in header.i.

Which domain does DMARC compare on the SPF path?

The envelope domain reported in the smtp.mailfrom parameter. DMARC checks the bounce address from MAIL FROM rather than a HELO identity or the visible From header.

Does a dmarc=fail result mean strict alignment was in effect?

No. SPF and DKIM alignment both default to relaxed mode unless a domain explicitly publishes strict tags. A failure token by itself never proves that strict mode was evaluated.

Can I fix alignment by editing headers on existing messages?

No. Rewriting headers on an already delivered email won’t fix anything. You have to configure the sending service to sign new outbound messages with the aligned domain.

Email deliverability consultant

Get a second opinion on your email setup

Tell me what your customers are seeing or what you’re planning to change. In 30 minutes, we’ll work out what your team can check first and whether a deliverability audit would help.

I led deliverability at GetResponse, designed a dedicated newsletter system for Easy.Tools and helped Youmoney migrate its automated emails in stages. Read the case studies

Book free call

Email deliverability audit

See what I check and read a sample report with recommendations for your team.