BROWSER USE

- Browser Use Agents: give Browser Use a task and receive completed work. API V4 is current for new integrations.
- Browser Infrastructure: connect your agent or automation to managed browsers through SDK, REST, or CDP. Starts at $0.02/browser-hour.
- Developer tools: Open Source, Browser Harness, SDK, and MCP support the two products above.

[Developer Index](https://browser-use.com/index.md)
[Product Map](https://browser-use.com/llms.txt)
[Full Product Context](https://browser-use.com/llms-full.txt)
[Pricing](https://browser-use.com/pricing.md)
[Cloud Docs](https://docs.browser-use.com/cloud/quickstart)
[Open Source Docs](https://docs.browser-use.com/open-source/introduction)

---

# Bot Detection Test: Is Your Browser Detected as a Bot?

## Bot Detection Test

See whether your browser looks automated. Free checks for navigator.webdriver, headless Chrome, user agent and client hint mismatches, WebGL and plugins, run in your own browser.

## How it works

### Open the page

The checks start on their own in the browser you opened this page with, whether that is your everyday browser or one driven by Playwright, Puppeteer or Selenium.

### Read each check

Every check says pass or suspicious, shows the raw value it read, and gives a one-line reason. Info rows are shown for reference and do not count toward the verdict.

### Fix and run again

Change a launch flag, a user agent override or a stealth setting, then press Run again to see which signals moved.

### Are my results sent or stored?

No. The checks run in JavaScript in this tab. One request goes to this site to read back the User-Agent, Accept-Language and Sec-CH-UA headers your browser sent, so they can be compared with JavaScript. They are not logged or saved. The site's usual analytics records that the test ran, not what it found.

### Why does my normal browser show a flag?

Some flags have innocent causes: a disabled GPU removes WebGL, and privacy extensions can rewrite navigator properties. Each row shows the raw value it read so you can judge.

A page sees only what its JavaScript can read. [What this test cannot see](https://browser-use.com/tools/bot-detection-test#limits).

## What this test can and cannot see

Every check runs in this tab with JavaScript, and the results stay here. The test makes one request, to this site, to read back the headers your browser just sent, and that read-back is not logged. The site's usual analytics records that the test ran, not what it found. Real anti-bot services also use signals a web page cannot read: the [TLS](https://developers.cloudflare.com/bots/additional-configurations/ja3-ja4-fingerprint/) and [HTTP/2](https://www.blackhat.com/docs/eu-17/materials/eu-17-Shuster-Passive-Fingerprinting-Of-HTTP2-Clients-wp.pdf) fingerprint of your connection, the [reputation of your IP address](https://www.cloudflare.com/learning/bots/what-is-bot-management/), and [how you behave across many requests](https://developers.cloudflare.com/bots/concepts/bot-detection-engines/). Passing here does not mean you pass there.

## If your automation fails these checks

[Browser Use cloud browsers](https://browser-use.com/stealth-browsers) run a maintained Chromium fork with stealth enabled by default and residential proxies. See how stealth browsers compare in the [browser benchmark](https://browser-use.com/benchmarks/browsers).