Every DMARC tag, explained, and why each one matters
A DMARC record is a single line, but every tag changes how receivers treat your mail and what data flows back to you. This is the complete reference, with the significance of each.
ruf=mailto:fail@xmpl.example; adkim=s; aspf=r; pct=100; fo=1; ri=86400
The required tags
v=DMARC1Mandatory and must be first. Identifies the record as DMARC. A typo here means receivers skip the record entirely. That leaves you with no DMARC at all while the record appears configured.
p=the core decisionThe policy applied to mail that fails DMARC. This is the whole point of the record:
p=noneMonitoring: take no action. Where everyone starts, to gather data safely.p=quarantineSend failing mail to spam/junk. The first real enforcement step.p=rejectBlock failing mail outright. Full protection: the goal.Alignment tags: the heart of DMARC
These decide how strictly the authenticated domain must match your visible From. See alignment vs. authentication for the full picture.
adkim=DKIM alignment mode. r (relaxed, default) lets a subdomain’s signing domain align with the parent; s (strict) demands an exact match. Significance: strict blocks subdomain signers. Only use it once every sender signs with the exact From domain.
aspf=SPF alignment mode. Same r/s choice, applied to the envelope-from domain. Relaxed is almost always correct because many ESPs use their own envelope domain.
Reporting tags: your visibility
rua=essentialAggregate report address(es), as mailto: URIs. Without it you fly blind. These daily XML reports are how you discover every server sending as you. This is the address ClearDMARC parses to build your dashboards.
ruf=Forensic / failure report address(es). Receivers send a copy of individual failing emails here. Increasingly rare: most providers withhold RUF for privacy, so don’t rely on it.
fo=Failure-reporting options (controls when RUF is generated). 0 = only if both SPF and DKIM fail (default). 1 = if either fails (most useful). d = DKIM fail. s = SPF fail.
ri=Reporting interval in seconds (default 86400 = daily). A request, not a guarantee: most receivers send once per day regardless.
Scope and rollout tags
sp=Subdomain policy. Overrides p= for mail from subdomains. Significance: lets you run p=reject on the parent while keeping a looser policy on subdomains still being onboarded. Or, conversely, it lets you lock down unused subdomains attackers love to spoof. If omitted, subdomains inherit p=.
pct=Percentage of failing mail the policy applies to (1–100, default 100). Lets you ramp enforcement. For example, p=quarantine; pct=25 quarantines a quarter of failures while you watch for collateral damage. Important: pct affects only the action. Reports still cover 100% of mail.
To start safely you need only three things: v=DMARC1, p=none, and a rua= address. That gives full visibility without changing how your mail is delivered. Everything else is for tightening and ramping towards p=reject. For the full spec, see RFC 7489 explained.