Free DMARC checker: DMARC, SPF and DKIM records for any domain

By , co-founder of Sales.co. Published November 15, 2026.

Policy shares: 19,736 business domains (41,882 recipients) drawn from 974,150 recipients Sales.co emailed, October 6, 2025 to October 31, 2026 · DMARC and SPF records read November 15, 2026 · checks run live in your browser

A DMARC checker reads the TXT record at _dmarc.yourdomain.com and reports its policy: none (monitor only), quarantine (failing mail goes to spam) or reject (failing mail is refused). Type a domain below. The check also reads the SPF record, counts its DNS lookups against the limit of 10, and tries 10 common DKIM selectors.

Across the 19,736 business domains Sales.co emailed, 39.4% enforce DMARC, 34.9% only monitor and 25.7% have no working policy. The result shows where the domain you check fits.

sales.co enforces DMARC: mail that fails goes to spam.

CheckWhat DNS returnedResult
DMARCv=DMARC1; p=quarantineOK
SPFv=spf1 include:_spf.google.com ~allOK
SPF DNS lookups1 of 10OK
DKIMkey found at google._domainkey, s1._domainkey, s2._domainkeyOK

DMARC tags: no rua= tag, so nobody receives the daily reports; alignment: DKIM relaxed, SPF relaxed.

22.1% of the 19,736 business domains Sales.co emailed (October 6, 2025 to October 31, 2026) publish the same policy (p=quarantine). How people at domains with each policy replied to cold email is in the policy table below.

Nothing to fix: one DMARC record with an enforced policy, one SPF record with a real limit under 10 lookups, and a DKIM key.

Cite this: Sales.co, "DMARC checker", https://sales.co/dmarc-checker, policy shares from 19,736 business domains Sales.co emailed October 6, 2025 to October 31, 2026, DNS read November 15, 2026.

What the DMARC data shows

DMARC policy share and reply rate, business domains

19,736 business domains (a random sample of the 467,208 company domains Sales.co emailed), classified by the DMARC record at _dmarc on November 15, 2026. Reply rates are per recipient across the whole sequence.

SetupDomainsShare of domainsRecipientsReplied (a person)Replied with interest
p=none6,89434.9%13,3170.89%0.28%
p=quarantine4,37022.1%11,9270.55%0.14%
p=reject3,40417.2%9,2510.41%0.11%
No DMARC record4,94625.1%7,2060.68%0.21%
More than one record (ignored)1150.6%166not shownnot shown
Record with no valid policy7under 0.1%15not shownnot shown

"Not shown": fewer than 2,000 recipients, or one sending workspace held over 45% of them. All business domains in the sample: 0.65% replied.

SPF setup share and reply rate

The same domains, classified by the closing term of their SPF record.

SetupDomainsShare of domainsRecipientsReplied (a person)Replied with interest
~all (softfail)9,78449.6%20,4960.82%0.23%
-all (fail)7,20636.5%17,1970.38%0.12%
No SPF record2,04310.4%2,7360.95%0.29%
redirect= (another domain's rules)1300.7%461not shownnot shown
?all (neutral)2631.3%454not shownnot shown
More than one SPF record (error)2491.3%420not shownnot shown
No all mechanism590.3%115not shownnot shown
+all (anyone may send)2under 0.1%3not shownnot shown

What Gmail and Outlook.com require from senders

How to read the result

Worked example: sales.co

Checking sales.co on November 15, 2026: the DMARC record reads "v=DMARC1; p=quarantine", so its policy is p=quarantine. The SPF record reads "v=spf1 include:_spf.google.com ~all" (~all (softfail)), which costs 1 of the 10 DNS lookups. DKIM keys answered at google._domainkey, s1._domainkey, s2._domainkey. That puts it with the 22.1% of business domains in the sample that publish p=quarantine.

Five domains checked on November 15, 2026

The same check run on five well-known domains when this page was built, so you can compare your result with large senders.

DomainDMARC policySPF endingSPF DNS lookupsDKIM selectors that answered
sales.cop=quarantine~all (softfail)1 of 10google, s1, s2
google.comp=reject~all (softfail)1 of 10none of the 10 tried
microsoft.comp=reject-all (fail)6 of 10selector2
hubspot.comp=rejectredirect= (another domain's rules)4 of 10google, s1, s2
salesforce.comp=reject~all (softfail)4 of 10google, s1, s2

Method

What to do with the result

Fix your own domains first: one DMARC record, one SPF record under 10 lookups, a DKIM key for every service that sends as you. Then check a sample of the domains on your list with the MX lookup to see who hosts their mail, clean the list with the free email list cleaner, and test your copy in the spam checker. The cold email deliverability guide covers warm-up and volume. If you would rather not run the sending yourself, Sales.co runs done-for-you cold email from $2,000 a month for up to 10,000 emails, domains and records included, and every email list is $295 one time.

Sources (read November 15, 2026)

SEE ALL FREE TOOLS

FAQ

What is a DMARC record?

A DMARC record is a TXT record at _dmarc.yourdomain.com that tells receiving mail servers what to do with mail that claims to be from you but fails SPF and DKIM. The choices are deliver it anyway (p=none), send it to spam (p=quarantine) or refuse it (p=reject). It also names an address for daily reports (rua=).

Do I need DMARC to send cold email?

If you send more than 5,000 messages a day to Gmail or Outlook.com addresses, yes: both require SPF, DKIM and a DMARC record of at least p=none (Google since February 1, 2024; Outlook.com since May 5, 2025). Below that volume it is still the cheapest protection against someone spoofing your domain. Cold email is usually sent from secondary domains, and each one needs its own records.

Should my DMARC policy be none, quarantine or reject?

Start at p=none with a rua address, read the reports until every service that sends as you passes, then move to quarantine and later reject. Of the business domains Sales.co emailed, 34.9% sat at none, 22.1% at quarantine and 17.2% at reject.

What is the SPF 10 lookup limit?

SPF allows at most 10 DNS lookups to evaluate a record (RFC 7208, section 4.6.4). Each include:, a, mx, ptr, exists and redirect counts, including the ones inside included records. Past 10, receivers return a permanent error and SPF fails. The checker counts them for you, nested includes included.

Why does the checker not find my DKIM key?

DKIM keys sit at selector._domainkey.yourdomain.com, and DNS cannot list selectors. The checker tries 10 common ones (google, selector1, selector2, k1, k2, s1, s2, default, dkim, mail). If your provider uses another, the key may exist anyway: check the provider's admin panel.

Does a recipient's DMARC policy affect my cold email?

Not directly: their policy applies to mail sent from their domain, not to mail you send them. In Sales.co's sends, people at domains that enforce DMARC replied at 0.49% against 0.89% at p=none domains, which may reflect the companies (for example their size or the mail filtering in front of the inbox, neither of which was measured) more than the policy itself.

Is the check private?

The check sends the domain only to Google Public DNS (or Cloudflare's resolver if Google fails), not to Sales.co's servers. Like every page on this site, it loads analytics scripts that record page views, so a domain passed in the address (?domain=) stays in that URL.

More free tools

all free tools · MX lookup · email list cleaner · disposable email checker · spam checker · email lists