Skip to Content
Platform.Ontology

Automation (webdriver) flag

True when the browser is being driven by Selenium, Playwright, Puppeteer or similar.

Gets silentlyDevice detailsBrowser identityWeb browsersWhen the page loadsWhile you use it

In one line

Can tell if Selenium, Playwright, or Puppeteer is controlling the browser

True when the browser is being driven by Selenium, Playwright, Puppeteer or similar.

Tells a site a script, not a person, may be on the page. Bot defenses use it with other tells (missing plugins, headless UA) to block or challenge scrapers and agents.

What it can and can't do

What the user does: Nothing. It happens when the page loads

It can

  • Check whether the browser says it is automated
  • Combine it with other clues like a headless label
  • Block, slow, or challenge likely scrapers and AI agents

It cannot

  • Be sure; bot makers can hide the flag
  • See what the script is doing
  • Tell a good script from a bad one
  • Show true when you browse by hand

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported632017-12-06None
EdgeSupported122015-07-29None
FirefoxSupported602018-05-09None
SafariSupported10.12017-03-27None
Safari on iPhoneSupported10.32017-03-27None
Chrome on AndroidSupported632017-12-05None
Samsung InternetSupported8.02018-07-18None

How a site asks for it

APInavigator.webdriver
Browser compat keysapi.Navigator.webdriver
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnone needed (no grant)
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: object
How often: static per session

FieldTypeUnitRangePrecision
webdriverbooleanNonetrue when under WebDriver controlNot listed

Technical limits

  • Trivially spoofed by stealth plugins
  • Does not identify who runs the automation

The story

What it is

A simple true or false that says a script, not a person, is driving the browser.

For you

You never see it. In an ordinary browser it says false and nothing changes. If you run an automation tool, some sites will challenge you.

For makers

It is the cheapest bot test: one line of code. Defences use it with other tells like missing plugins and headless user agents. It catches lazy scrapers but not skilled ones.

Where you see it

TypeExampleApps
securityA web firewall serves a challenge page to clients with the flag set.Cloudflare
shoppingA concert ticket seller blocks scalper scripts that run in automated browsers.Ticketmaster
gamesA multiplayer browser game bans automation that plays for you.None named
adsAn ad network refuses to count ad views from automated browsers.None named
analyticsA traffic tool removes automated visits so your numbers are cleaner.Google Analytics
developerA QA engineer sees the flag in a test run and sets sites to test mode.Puppeteer
travelA flight site stops fare scraping bots by challenging automated browsers.None named

Risks

  • Blocks useful automation
  • Easy to hide

What the platform says

Good uses and abuse

Legitimate uses

  • Bot defense
  • Fraud scoring

Known abuse

  • Blocking legitimate agents

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits0.1Rough identifying entropy, when known

A real example: LinkedIn

Collected as automation flag and framework detection. Read by the LinkedIn APFC fingerprint script (48 features, alleged by BrowserGate, partly confirmed by BleepingComputer).

Sources

How well checked: Based on official documentation.

On this page