Check a domain's DMARC record online: fetches _dmarc TXT, explains every tag (p, sp, pct, rua, ruf, adkim, aspf, fo, ri), and flags p=none, missing rua, pct below 100, unauthorized external report addresses and duplicate records. Free, no signup.
_dmarc.<domain> is fetched.sp= tag then applies).rua/ruf address on another domain, the checker looks for the <your-domain>._report._dmarc.<their-domain> record that authorizes it (RFC 7489 section 7.1). Without it, receivers may drop your reports.Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
A single TXT record at _dmarc.yourdomain.com that starts with v=DMARC1. Subdomains without their own record inherit the organizational domain's policy (sp= if set, otherwise p=).
Only long enough to read a few weeks of rua aggregate reports and fix any legitimate sender that fails SPF or DKIM alignment. Then move to p=quarantine (optionally with pct) and on to p=reject. Google and Yahoo bulk-sender rules require a DMARC record, and p=none does not stop spoofing.
To stop people sending reports to a mailbox they do not own, RFC 7489 requires the receiving domain to publish yourdomain._report._dmarc.theirdomain TXT "v=DMARC1". DMARC report services usually publish a wildcard for you; if it is missing, reports may be dropped.
They set alignment mode. Relaxed (r, default) lets a subdomain match the From domain; strict (s) needs an exact match. Most domains should keep relaxed.
Usually not. Most large mailbox providers never send failure reports, and the ones that do may include message content. Aggregate rua reports are what you need.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.