Free · Runs in your browser · No signup
Am I Detectable?
See exactly what bot detection systems see when your scraper visits a site. Canvas, WebGL, User-Agent, headless flags, all checked client-side, instantly.
Running fingerprint checks in your browser…
Want to dig into one signal?
What this tool actually checks
Browser fingerprinting combines dozens of signals into a near-unique identifier for your device. Bot detection systems like Cloudflare, DataDome, PerimeterX, and Akamai use the same signals to decide whether you're a real person or a scraper. This tool surfaces every signal a site can read from your browser, side by side with a verdict on whether each one looks normal or screams “automated.”
Identity signals
User-Agent string, platform, languages, timezone, screen resolution, hardware concurrency, device memory, touch points. The basics every site reads on first load.
Hardware fingerprints
Canvas hash (how your GPU draws text), WebGL vendor and renderer (which GPU you have), Audio context hash. Hardest to spoof, most stable across sessions.
Automation tells
navigator.webdriver, missing window.chrome.runtime, Notification.permission inconsistency, empty plugins, headless UA strings. The classic flags every stealth plugin tries to hide.
Why no TLS / IP check?
TLS JA3/JA4 and IP reputation require server-side inspection. This tool is fully static (no backend, nothing logged). For server-side signals, pair this with the IP reputation check at your proxy provider.
Frequently asked questions
→What is a browser fingerprint?
A browser fingerprint is the combination of signals a website can read from your browser, User-Agent, screen size, fonts, canvas rendering, WebGL hardware, timezone, language, plugins, and dozens of other properties. Together those signals are usually unique enough to identify a specific device, even with cookies disabled. Sites use this for tracking and for bot detection.
→Why is my scraper being detected even with proxies?
Proxies only change your IP. They don't change your fingerprint. If your headless browser still reports navigator.webdriver=true, missing chrome.runtime, an unusual WebGL renderer like 'Google SwiftShader', or a timezone that doesn't match the proxy's country, you're flagged regardless of how clean the IP is. Run the test on this page to see what you're actually leaking.
→How do I make my headless browser undetectable?
Start with stealth plugins (puppeteer-extra-plugin-stealth, playwright-stealth, undetected-chromedriver). Then patch the obvious leaks: spoof navigator.webdriver, fix the WebGL UNMASKED_RENDERER_WEBGL string, match timezone and language to your proxy, ensure window.chrome exists, and check that Notification.permission isn't stuck on 'denied'. Test after each fix using this page.
→Can a website really see my GPU?
Yes, via the WebGL UNMASKED_RENDERER_WEBGL extension, sites can read your real GPU vendor and model. Headless browsers running in cloud VMs typically report things like 'Google SwiftShader' or 'llvmpipe', which is an instant bot signal. Spoofing this requires patching the WebGL extension at the driver level.
→What is canvas fingerprinting?
A site draws text and shapes onto a hidden HTML canvas, then reads back the pixel data and hashes it. Tiny differences in your GPU, drivers, anti-aliasing, and font rendering produce a stable hash unique to your hardware. Two clean Chrome installs on identical OSes will still produce different hashes if the GPUs differ.
→Does this tool send my fingerprint to a server?
No. All detection happens client-side in your browser. Nothing is uploaded, stored, or logged. View page source if you want to verify.
→Is browser fingerprinting legal?
Yes, but disclosure is regulated under GDPR (EU) and similar privacy laws, sites using fingerprinting for tracking generally need consent. For bot detection (your case as a scraper) it's universal and unregulated.
→How do I generate a fake but realistic User-Agent?
Don't randomize blindly, bot detectors check whether your User-Agent string matches your other signals. A Windows UA with a macOS timezone and Linux WebGL renderer is a giveaway. Pick a real, current UA (Chrome on Windows is safest), then make sure platform, languages, timezone, and screen size all match a real machine with that UA. The /user-agent page on this site shows what your current UA actually claims.
Learning web scraping?
Foundations, static scraping, dynamic web, and APIs. A full curriculum on getting past bot detection.
Start the curriculum →