Skip to content
Technical guide

Understanding DMARC

DMARC connects the visible sender domain to SPF or DKIM. A published DNS record alone does not prove that a message is correctly authenticated.

What is checked?

The check examines the published DMARC policy and its reporting destinations. A message passes DMARC when at least one successful SPF or DKIM check aligns with the visible From domain. p=none requests observation rather than quarantine or rejection due to DMARC.

Worked example

Synthetic example using a reserved domain and documentation addresses. Adapt the domain, addresses and services to your infrastructure before using it.

_dmarc.example.test. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.test"

This policy requests aggregate reports for example.test. The mailbox must be configured. An external reporting destination also requires checking its DNS authorization.

Common mistake

Classifying your own IP as authorized does not change message authentication. An SPF pass for an unrelated Return-Path domain does not satisfy DMARC alignment.

Recommended next step

Review reports by legitimate sending path. Compare the actual From domain, SPF domain and DKIM signature for affected sources, then correct the sending service. Assess the impact before choosing a stricter policy.

What the result does not prove

DNS shows a published policy. Message evidence or receiver reports are needed to establish whether a message passes SPF or DKIM and aligns with the From domain. DMARC does not guarantee delivery.

Check your domain

Start without signing in. History and alerting require a verified domain and an available account.