This free DMARC checker shows what your record does to your mail.

We read your policy and reporting address, explain every tag in plain English and write the next record to publish.

Works with a domain or a full email address. We read DNS fresh on every run.

Example report for trynorthpeak.example, a made-up new cold email domain

3 of 5 checks pass. Fix SPF first: until SPF passes, this domain falls short of the rules Gmail, Yahoo and Outlook set for bulk senders.

That meets the minimum Gmail and Yahoo ask of bulk senders, but mail that fails is still delivered, so anyone can send as this domain, and you will never hear about it.

What we found
v=DMARC1; p=none
How to fix it

Replace it with this record. Your DKIM key is in place, so mail signed with it passes DMARC. Quarantine is safe once the SPF fix above is live. If other services send as this domain, switch DKIM on in each of them first. Reports go to dmarc@trynorthpeak.example: create that address, or change it to one you read.

v=DMARC1; p=quarantine; rua=mailto:dmarc@trynorthpeak.example

Add it as a TXT record with host _dmarc in your DNS, in place of any DMARC record already there.

Every tag in the record, in plain English
v=DMARC1Marks this TXT record as DMARC.
p=noneThe policy for mail that fails both SPF and DKIM alignment. Mail that fails is delivered as usual. You only get reports.
Also checked for trynorthpeak.example

Once your records pass, warm up the mailbox and start sending with Emailchaser.

Emailchaser warms up each mailbox on its own, then sends your campaign and its follow-ups from the domain you just checked.

Start my free trial7-day free trial, $0 today

The check runs on our server against live DNS and 16 public blocklists (3 for domains, 13 for mail server IPs). A list that does not answer is never counted as clean. Nothing you type is stored.

Each DMARC result means one thing, and each has one next step.

The checker gives one line for your DMARC record. Find that line below to see what receivers do with it and what to change. When you run a check, the row that matches your result is marked.

What the checker showsWhat it meansWhat to do
DMARC is enforced at p=rejectReceivers refuse mail that fails SPF and DKIM for your domain. This is the strongest setting.Keep reports switched on, and re-check each time you add a sending service.
DMARC is enforced at p=quarantineReceivers send mail that fails both checks to spam.When reports show only your own mail passing, move to p=reject.
DMARC is set to p=noneYour result in the exampleFailing mail is delivered as usual and you only get reports. It meets the minimum for bulk senders and stops nobody.Switch DKIM on at every service that sends as you, then move to p=quarantine. The report gives the record.
Enforced, but only for part of failing mailThe pct tag applies your policy to a share of failing mail and leaves the rest at p=none.Raise pct to 100 once the reports look clean.
No DMARC record foundAnyone can send as your domain, and Gmail, Yahoo and Outlook expect a record from bulk senders.Publish one TXT record at _dmarc. Copy the starter record in the report.
More than one DMARC recordReceivers act as if there were none.Delete them all and publish the single record the report suggests.
A record with no valid policyThe p= tag is missing or is not none, quarantine or reject, so receivers ignore the record.Set p= to one of the three and publish the record again.

See how your DMARC policy compares with 13,511 listed companies.

On 18 October 2026, 48.4% of 13,511 listed companies published p=quarantine or p=reject, 24.4% sat at p=none and 27.0% had no DMARC record at all. Only quarantine and reject change what a receiver does with forged mail.

How the example domain compares, so you can see what your own result will show.

Your DMARC policy

p=none

24.4% of the 13,511 companies are at p=none, and 48.4% enforce DMARC with quarantine or reject.

DMARC reports address

Not set

82.7% of the companies with a readable DMARC record name an address for reports.

DMARC on your provider

Google Workspace

44.6% of them enforce DMARC. Across all 13,511 companies it is 48.4%.

DMARC policy of 13,511 company domains, October 2026
  • p=reject: receivers refuse failing mail3,75427.8%
  • p=quarantine: receivers send failing mail to spam2,78220.6%
  • p=none: reports only, delivery unchanged3,30324.4%
  • A record receivers cannot read270.2%
  • No DMARC record3,64527.0%
Share of domains that enforce DMARC, by who handles their mail
  • Microsoft 3654,421 domains57.9%
  • Google WorkspaceYour domain1,302 domains44.6%
  • A security gateway in front of the mailbox2,526 domains74.0%
  • Another host or their own server4,108 domains32.3%

All 13,511 domains: 48.4%

Companies on Microsoft 365 and on Google Workspace set these records differently.

