Skip to content
HEED Data Supply
Domain protection • HEED INSIGHTS

DMARC Alignment: Audit the Identity, Not the Green Badge

An authentication pass for somebody else’s domain is not the result your From address needs.

01 / Domain protection

What does DMARC alignment add to authentication?

DMARC connects a passing authentication result to the domain visible in the message’s From address. A message can pass SPF or DKIM for another identity without satisfying that connection. Inspect the identifiers and alignment mode, rather than treating a green authentication badge as proof that every domain relationship is correct.

RFC 7489 permits DMARC success through aligned, passing SPF or aligned, passing DKIM. Strict alignment requires an exact domain match; relaxed alignment compares organizational domains. The example below uses relaxed alignment and the reserved example.com domain. It is a diagnostic model, not a statement about a production sender.

Receiving-provider requirements are a separate layer from the DMARC pass algorithm. Do not assume that satisfying one protocol check satisfies every policy imposed on your traffic. Save actual message headers and the applicable provider requirements before deciding whether the sender configuration is ready.

Sources: RFC 7489: DMARC identifier alignment

02 / Domain protection

How do three messages reveal alignment mistakes?

Compare the visible From domain with the SPF-authenticated envelope domain and the DKIM signing domain. Record both pass status and alignment for each mechanism. Under the stated mode, one passing aligned mechanism can satisfy DMARC, while two passing but unrelated identities can still leave the message failing that check.

In the first hypothetical message, From is sales@example.com and SPF passes for bounce.example.com. Under relaxed alignment those domains align, so SPF can provide DMARC success. In the second, SPF passes for vendor.example.net while DKIM passes with d=example.com; aligned DKIM supplies the success instead.

In the third message, both SPF and DKIM pass only for vendor.example.net while From remains example.com. Neither identity aligns, so those results do not produce a DMARC pass. Real evaluation also needs valid records and applicable protocol handling; the table isolates the identity question.

Hypothetical relaxed alignment; visible From domain is example.com
MessagePassing SPF domainPassing DKIM d=Aligned mechanism
Abounce.example.comNoneSPF
Bvendor.example.netexample.comDKIM
Cvendor.example.netvendor.example.netNeither

Sources: RFC 7489: DMARC identifier alignment

03 / Domain protection

What should a RevOps owner request from the administrator?

Request an identity worksheet per sending service and message headers showing the result. Keep protocol success, receiver requirements and campaign permission as separate gates. Authentication checks can expose a configuration error; they do not establish that a researched contact wants the message or that the message will reach an inbox.

For each service, record the visible From domain, envelope domain, DKIM signing domain, selector, alignment mode and administrator. Compare results after any vendor or domain change. A worksheet with three real messages is more useful than a screenshot showing one isolated pass badge without the identifiers.

Use the same discipline for the audience file: preserve evidence about the person, role and checked date rather than relying on a generic verified label. HEED’s B2B research scope concerns the contact deliverable. Your sending-domain configuration and proposed use remain separate responsibilities.

  • Preserve complete test headers in the internal change record.
  • Verify the alignment mode before interpreting subdomain matches.
  • Keep DNS-policy changes under the domain owner’s review.

Sources: RFC 7489: DMARC identifier alignment · HEED B2B research scope

Define a B2B research briefSpecify the audience, required fields and exclusions before choosing a batch.

QUESTIONS

Common questions

Must both SPF and DKIM align for DMARC to pass?

DMARC can pass through either passing aligned mechanism. A receiving provider may separately require both mechanisms to be configured for certain traffic, so check that policy too.

Should every team immediately set p=reject?

No universal policy change follows from this example. Inventory legitimate senders and evaluate actual reports with the administrator before selecting or changing enforcement.

Sources

  1. RFC 7489: DMARC identifier alignment
  2. HEED B2B research scope
KEEP READING