How common is DMARC? A measurement of the 10,000 most visited domains

How many of the most popular domains on the web have SPF, DMARC, MTA-STS and BIMI set up, and how strict is their DMARC? We measured it on 1 November 2026 for the 10,000 most visited domains. Here are the numbers, the method and where the measurement reaches its limits.

The results

Of the 10,000 measured domains, 7,189 (71.9%) accept email, that is, they have an MX record. All percentages below refer to these 7,189 domains.

FeatureShare
SPF record92.7%
DMARC record82.4%
DMARC with enforcement (quarantine or reject)60.7%
DMARC with reject34.9%
BIMI record13.2%
TLS-RPT record4.5%
MTA-STS record4.0%

Striking: SPF and DMARC are almost standard for popular domains. MTA-STS and TLS-RPT, which secure encrypted delivery, are set up by only about one in 25 domains.

DMARC in detail

Of the 7,189 domains with email, 5,926 have a DMARC record. Their policy (p=):

PolicyDomainsShare of all domains with email
reject2,50934.9%
quarantine1,85525.8%
none1,56021.7%
no DMARC1,26317.6%

Of the domains with DMARC, 87.2% have entered a report address (rua=). Of the SPF records, 47.8% end in ~all, 46.4% in -all and 2.1% in ?all. A single record allows anyone to send with +all.

So more than one in five domains is at p=none, the starting value that only observes forgeries and does not reject them. Two records had an invalid policy.

By popularity

The more popular the domain, the more often DMARC is set strictly:

RankDomains with emailDMARCwith enforcementreject
1 to 1,00068489.3%74.9%50.6%
1,001 to 3,0001,39183.5%64.1%36.8%
from 3,0015,11481.2%57.9%32.3%

Method

Limits of the measurement

What this means for your domain

If most large domains already have DMARC, it is more of a duty than an option for your domain too, especially if you send a lot of email (requirements of Gmail, Yahoo and Outlook). The way is always the same: start with p=none, collect reports, then move to quarantine and later reject.

You may use the numbers with attribution (Postwacht, measurement of 1 November 2026). Please report mistakes via support.