Where the mail is handledDomainsEnforce DMARCAt p=rejectNo DMARC record
Microsoft 3654,42157.9%30.7%16.9%
Google Workspace1,30244.6%23.7%22.0%
A security gateway in front of the mailbox2,52674.0%52.5%4.9%
Another host or their own server4,10832.3%14.3%38.6%

Companies on Microsoft 365 enforce DMARC 57.9% of the time and companies on Google Workspace 44.6%. Companies behind a security gateway lead at 74.0%. These are large listed companies, not cold email domains, so read the numbers as the standard the people you email already meet, not as a target for your own setup.

Source: Emailchaser DMARC adoption study, 13,511 company domains with a stock exchange listing, read from public DNS on 18 October 2026. See the full study and its data.

A receiver applies your DMARC policy in four steps.

DMARC ties SPF and DKIM to the address your recipient sees in the From line.

  1. It reads the From domain

    The receiver looks up the TXT record at _dmarc on the domain in the From line.

  2. It checks alignment

    SPF or DKIM must pass for a domain that matches the From domain. One of the two is enough.

  3. It applies your policy

    If neither aligned, the message is delivered, sent to spam or refused: p=none, quarantine or reject.

  4. It sends you a report

    If you set a rua address, the receiver mails a daily summary of every server that sent as your domain.

Publish your DMARC record as one TXT record at _dmarc.

Start at p=none only if you do not yet know every service that sends as your domain. Otherwise start at p=quarantine.

  1. Open the DNS settings for the domain and make sure SPF and DKIM are already in place.
  2. Add a TXT record with the host _dmarc. A domain can have exactly one.
  3. Replace dmarc@yourdomain.com with a mailbox you read, or with the address a DMARC reporting service gives you.
  4. Save, then run the check above to see the policy as receivers read it.

Move up one record at a time.

Step one, watch and learnType TXT, host _dmarc
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Delivery does not change. Read a week or two of reports and list every sender in them.

Step two, send failing mail to spamType TXT, host _dmarc
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

Safe once every service that sends as you passes SPF or DKIM for your domain.

Step three, refuse failing mailType TXT, host _dmarc
v=DMARC1; p=reject; rua=mailto:dmarc@yourdomain.com

The strongest setting. Move here when reports show nothing of yours failing.

A DMARC record tells receivers what to do with mail that fails SPF and DKIM.

SPF and DKIM each answer a narrow question about a message. DMARC ties them to the address your recipient actually sees in From. A message passes DMARC when SPF or DKIM passes for the same domain as that From address, which is called alignment. When neither does, the receiver applies your policy: deliver it anyway (p=none), send it to spam (p=quarantine) or refuse it (p=reject).

Without a DMARC record, anyone can put your domain in the From line of their own mail, and receivers have no instruction from you about it. Gmail, Yahoo and Outlook all require a DMARC record from anyone sending in bulk, at p=none or stricter.

Every DMARC tag does one thing, and only v= and p= are required.

TagExampleWhat it does
vv=DMARC1Marks the record as DMARC. It must come first.
pp=quarantineThe policy for mail that fails: none, quarantine or reject.
ruarua=mailto:dmarc@yourdomain.comWhere receivers send daily summary reports.
spsp=rejectA separate policy for subdomains. Without it, subdomains follow p.
pctpct=50Applies the policy to only part of failing mail, for a careful rollout.
adkimadkim=sStrict DKIM alignment: the signing domain must match exactly. Relaxed (r) is the default.
aspfaspf=sStrict SPF alignment, the same idea for the return-path domain.
rufruf=mailto:...Where to send copies of single failures. Outlook does not send these, and many receivers do not.
fofo=1When failure reports are sent: when either check fails, rather than both.

The tags are defined in RFC 7489. Microsoft says it does not send ruf reports; read on 6 October 2026.

Move from p=none to p=reject in three steps, with reports telling you when.

  1. Start with reports. Publish v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com if you do not know every service that sends as your domain. Read a week or two of reports and list every sender in them.
  2. Fix every legitimate sender. Switch DKIM on at each service that sends as you, so each one signs with your domain. The DKIM checker shows the keys you already have.
  3. Then enforce. Change p=none to p=quarantine. When the reports show only your own mail passing and nothing of yours failing, move to p=reject.

A brand-new cold email domain that only sends through one provider with DKIM on can skip the first step and start at p=quarantine. That is what our check suggests when it finds a working DKIM key. Microsoft's own advice for high-volume senders is the same order: none, then quarantine, then reject, once your legitimate sources are aligned (Microsoft, read 6 October 2026).

