DMARC CHECKER // POLICY + ALIGNMENT
DMARC Checker: Get to p=reject Without Quarantining Your Own Mail
A DMARC record is easy to publish and easy to get wrong: a typo in the rua address, a policy stuck at p=none for years, alignment failures nobody is reading about. The Inboxes DMARC checker validates the record and tells you when it is safe to tighten it.
Inbox placement
67%
··%
· ·
Authentication
checking 130+ blacklists
Sample data. Seed results are estimates, not guarantees.
What is a dmarc checker?
A DMARC checker validates the record at _dmarc.yourdomain and tells you what receivers will do with mail that fails authentication. Inboxes checks syntax, the policy (p=none, quarantine, or reject), rua reporting addresses, pct rollout percentage, and the adkim and aspf alignment modes, then grades where you sit on the progression: start at p=none to observe, move to quarantine once reports show your legitimate sources passing, and finish at reject to shut down spoofing. Because Inboxes also parses your aggregate reports, it can tell you when tightening is safe: no aligned-source failures for 30 days is a very different signal than no data at all. A correct DMARC record protects your domain and helps deliverability, but it is one factor among several, and no DNS record guarantees inbox placement.
// example DMARC record for example.com
_dmarc.example.com. 3600 IN TXT "v=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]; adkim=r; aspf=r" policy: quarantine | reporting: on | next: p=reject once sources hold aligned
A mid-progression record: quarantine at full volume, reports flowing, reject in sight.
What you get
Dmarc checker, done properly
Every tag, explained
p, sp, pct, rua, ruf, adkim, aspf: the checker reads each tag, flags misconfigurations like an unverified external rua domain, and says what the current combination actually does.
A staged path to reject
Jumping straight to p=reject quarantines your own forgotten senders. The checker maps the none, quarantine, reject progression against your real report data.
Alignment failures pinpointed
DMARC passes only when SPF or DKIM aligns with the From domain. Placement tests show exactly which seed mailboxes saw unaligned mail and why.
Gmail and Yahoo requirements covered
Bulk senders to Gmail and Yahoo must publish DMARC since 2024. The checker verifies you clear that bar, and how much further you can safely go.
How it works
From send to fix list in four steps
Fetch and parse the record
Inboxes reads _dmarc.yourdomain, validates every tag, and renders the policy in plain language.
Verify with live mail
A placement test confirms real messages pass DMARC, aligned, at all 6 providers on the board.
Watch the reports
Parsed RUA data shows every source sending as your domain and whether each one aligns.
Tighten on evidence
When legitimate sources hold at 100% aligned, step the policy up and let monitoring confirm nothing broke.
The honest boundary: seed results are directional estimates and nobody can guarantee inbox placement. Inboxes finds the fixable causes, tells you exactly what to change, and monitors the result. No warmup networks, no bot opens, ever. Full detail on the methodology page.