How to read your DMARC record: tags, policies and common errors
A DMARC record is a single TXT entry at _dmarc.yourdomain.com, but each tag inside it changes how receivers treat mail that fails SPF or DKIM. The DMARC checker above reads every tag for you. The notes below explain what the results mean and what to change.
DMARC tags explained
| Tag | What it does | Common values |
|---|---|---|
| v | Version, must come first | DMARC1 |
| p | Policy for your main domain | none, quarantine, reject |
| sp | Policy for subdomains | Same as p if left out |
| pct | Share of failing mail the policy applies to | 100 by default |
| rua | Where aggregate reports are sent | mailto:reports@yourdomain.com |
| ruf | Where failure reports are sent | Rarely honoured by large providers |
| adkim / aspf | DKIM and SPF alignment mode | r (relaxed, default) or s (strict) |
Only v and p are required. Without rua you get no reports, which means you're making policy decisions blind.
DMARC policy: p=none vs quarantine vs reject
With p=none, receivers deliver failing mail as usual and only send you reports. It's the right start, and it meets the minimum Gmail and Yahoo set for bulk senders, but it doesn't stop anyone from spoofing your domain. p=quarantine asks receivers to put failing mail in spam, and p=reject asks them to refuse it outright. The safe route is to read your aggregate reports until every service that sends as your domain passes SPF or DKIM with alignment, then move to quarantine with a low pct, raise it to 100, and finish at reject. Our guide on DMARC reporting and monitoring tools helps with the reports part.
DMARC errors this checker finds
The most common result is "no DMARC record found": nothing is published at _dmarc, or it sits on the wrong host. Our walkthrough on fixing the "no DMARC record found" error covers the fix step by step. Other frequent problems are two DMARC records on one domain (receivers then ignore both), a typo in a tag name, a "DMARC policy not enabled" warning on domains stuck at p=none, and rua addresses on another domain that hasn't authorised them with its own _report._dmarc record. After you edit the record, allow for the old TTL before you check again, since resolvers may serve the cached version for a while. Alignment fails are harder to spot: SPF and DKIM pass, but for a different domain than the one in your From address, so DMARC still fails.
Next step: publish, then move to enforcement
No record yet? Create one in a minute with the DMARC Generator, then come back and check it here. If your record is in place, confirm SPF and DKIM with the SPF Checker and DKIM Checker, since DMARC passes only when one of them passes and aligns. Warmy's DMARC tracker reads your reports for you, shows which senders fail and tells you when it's safe to tighten the policy.
Get from p=none to p=reject without losing real mail. Start a free 7-day trial or book a demo.

























