Resolved over DNS, not read from headers

Which networks refuse AI crawlers

A server can decline to say who runs it. It cannot decline to have an address. Every domain here was resolved to an IP, the IP mapped to its autonomous system, and the refusal rate computed per operator - so the figure covers origins that strip every identifying header.

The measurement

Origin networks were resolved for 30,240 of 30,319 measured domains, against 7,971 identifiable from response headers alone. Among networks hosting at least 50 measured domains, SERVICEPIPE has the highest refusal rate at 71% of 76 domains, against 23.0% across all resolved networks.

Measured 2026-10-10 by direct request to every domain in the corpus. Method: how this is measured. Reuse under CC BY 4.0 with attribution.

Cite as: Crawl Census, "AI crawler refusal by origin network", measured 2026-10-10. https://crawlcensus.com/networks

30,240
domains resolved to a network
7,971
identifiable from headers alone
3.8x
coverage gained
30
networks with 50+ domains

Refusal rate by origin network 25 or more domains each

bar chartSERVICEPIPE71.1%Automattic38.1%Cloudflare37.4%Akamai31.4%Datacamp17.1%National Informatics Cent…16%Renater15.7%Amazon13.7%Google13.5%Fastly13.1%DataWeb Global Group12.7%Microsoft9.8%DigitalOcean9.3%OVH8.9%

Every network measured the table

NetworkASNDomainsRefuse AI agentsRateCharge instead
SERVICEPIPEAS201706765471%-
AutomatticAS263528911038%22
CloudflareAS133358,7813,28537%118
AkamaiAS1662588527831%2
DatacampAS60068761317%-
National Informatics CentreAS475850816%-
RenaterAS78951816%-
AmazonAS89876,24685614%58
GoogleAS1516984211414%-
FastlyAS541131,09214313%76
DataWeb Global GroupAS3957271913%-
MicrosoftAS80686876710%1
DigitalOceanAS14061172169%-
OVHAS16276361329%-
Verein zur Foerderung eines Deutschen FoAS6808179%-
OracleAS318986458%-
HetznerAS24940464368%2
DDOS-GUARDAS57724149117%-
ImpervaAS19551326237%-
Alibaba (US) TechnologyAS45102151107%-
Cloudflare LondonAS209242662416%-
HLLAS5111514785%-
Hangzhou Alibaba AdvertisingAS3796320394%-
Shenzhen Tencent Computer Systems CompanAS450907234%-
JSC SelectelAS4950516664%-
IDCAS237246023%-
Yandex.CloudAS2003507623%-
Tencent BuildingAS1322035012%-
F5 Networks SARLAS352805212%-
IONOS SEAS85605300%-

Why this differs from the edge table method

The edge provider table reports what a server says about itself: a server header, a cf-ray, an x-served-by. Roughly three quarters of measured domains say nothing at all, and a header can be forged or stripped.

This page reports something a site cannot suppress. The domain resolves to an address, the address belongs to an autonomous system, and that mapping is published in the global routing table. It answers a different question - not "which CDN is in front of this origin" but "whose network is this origin on" - and for a self-hosted origin those are the same answer, while for a CDN-fronted origin the anycast address belongs to the CDN.

Networks hosting fewer than 50 measured domains are excluded: a refusal rate over a handful of sites is noise. Resolution uses DNS over HTTPS and the Team Cymru IP-to-ASN service, both queried live at scan time.