Skip to content

Research ·

SPF and DMARC adoption among 214 major companies

We looked up the SPF and DMARC records of 214 well-known company domains to see how many publish them and how strictly they enforce them.

Headline figures

publish an SPF record
92.5%
publish a DMARC record
98.6%
of DMARC domains enforce quarantine or reject
92.4%
of DMARC domains use p=reject
77.7%

Key findings

  • DMARC is close to universal. 211 of 214 domains (98.6%) publish a DMARC record.
  • Most enforce it. 195 of the 211 DMARC domains (92.4%) use quarantine or reject, and 164 (77.7%) use p=reject.
  • Soft fail is the most common SPF setting. 49.5% of SPF records end in ~all, compared with 44.9% using -all.
  • Some rely on DKIM alone. 14 domains (6.5%) publish DMARC without any SPF record.

Results

Record coverage

All 214 domains

Records published Domains Share
SPF and DMARC 197
92.1%
DMARC only (no SPF) 14
6.5%
SPF only (no DMARC) 1
0.5%
Neither 2
0.9%

SPF enforcement

198 domains with SPF

Qualifier Domains Share
Soft fail (~all) 98
49.5%
Hard fail (-all) 89
44.9%
No "all" mechanism 9
4.5%
Neutral (?all) 2
1.0%

DMARC policy

211 domains with DMARC

Policy Domains Share
p=reject 164
77.7%
p=quarantine 31
14.7%
p=none (monitor only) 16
7.6%

What this means

Among large organizations, publishing SPF and DMARC is now standard practice. Enforcement is less complete. Of the 211 domains with DMARC, 16 (7.6%) are still at p=none, which only monitors and asks receivers to take no action on mail that fails authentication. Another 31 (14.7%) use p=quarantine, which usually sends failing mail to spam. Together, 47 domains (22.3%) have still to move to the strictest policy, p=reject.

The 14 domains that publish DMARC without SPF depend entirely on DKIM alignment to pass DMARC. That works, but it leaves no fallback if a message's DKIM signature breaks in transit, so it is worth checking when you audit a domain.

If you are setting up authentication for your own domain, these companies show a sensible target. Publish SPF, preferably ending in -all. Start DMARC at p=none to collect reports without affecting delivery, then move to p=quarantine and finally p=reject once the reports confirm that all legitimate mail passes. Our DMARC guide walks through each step.

Methodology

We compiled 214 well-known public company domains across technology, finance, retail, healthcare, media, airlines, hospitality, education and SaaS. On October 2, 2026, we queried public DNS for each domain's TXT records with dig TXT <domain> to find SPF and dig TXT _dmarc.<domain> to find DMARC. This is a DNS-only study: no SMTP connections were made.

SPF enforcement is classified by the qualifier on the final all mechanism: -all (hard fail), ~all (soft fail), ?all (neutral), or no all mechanism. DMARC policy is read from the p= tag of the published record.

About the sample: these are large, well-resourced organizations, not a random sample of all domains. Studies of all registered domains find much lower DMARC adoption, so read the 98.6% figure as "among major companies", not "across the internet".

FAQ

SPF and DMARC study FAQ

What the sample does and does not measure.

Is this sample representative of all domains?

No. The sample is 214 well-known public companies across technology, finance, retail, travel, media and SaaS, not a random sample of registered domains. Large, security-focused organizations adopt SPF and DMARC at much higher rates than the wider domain population, which includes many small and inactive domains.

Why does this study not measure catch-all domains?

Detecting a catch-all domain requires an SMTP conversation with its mail server. This study is limited to public DNS records, which anyone can reproduce with a standard DNS lookup.

Can I reuse this data?

Yes. The full per-domain results, including the exact SPF and DMARC record text, are available as a CSV download. Please link to this page when you cite the figures.

Authentication gets you delivered. Clean lists keep you there.

Verify every address before you send, so bounces never undo the work you put into SPF and DMARC.

100 free credits · No card required · Credits never expire