See what protects a website.
Identify anti-bot systems, CAPTCHA providers, and browser fingerprinting signals with a free Chrome extension. Inspect the evidence before you build your scraper or automation workflow.
Free Chrome extension · No account required
8
CAPTCHA detectors
15
Anti-bot / WAF detectors
21
Fingerprinting detectors
Free
No account required
Scrapeless Anti-bot Detector is a free Chrome extension that identifies anti-bot / WAF systems, CAPTCHA providers, and browser fingerprinting activity from signals on the pages you visit. It shows matched technologies and supporting evidence so you can investigate website protection before choosing a scraping or automation approach. The extension detects protection; it does not bypass it or solve CAPTCHAs.
44 Built-in detectors
Explore three categories of page protection. Each result reflects a match to a detector rule, rather than a guarantee about a website’s entire security setup.
Recognize systems such as Cloudflare Bot Management, Akamai, and DataDome from their observable signals. Use the result to narrow down which protection technology to investigate when requests are blocked or challenged.
Find supported CAPTCHA providers even when a page exposes a script or widget before showing a visible challenge. Provider detection helps you understand what your users or browser workflow may encounter.
Provider identification does not guarantee reCAPTCHA version classification or that a challenge is currently active.
Observe when a page accesses supported browser APIs, including Canvas, WebGL, Audio, and WebRTC. This adds context to an automation investigation; API activity alone does not prove malicious tracking or explain why a request was blocked.
Coverage based on the bundled detector rules, reviewed September 23, 2026. No match does not guarantee that a site has no protection.
Move from an initial signal to evidence you can review, keep, and use in your own investigation.
Open a detection card to inspect the matched provider, category, confidence score, and contributing methods. Follow the evidence instead of relying on a vendor name alone.
JavaScript hooks watch supported APIs as the page uses them. This helps distinguish observed API activity from a library name that merely appears in page markup.
Use local scan history to review what you encountered across pages. Copy detection data for debugging notes and compare findings during an investigation.
Read, edit, disable, or add detector definitions in the extension. Configure matching conditions and confidence values when your investigation needs a different rule.
The analytics board summarizes your own stored scan history, including detection trends, vendor rankings, category distribution, and vendors that appear together.
Repository SDKs cover browser JavaScript, Node.js, Python, Go, Java, C#, Ruby, PHP, and Rust. They expose detection results for extension-backed workflows.
Choose the next tool based on whether you need page content or an interactive browser session.
The extension compares observable page and browser signals with its detector definitions. Different rules use different combinations of evidence.
Install the extension, open or reload the target page, and let its normal page-load detection run.
Supported signals are evaluated against enabled detector rules for providers and fingerprinting activity.
Open the extension to review matches, then decide what to investigate or test next.
Eight signal types supported by the detector catalogue
These are catalogue capabilities, not eight mandatory checks for every vendor. The extension does not inspect TLS/JA3/JA4 fingerprints or offer a standalone hosted classification API.
Use the free detector to gather context before spending time changing clients, proxies, or browser workflows.
A scraper returns a challenge instead of page content. Visit the page in Chrome and inspect the detected anti-bot provider and matched evidence. Use that context when testing access through Web Unlocker.
A workflow must click, scroll, or preserve state across multiple steps. Check the page’s CAPTCHA and fingerprinting signals, then evaluate an Agent Browser session for the interactive workflow.
Check whether a CAPTCHA integration exposes recognizable signals on your site. Compare pages and keep findings for your team. Detection is a diagnostic aid, not a security certification.
Explore detection results, scan history, custom rules, and settings in one extension.
Choose by the job you need to complete, not just the vendor name detected. A detection match does not guarantee that another product will handle every target; test your own page and workflow.
Send a target URL and retrieve rendered content through an API, with managed access handling.
Run browser automation in a cloud browser with the tools and session control your workflow needs.
| Your task | Start with | What you get |
|---|---|---|
| Identify page protection | Anti-bot Detector · Free | Matched technologies and detection evidence. |
| Retrieve public page content | Web Unlocker · Paid product | Content returned through a managed API request. |
| Run interactive automation | Agent Browser · Paid product | A cloud browser session controlled by your framework. |
The free extension does not include paid API usage. Review current Scrapeless pricing for product plans and billing.
On GitHub, choose Code → Download ZIP, then unzip it.
Open chrome://extensions/, enable Developer mode, and select Load unpacked.
Choose scrapeless-extension/ inside the extracted repository.
Visit or reload the page, then click the extension icon to view detected providers and matched signals.
