Skip to content
Automation environment check

Bot Detection

Review WebDriver, headless UA, CDP, Selenium/Puppeteer traces, navigator consistency and request headers for automation risk.

Pass--
Review--
Fail--

Detection groups

Inspect WebDriver and related environment clues. Automation, debugging tools and anti-detect browsers are different things; one signal cannot identify who is visiting.

Source browser-js

WebDriver / automation markers

navigator.webdriver, Selenium, Playwright, Puppeteer and injected globals.

--

UA / Headless

HeadlessChrome, bot/crawler strings and UA platform consistency.

--

CDP / DevTools

Error.stack serialization side effects and debugging-channel exposure.

--

Navigator / permissions

Languages, plugins, chrome object, permission state and browser capabilities.

--

Context parity

Main frame, iframe and worker UA, webdriver and language parity.

--

Request proof

Server-observed User-Agent, Accept-Language, HTTP and IP context.

--

Parameter evidence matrix

Every field keeps its collected value, status, penalty and rationale so engineers can isolate the exact anomaly.

Captured --
CheckValueStatusPenaltyNote

Parameter coverage

Sensitive permissions are not requested by default; only support and permission states are read.

navigator.webdriverCDPseleniumheadlesspermissionsMismatchiframeParityworkerParityheaderUaserverContextsourceCoverageserverAttestation
JSON

Raw parameters

Full JSON evidence includes local browser fields, iframe/worker parity, CDP probe and server-observed request headers.

{}