Skip to content
OutboundQA

Free tool

Free DMARC record checker

Use this DMARC checker to confirm a domain has a DMARC record and see what policy it enforces: none, quarantine, or reject.

This checks DMARC policy for one domain. For a real launch verdict, run every domain, inbox, and tracking domain through the full QA pass.

Runs live in your browser via public DNS. Nothing is stored.

How to read the result

A missing DMARC record is a launch blocker. If the record exists, the policy tag p= tells you what receivers do with failing mail. p=none only monitors, p=quarantine sends failures to spam, and p=reject blocks them.

For a new cold email domain, p=none is a common starting point while reports come in, but it is not the whole launch decision. OutboundQA checks DMARC alongside SPF, DKIM, inbox setup, tracking SSL, blacklist status, and the full sender checklist across the workspace.

What this check does not catch

A passing DMARC policy lookup is useful, but it is not launch signoff. Cold email campaigns still fail when adjacent records, tracking domains, or inbox-level settings are broken.

SPF lookup limits
DKIM selector setup
MX readiness
tracking-domain SSL
blacklist status
sending-domain age

Setup guides for this check

Read the setup notes behind this result, then verify the neighboring records before launch.

Need to check a full outbound workspace?

OutboundQA checks every domain, inbox, and tracking domain in the workspace, then gives you a shareable report with a Ready, Needs Fix, or Do Not Launch verdict.

Questions

DMARC is a DNS TXT record at _dmarc.yourdomain that tells receivers what to do with mail that fails SPF and DKIM, and where to send reports. Google and Yahoo require it for bulk senders.

p=none is monitor-only. DMARC reports come in but nothing is enforced. It is a safe starting point, but for cold email you usually want to move to p=quarantine once your reports look clean.

Effectively yes. Google and Yahoo bulk-sender rules expect SPF, DKIM, and DMARC. Missing DMARC is one of the most common pre-launch blockers OutboundQA catches.