---
title: "DMARC Checker: Free DMARC, SPF and DKIM Record Check"
url: https://sales.co/dmarc-checker
source: https://sales.co/dmarc-checker
description: "Check a domain's DMARC policy, SPF record and lookup count, and DKIM keys in your browser, next to the DMARC policies of 19,736 domains Sales.co emailed."
---

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

By [Ryan Doyle](https://www.linkedin.com/in/ryan-doyle/), 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.

| Check | What DNS returned | Result |
| --- | --- | --- |
| DMARC | `v=DMARC1; p=quarantine` | OK |
| SPF | `v=spf1 include:_spf.google.com ~all` | OK |
| SPF DNS lookups | 1 of 10 | OK |
| DKIM | key found at `google._domainkey`, `s1._domainkey`, `s2._domainkey` | OK |

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

- 39.4% of the 19,736 business domains Sales.co emailed enforce DMARC (22.1% quarantine, 17.2% reject), 34.9% only monitor with p=none, and 25.7% have no working DMARC policy (25.1% publish no record at all).
- People at domains that enforce DMARC replied to cold email about half as often as people at p=none domains: 0.49% against 0.89% (104 replies from 21,178 recipients against 119 from 13,317). Interested replies: 0.13% against 0.28%.
- The gap holds with each group's largest sending workspace taken out: 0.42% against 0.80%.
- A recipient's DMARC policy only governs mail sent from their domain, so it does not filter your email to them. Read it as a sign of the company, not a filter: enforcing domains received 50.6% of the recipients but are 39.4% of the domains, so they sit at companies where more people were emailed. Company size itself was not measured.
- SPF: 49.6% of the domains end their SPF record in ~all (softfail), 36.5% in -all (fail), and 10.4% publish no SPF record. 1.3% publish two SPF records, which breaks SPF for all their mail. 0.6% publish two DMARC records, so receivers ignore DMARC for them.

## 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.

| Setup | Domains | Share of domains | Recipients | Replied (a person) | Replied with interest |
| --- | --- | --- | --- | --- | --- |
| p=none | 6,894 | 34.9% | 13,317 | 0.89% | 0.28% |
| p=quarantine | 4,370 | 22.1% | 11,927 | 0.55% | 0.14% |
| p=reject | 3,404 | 17.2% | 9,251 | 0.41% | 0.11% |
| No DMARC record | 4,946 | 25.1% | 7,206 | 0.68% | 0.21% |
| More than one record (ignored) | 115 | 0.6% | 166 | not shown | not shown |
| Record with no valid policy | 7 | under 0.1% | 15 | not shown | not 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.

| Setup | Domains | Share of domains | Recipients | Replied (a person) | Replied with interest |
| --- | --- | --- | --- | --- | --- |
| ~all (softfail) | 9,784 | 49.6% | 20,496 | 0.82% | 0.23% |
| -all (fail) | 7,206 | 36.5% | 17,197 | 0.38% | 0.12% |
| No SPF record | 2,043 | 10.4% | 2,736 | 0.95% | 0.29% |
| redirect= (another domain's rules) | 130 | 0.7% | 461 | not shown | not shown |
| ?all (neutral) | 263 | 1.3% | 454 | not shown | not shown |
| More than one SPF record (error) | 249 | 1.3% | 420 | not shown | not shown |
| No all mechanism | 59 | 0.3% | 115 | not shown | not shown |
| +all (anyone may send) | 2 | under 0.1% | 3 | not shown | not shown |

## What Gmail and Outlook.com require from senders

- **Gmail, since February 1, 2024:** anyone sending more than 5,000 messages a day to Gmail accounts needs SPF, DKIM and a DMARC record, and the policy can be none. The From: domain must align with SPF or DKIM, and marketing mail needs one-click unsubscribe. Senders below that need SPF or DKIM.
- **Outlook.com, since May 5, 2025:** domains sending more than 5,000 emails a day need SPF and DKIM to pass and a DMARC policy of at least p=none aligned with SPF or DKIM. Microsoft's post says mail that fails is rejected with error 550 5.7.515, and also describes routing to Junk as the first step; its dates disagree, so treat rejection as live.
- **What it means for cold email:** Sales.co's plans send 10,000 to 20,000 emails a month in total, spread over many sending domains, so each domain stays under 5,000 a day. The same three records still keep a new sending domain out of spam, so set them on every domain you send from, not only the main one.

## How to read the result

- A DMARC policy of p=none only collects reports; p=quarantine and p=reject act on mail that fails. Two v=DMARC1 records cancel each other out.
- An SPF record ending in ~all (softfail) or -all (fail) sets a limit; ?all and +all do not. Two v=spf1 records is a permanent error.
- Every include:, a, mx, ptr, exists and redirect in SPF costs one DNS lookup, nested ones too. More than 10 and SPF fails.
- DKIM "not found" only means none of the common selectors answered; your provider may use its own name.

## 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.

| Domain | DMARC policy | SPF ending | SPF DNS lookups | DKIM selectors that answered |
| --- | --- | --- | --- | --- |
| sales.co | p=quarantine | ~all (softfail) | 1 of 10 | google, s1, s2 |
| google.com | p=reject | ~all (softfail) | 1 of 10 | none of the 10 tried |
| microsoft.com | p=reject | -all (fail) | 6 of 10 | selector2 |
| hubspot.com | p=reject | redirect= (another domain's rules) | 4 of 10 | google, s1, s2 |
| salesforce.com | p=reject | ~all (softfail) | 4 of 10 | google, s1, s2 |

## Method

- Your check: the browser asks Google Public DNS (dns.google, JSON API) for the TXT records at _dmarc.<domain> and at the domain, with Cloudflare's resolver as the fallback. It follows every include: and redirect= in the SPF record to count DNS lookups, and asks for TXT records at 10 common DKIM selectors. An email address is cut to the part after the @.
- Policy shares: every recipient Sales.co emailed from October 6, 2025 to October 31, 2026 (974,150 recipient threads, one address in one sending workspace, over 467,226 domains). 20,000 of the 467,208 company domains were drawn in a seeded random order, the same sample as the [MX lookup](https://sales.co/mx-lookup). Their DMARC and SPF records were read over public DNS on November 15, 2026; 264 lookups timed out and are left out. The page and the collector use the same classification code.
- Reply rates: a recipient counts once if they ever replied with a reply that is not an auto-reply, out-of-office, bounce, warm-up, test or spam (the sending tool's labels); "with interest" means at least one reply was labeled possibly interested. Replies to the newest 14 days of sends are not counted yet, which is why the window ends October 31, 2026.
- The rates describe the people at domains with each setup, not the setup's effect: company size, industry and mail filtering differ between the groups.

## 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](https://sales.co/mx-lookup) to see who hosts their mail, clean the list with the [free email list cleaner](https://sales.co/free-email-list-cleaner), and test your copy in the [spam checker](https://sales.co/email-spam-checker). The [cold email deliverability guide](https://sales.co/blog/cold-email-deliverability) 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](https://sales.co/pricing), domains and records included, and every [email list](https://sales.co/email-lists) is $295 one time.

## Sources (read November 15, 2026)

- Sales.co sending database: recipients and labeled replies, October 6, 2025 to October 31, 2026, computed November 15, 2026. Policy labels and counts only; no address or domain is published.
- DMARC and SPF records: public DNS (Cloudflare 1.1.1.1 and Google 8.8.8.8), read November 15, 2026.
- Gmail: [Email sender guidelines](https://support.google.com/a/answer/81126), read November 15, 2026. Outlook.com: [new requirements for high-volume senders](https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730), read November 15, 2026.
- DMARC: [RFC 7489](https://www.rfc-editor.org/rfc/rfc7489). SPF and its 10-lookup limit: [RFC 7208, section 4.6.4](https://www.rfc-editor.org/rfc/rfc7208#section-4.6.4).

[SEE ALL FREE TOOLS](https://sales.co/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](https://sales.co/tools) · [MX lookup](https://sales.co/mx-lookup) · [email list cleaner](https://sales.co/free-email-list-cleaner) · [disposable email checker](https://sales.co/disposable-email-checker) · [spam checker](https://sales.co/email-spam-checker) · [email lists](https://sales.co/email-lists)
