Atlas
Map the automation and protection landscape.
Atlas will be the research and intelligence layer of WhoScrapes. It catalogs both sides: what protection the web uses, what automation stacks exist, and how the two interact.
In development · Pre-launch
Protection intelligence
- Anti-bot vendors
- WAF providers
- CAPTCHA and challenge systems
- Browser fingerprinting
- Fraud and device intelligence
- IP intelligence
- Open-source detection tools
- Detection algorithms
- Observed deployments
Automation intelligence
- Browser automation libraries
- HTTP client libraries
- Crawling frameworks
- Browser infrastructure platforms
- Network stacks
- Browser / runtime configurations
- Crawler identities
- Authenticated bots
- AI agents and crawlers
- Known automation signatures
- Transport / client fingerprints
Example research subjects
Cloudflare · Akamai · DataDome · HUMAN / PerimeterX · F5 / Shape · Imperva · AWS WAF Bot Control · Fastly · Fingerprint · Google reCAPTCHA · hCaptcha · GeeTest · Arkose Labs · Kasada · Radware · Netacea · Oracle WAF · Azure WAF · Fortinet · Coraza · OWASP CRS · BotD · CreepJS · JA4 · p0f · CrowdSec · IPinfo · MaxMind · Spur · IPQualityScore · GreyNoise · AbuseIPDB
Playwright · Puppeteer · Selenium · WebDriver BiDi · Chrome DevTools Protocol · Scrapy · curl · Python requests · httpx · Go net/http
Technologies Atlas may research, listed for illustration. Names are trademarks of their respective owners; no affiliation, partnership or endorsement is implied.
Observed is not the same as inferred.
Atlas records how much is actually known, and says so.
- Verified
- Public vendor or customer documentation confirms it.
- Observed
- Distinct technical behavior or signatures were observed.
- Inferred
- Available evidence strongly suggests the technology or capability.
- Unknown
- Not enough evidence to say.
Atlas describes what is publicly observable. It does not claim knowledge of proprietary internal algorithms or of customer-specific security configurations.
The research value is in the relationship.
Atlas is not only "what protection does the web use?" It also asks what automation stacks exist, and how each class of automation interacts with each class of protection.
Each cell is a research question, not a result. CF Cloudflare · DD DataDome · AK Akamai · AWS AWS WAF.
| Automation ↓ / Protection → | CF | DD | AK | AWS |
|---|---|---|---|---|
| Playwright | ||||
| Puppeteer | ||||
| HTTP clients | ||||
| Browser clouds | ||||
| AI crawlers |
Atlas researches the ecosystem. Probe benchmarks against it.
Atlas will track protection vendors, detection techniques, integrations and observed deployments. That research will help determine which products and signal families Probe should benchmark.
When a commercial system is impractical to integrate directly, Atlas research can support a modeled detector or identify opportunities for controlled benchmark environments.
Probe benchmarks will run against WhoScrapes-controlled, partner-provided or explicitly authorized environments, not unrelated third-party sites.
- AtlasResearch protections
- ProbeBenchmark clients
- AtlasRecord observed behavior
Inside Atlas
Inspect a website.
Understand the publicly observable automation and protection surface of a website: infrastructure, protection technologies, and how protection appears to be applied across the site, each with an evidence level.
Inspect observes. Probe tests.
Inspect is technology research. It reports what appears to be deployed, never site-specific techniques. When active testing is needed, verified site owners use Probe.