Xem research · November 8, 2026
39% of the web's top sites don't ask Gmail to stop email forged in their name.
We checked the email authentication records of the 10,000 most popular websites. Of the 7,266 that receive email, 83.1% publish a DMARC record, but only 61.1% tell mailbox providers to quarantine or reject mail that fails it.
93.3%
of sites that receive email publish an SPF record
83.1%
publish a DMARC record of any kind
35.1%
set DMARC to reject, the strongest protection
13.3%
publish a BIMI record to show their logo in the inbox
26% of DMARC records don't stop anything
DMARC tells Gmail, Outlook and Yahoo what to do with mail that claims to come from your domain but fails SPF and DKIM. A policy of p=none only asks for reports and tells providers to take no action on failing mail. Only quarantine and reject ask them to keep forged mail away from readers.
DMARC policy, sites that receive email
87% of DMARC records ask for aggregate reports (a rua address), the first step towards enforcing. Among sites that do enforce, 2.8% apply the policy to only part of their failing mail (pct below 100).
Protection drops off outside the top 1,000
The top 100 and the top 1,000 sites enforce DMARC at about the same rate. Below that, enforcement falls: across the full top 10,000, 39% of sites that receive email don't enforce it.
DMARC set to quarantine or reject
SPF is nearly universal, but often soft
93.3% of sites that receive email publish SPF, the list of servers allowed to send for them. How the record ends decides what happens to everything else: -all says fail it, ~all says treat it as suspicious, and ?all says nothing at all.
How SPF records end, among sites with SPF
Domains that never send mail are the easiest to fake
2,711 of the 10,000 domains publish no MX record. They can still be spoofed unless they say they never send it: an SPF record of v=spf1 -all and a DMARC policy of p=reject. Only 16.3% of them do both.
The newer standards are rare
BIMI, which shows a verified brand logo next to your mail in Gmail, Apple Mail and Yahoo, appears on 13.3% of sites that receive email. MTA-STS, which forces encrypted delivery to your own mail servers, appears on 4%.
Check your own domain
Xem's free checker runs the same lookups for your domain, in your browser, and gives you the exact record to add for anything missing.
Check your domainHow we did this
We took the top 10,000 domains of the Tranco list 94P72, a research ranking that averages several popularity lists. On November 8, 2026 we looked up each domain's MX records and the TXT records for SPF (the domain itself), DMARC (_dmarc), BIMI (default._bimi) and MTA-STS (_mta-sts) through Cloudflare, Google and Quad9 public resolvers, retrying failed lookups twice. Domains with any failed lookup were then scanned again, more slowly, the same day.
A domain “receives email” if it has at least one MX record that isn't a null MX. Lookups that still failed (120 domains had at least one) are left out of that check rather than counted as missing. A domain with two DMARC records is counted as invalid, as mailbox providers ignore both. We didn't check DKIM, because its selectors can't be discovered from DNS alone, and we read only public DNS: no mail was sent.
The aggregate numbers are available as JSON under CC BY 4.0. Please cite and link this page if you use them.
Cite this research
Xem (2026). Email authentication on the top 10,000 websites. https://xem.email/research/email-authentication