Skip to Content
Platform Ontology

Automation framework leftovers

Test tools leave marks on the page that a script can look for.

Gets silentlyWhile you use it

Selenium, PhantomJS, Playwright and Puppeteer inject helper properties or bindings into the page, such as cdc_ prefixed document keys, callPhantom, or names starting with __playwright and __pw. Bot defenses scan the window and document for these names. Operators rename or remove them with patches.

What it can and can't do

What the user does: Nothing. It runs from page script

It can

  • List window and document properties
  • Match known test tool names
  • Block or challenge clients with a hit
  • Combine hits with the webdriver flag

It cannot

  • Catch a tool that renames its marks
  • Tell a good test from a bad scrape
  • See what the script does
  • Prove who runs it

How it differs between platforms: Names change between driver versions and are removed by stealth patches. Only a known name is a hit, so new tools pass until lists catch up.

Browser support

Version notes
  • Chrome: Names depend on the driver and its version
  • Edge: Same Chromium behavior
  • Firefox: Some drivers leave marks here too
  • Safari: Fewer known marks
  • Chrome on Android: When driven by Selenium or Appium
  • Samsung Internet: Not verified

How a site asks for it

APIObject.keys(window) and document for names like $cdc_, __playwright*, __pw*, callPhantom, _phantom, domAutomation, __nightmare, __selenium*
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Page script enumerates window and document property names
  2. Script matches them against a list of known automation names
  3. A hit adds to a bot score

Data you get

Shape: list
How often: static per session

FieldTypeUnitRangePrecision
matchedNameslistNoneautomation related property names found on window or documentNot listed
countintegerNone0 in an ordinary browserNot listed

Technical limits

  • Names vary by version
  • Patched by stealth plugins
  • Says nothing about intent

The story

What it is

Automation tools sometimes leave their own handwriting on the page. Defenders keep a list of the known handwriting.

For you

You never see it. A normal browser has none of these names. Test tools you run may be spotted by them.

For makers

Keep your list current and match exact known names, not loose patterns, to avoid false positives. Treat a hit as strong, and a miss as meaning nothing.

Where you see it

TypeExampleApps
securityA web firewall flags sessions that carry a cdc_ marker on the document.Cloudflare
shoppingA ticket seller blocks scripted browsers with Playwright marks.None named
gamesA browser game bans accounts whose window has automation bindings.None named
adsAn ad network discards views with PhantomJS marks.None named
developerA tester checks a bot detection page to see which marks their framework leaves.Selenium, Playwright
analyticsA traffic tool flags visits with known automation names as bots.None named

Risks

  • Blocks useful automation
  • Easy to patch

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.2Rough identifying entropy, when known

History

  • 2016, Chrome: cdc_ style ChromeDriver marks widely documented by bot detection write ups

Sources

How well checked: Inferred from related behavior.

On this page