A DMARC report tells you every server that sent mail as your domain.

Once a record has a rua= address, receivers that send reports (Google and Yahoo among them) mail a compressed XML file there about once a day. Each file covers one receiver and one day, and each row in it is one sending server.

Field in the reportWhat it tells you
source_ipThe server that sent the mail. Look it up to see which service it belongs to.
countHow many messages that server sent as your domain that day.
policy_evaluated: dispositionWhat the receiver did: none, quarantine or reject.
policy_evaluated: dkim and spfWhether DKIM and SPF passed in a way that counts for DMARC, that is, aligned with your From domain.
auth_resultsThe raw DKIM and SPF results, with the domain each one checked.

Read it in that order. A server you recognise with dkim pass is fine. A server you recognise with dkim fail is a service to fix before you enforce. A server you do not recognise, failing both, is someone sending as you, and exactly what p=quarantine and p=reject are for. A reporting service turns the XML into a readable table if the volume gets large.

Your DMARC record protects your domain, not the mail you send to others.

A DMARC record governs mail sent as your domain. It does not change how a recipient's server judges you: that comes from your SPF, DKIM and DMARC passing, and from your sending reputation. Publishing p=reject does not make your own campaigns land better, and a recipient's strict policy does not make your mail to them land worse.

What a strict policy does give you is a domain that nobody else can spoof, which keeps phishing in your name out of your recipients' inboxes and your domain off the lists that catch it. Build a record from scratch with the DMARC record generator, or check all five records on the domain health check.

Common questions about DMARC

What is a DMARC record?

A TXT record at _dmarc.yourdomain.com that tells receiving servers what to do with mail that claims to be from your domain but fails both SPF and DKIM alignment: deliver it, send it to spam, or refuse it. It also tells them where to send reports.

What does p=none do?

Nothing to the mail itself. Failing messages are delivered as usual, and you only get reports. It meets the minimum Gmail, Yahoo and Outlook ask of bulk senders, but it does not stop anyone sending as your domain.

Is it safe to move to p=quarantine?

Yes, once every service that sends as your domain passes SPF or DKIM for it. DKIM is the safer one to rely on, because it survives forwarding. Our check suggests quarantine when it finds a working DKIM key, and keeps you at p=none when it does not.

Where should DMARC reports go?

To an address someone reads, or a DMARC reporting service. The rua= tag takes one or more mailto: addresses. Reports are daily XML files from each receiver, listing every server that sent mail as your domain and whether it passed.

Does DMARC need both SPF and DKIM to pass?

No. A message passes DMARC when either one passes for a domain that matches the From address. DKIM is the one to rely on, because forwarding breaks SPF and leaves a DKIM signature intact.

What is the difference between rua and ruf?

rua= receives aggregate reports: one summary a day from each receiver, with counts per sending server. ruf= receives failure reports, with details of single failing messages. Most receivers send only aggregate reports, so rua= is the one that matters.

Does a subdomain need its own DMARC record?

No. A subdomain with no record of its own follows its parent domain's record, using the sp= policy if there is one and p= otherwise. Our check reads the parent's record in that case and says so.

Why do two DMARC records break DMARC?

A domain may publish exactly one. With more than one, receivers act as if there were none (RFC 7489), so your policy stops working. Our check shows the strictest of them as the one to keep.

How do I check my DMARC record?

Type your domain in the checker above and press Check domain. It reads the TXT record at _dmarc.yourdomain.com and explains every tag. From a terminal, run nslookup -type=txt _dmarc.yourdomain.com on Windows, or dig TXT _dmarc.yourdomain.com +short on Mac and Linux.

Is DMARC really necessary?

For cold email, yes. Gmail, Yahoo and Outlook require a DMARC record from bulk senders, which Google and Microsoft define as about 5,000 messages a day, and p=none is the minimum. Below that volume it is not required, but it still stops others sending as your domain unchecked.

How many companies enforce DMARC?

48.4% of the 13,511 listed companies in our study published p=quarantine or p=reject, 27.8% are at p=reject and 27.0% publish no DMARC record. The study was read from public DNS on 18 October 2026.

How do I fix a DMARC failure?

A message fails DMARC when neither SPF nor DKIM passes for a domain that matches the From address. Check both records above, switch DKIM on at each service that sends as you, then read your DMARC reports to find the sender that fails.

Check the rest of your setup with these free tools.

Send cold email from domains that pass all five checks.

Every plan includes warm-up, follow-ups and unlimited email accounts.

Start my free trial7-day free trial, $0 today