How DMARC works

DMARC is defined in RFC 7489. A domain publishes a TXT record at _dmarc.example.com:

_dmarc.example.com.  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com; adkim=r; aspf=r"

When a message arrives with example.com in its From: header, the receiver looks up this record and runs two checks:

  1. Did SPF pass, and does the envelope sender (MAIL FROM) domain align with the From: domain?
  2. Did DKIM pass, and does the signing domain (d=) align with the From: domain?

If either answer is yes, the message passes DMARC. If both are no, the receiver applies the policy in the p= tag. The most useful tags are:

  • p=: the policy for failing mail (none, quarantine, or reject).
  • sp=: an optional, separate policy for subdomains.
  • rua=: where to send aggregate reports.
  • adkim= and aspf=: alignment mode, r (relaxed) or s (strict).
  • pct=: the percentage of failing mail the policy applies to, used for gradual rollouts.

Why alignment is the key concept

SPF and DKIM on their own authenticate a domain, but not necessarily the domain the recipient sees. An attacker can send mail that passes SPF for a domain they own while putting your domain in the From: header. DMARC closes this gap by requiring the authenticated domain to match the From: domain.

In relaxed mode, the default, mail.example.com aligns with example.com because they share the same organizational domain. In strict mode they must match exactly. Relaxed alignment suits most organizations, since ESPs commonly sign or send from a subdomain.

Reading DMARC aggregate reports

If you specify a rua address, participating mailbox providers send aggregate XML reports, typically once a day. Each report lists the sending IPs that used your domain, how many messages each sent, and whether SPF and DKIM passed and aligned. Raw XML is hard to read, so most teams use a report-processing service or parser.

Reports are how you find the senders you forgot about, such as a billing system, an old marketing tool, or a partner sending on your behalf, along with anyone spoofing your domain. Fix every legitimate source before you tighten the policy. If reports go to a mailbox on a different domain, that domain must publish a DNS record authorizing it to receive them.

Why DMARC is now a requirement

Google’s sender guidelines, enforced since February 2024, require bulk senders to publish a DMARC record (a policy of p=none is accepted) and to align the From: domain with SPF or DKIM. Yahoo introduced matching requirements at the same time, and Microsoft announced similar rules for high-volume senders to Outlook.com consumer addresses in 2025. Bulk mail from a domain without DMARC can be filtered or rejected regardless of content.

Monitoring alone is not protection, though. A domain at p=none can still be spoofed. In our DMARC and SPF adoption study of 214 well-known company domains, 98.6% published a DMARC record and 92.4% of those had moved to quarantine or reject. Large organizations treat enforcement as the goal, not an optional extra.

How to roll out DMARC safely

  1. Set up SPF and DKIM first, using your own domain for the DKIM signature and the return-path wherever your providers allow it.
  2. Publish p=none with a rua address and collect reports for at least a few weeks.
  3. Fix every legitimate sender that fails alignment.
  4. Move to p=quarantine, optionally with a lower pct= value at first, then raise it to 100.
  5. Move to p=reject once reports show legitimate mail consistently passing.
  6. Keep monitoring. New tools and vendors get added over time, and each one needs to be authenticated before it sends.

Reaching enforcement also makes your domain eligible for BIMI, which can display your logo in supporting inboxes.

Where RocketVerifier helps

The free email deliverability checker reads your DMARC, SPF, and DKIM records and highlights missing or weak settings. Authentication is one half of the bulk-sender rules; the other is keeping bounces and complaints low, which is where bulk email verification and ongoing deliverability monitoring fit in.