Identify the defense layer before you burn unlock credits
Website AntiBot
Probe a URL through a live session and learn which vendor, challenge type, and fingerprint gap will block your scraper. Pick Crawler, Rendering, or WebUnlocker with evidence instead of trial and error.
- Vendor classification for Cloudflare, DataDome, Akamai, Imperva, and peers
- TLS, header, and browser signal breakdown for fingerprint tuning
- Run before WebUnlocker when pass rates drop on a target
Pre-flight
probe
Vendor
classification
TLS
signal audit
Mode
routing hints
Detect before you scale, or before you burn unlock credits
Blocking is the scraper's real bill. AntiBot probes one URL through BrowserSolver egress and returns vendor, challenge type, and a suggested next mode so you do not guess between Crawler, Rendering, and WebUnlocker.
- One URL per probe call, same HTTP API shape as your production scrapers
- Vendor signatures for Cloudflare, DataDome, Akamai, Imperva, PerimeterX, and peers
- Mode hints point to Crawler, Rendering, or allowlisted WebUnlocker
Runbook JSON for scraping teams
Use probe output in tickets, compliance reviews, and pipeline branching, then feed the same URL list into the mode AntiBot recommends.
- TLS and header signals when fingerprint coherence is the issue
- Pair with Website Technology to correlate stack depth and access difficulty
- Re-probe when pass rates drop overnight, vendors change protection without notice
Diagnose before you scale
Pick the right mode before you scale unlock traffic.
Stack ID
Name the vendor and challenge family.
Fingerprint scan
Surface browser and TLS mismatches.
Challenge map
See JS, CAPTCHA, or rate limits.
Vendor DB
Signatures for major bot vendors.
TLS profile
Highlight JA3/JA4 expectations.
Mode hint
Suggested Crawler, Render, or Unlock path.
Frequently asked questions
Credits, scrape types, and billing before your first production job.
Does AntiBot bypass challenges?
No, it maps protection layers. Switch to Website Rendering for JS-heavy pages or Website WebUnlocker on an allowlisted domain once you know which defenses are active.
When should I run AntiBot in a scraping workflow?
Run it when a new domain returns unexpected 403s, CAPTCHA interstitials, or empty HTML. Use the output to decide whether cheap HTTP, headless render, or allowlisted unlock is the right next step.
Pick your next move
Wire up an integration, review plans, or read the API reference before your first job.
Integrations
Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.
Scrape your first blocked URL
Fetch, render, screenshot, or unlock from one dashboard. Proxies, browsers, and anti-bot lanes stay on our side.
- 500 signup credits
- No card to start
- All scraping modes