Download websites that use AntiBot.Cloud

About AntiBot.Cloud

The registration records behind this bot filter look nothing like a customer base. As of October 2026 we detect AntiBot.Cloud on 26,156 sites, of which 15,516 resolve to registrants in Netherlands, and the addresses cluster heavily on .top. A protective service adopted independently by many unrelated owners would not concentrate like that. Concentration on one country and one inexpensive suffix is what a fleet looks like: many sites under few hands, deployed from a single template.

What the software does fits that reading. AntiBot.Cloud sells a Proprietary bot filter that places a challenge in front of an arriving visitor and decides, from behaviour and request patterns, whether to pass them through to the page. For a publisher it is a defence against scrapers and credential stuffing. For an operator running a large number of thin sites it is also a convenient way to keep crawlers, competitors and classification services from seeing what the pages contain. One product serves both cases, and the dataset does not pretend to know which case any given domain represents.

Release data supports the same reading. We record only 3 distinct releases across the entire detected population, concentrated on 7.102. Software installed by many independent owners fragments across releases over time, because each owner updates on a different schedule or never updates at all. A near uniform release line points instead to deployments maintained centrally, or installed fresh from whichever package was current.

Detection is more inferential here than usual and the caveat is a real one. The service works by intercepting requests, so what we record is the challenge layer, the cookie it sets or the script it serves, rather than the site sitting behind it. A configuration that only challenges suspicious traffic may hand us an ordinary page and never reveal itself, which means the deployed total is higher than what we publish. A site can also sit behind the filter on some paths and not on others, and a snapshot cannot tell the difference.

Checking one domain tells you that one site is filtered. The list is worth more to the people who need the shape of a network rather than any single node: fraud and abuse teams mapping infrastructure that deliberately resists crawling, ad verification vendors deciding which inventory they can actually inspect, and researchers assembling a starting set of domains that appear to share an operator. Bot filtering is a signal about who runs a site rather than about what the site says, and aggregated across a whole population it is one of the few signals that survives an operator's effort to look like everybody else.