DMARC Checker

How to read your DMARC results

DMARC is the policy layer that makes SPF and DKIM enforceable. It tells receiving servers what to do with mail that fails authentication and sends you reports on everyone sending as your domain. Since Google and Yahoo's 2024 sender requirements, it's no longer optional for anyone sending at volume.

Your policy level

The p= tag is the heart of the record. p=none monitors only — useful at first, but it protects nothing. p=quarantine diverts failing mail to spam, and p=reject blocks it. The goal is to climb from none to reject as your reports confirm every legitimate sender passes.

Reporting address

A rua= tag tells receivers where to send aggregate reports. Without it, you're flying blind — you can't see which services send as your domain or whether they pass authentication. We flag a missing reporting address because it's the single most useful thing DMARC gives you during setup.

Enforcement percentage

A pct= below 100 applies your policy to only a fraction of mail. It can be handy when rolling out a strict policy gradually, but most domains should run at 100 for full coverage.

DMARC depends on SPF and DKIM

A DMARC policy only does its job if SPF and DKIM are correctly configured underneath it. Check both with the SPF checker and DKIM checker, or run the combined deliverability test to see all three at once.

We set DMARC to enforcement and monitor the reports across every sending domain we manage. See how our cold email infrastructure is built, or read the full SPF, DKIM & DMARC guide for cold email.