← All tools
DMARC Record Checker
Enter a domain to read its DMARC record and see whether it actually protects the domain, whether reports are being collected, and what to change next on the road from p=none to p=reject.
What this does - and doesn’t - tell you
What’s checked
- Whether a DMARC record exists at _dmarc and whether there's exactly one
- The policy (none, quarantine or reject) and the subdomain policy
- Reporting: whether a rua= address is set so you receive aggregate reports
- Alignment mode, the percentage the policy applies to, and weak spots such as sp=none
Worth knowing
- Gmail and Yahoo require a DMARC record from bulk senders, but p=none satisfies that - it only monitors. Real protection starts at quarantine.
- Moving to enforcement safely means reading the reports first. Our guide to the p=none to p=reject rollout walks through it.
- A subdomain without its own record inherits the parent domain's policy; this checks the exact name you enter.
Moving to p=reject without breaking legitimate mail takes a careful read of the reports. We do that rollout for you.
How we help: Consulting · Private infrastructure · Managed mailboxes · Monthly support