Skip to Content
Platform Ontology

Extension traces in the DOM and globals

Browser extensions leave marks in the page that the page can see.

Gets silentlyWhile you use it

Ad blockers, password managers and similar tools add elements, attributes and global variables to pages. A page that looks for those marks can tell which of them you run. It works in all desktop browsers.

What it can and can't do

What the user does: None, the page reads it silently

It can

  • See elements an extension inserted
  • See attributes an extension set on html or body
  • See globals an extension exposed to the page world

It cannot

  • List extensions that do not touch the page
  • Read extension settings or data
  • See isolated world variables

How it differs between platforms: Desktop browsers. Extension code in the isolated world is hidden, but anything it writes to the page DOM or MAIN world is visible.

Browser support

Version notes
  • Chrome: Content scripts run in an isolated world but the DOM they change is shared
  • Edge: Same as Chrome
  • Firefox: Same
  • Safari: Safari extensions can inject too
  • Safari on iPhone: Extensions exist but the report lists no support
  • Chrome on Android: No extension support

How a site asks for it

APIdocument.querySelectorAll for injected nodes; compare window globals against a clean iframe; MutationObserver on documentElement
Browser compat keysapi.MutationObserver
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsPer origin
How to take it backClear site data
Inside an iframeSame as top level

Typical flow

  1. Page calls the API
  2. Browser answers with no prompt
  3. Page reads the result

Data you get

What comes back: Browser extensions leave marks in the page that the page can see.
Shape: object
How often: on demand

FieldTypeUnitRangePrecision
injected nodeslistNoneids, classes, custom elements, attributes on html or bodyNot listed
new globalslistNonenames missing from a clean windowNot listed
chrome-extension:// URLslistNoneimage or script sources inside the documentNot listed

Technical limits

  • Only extensions that modify the page are visible
  • Content script isolated world variables are hidden
  • Spectroscopy style timing signals are low confidence

The story

What it is

The page looks for the footprints extensions leave behind.

For you

A site can notice that you run an ad blocker or a password manager without asking.

For makers

Makers detect ad blockers to show a wall, and detect scraping or automation extensions.

Where you see it

TypeExampleApps
newsA news site notices an ad blocker and shows a notice.None named
socialA site checks for scraping extensions.None named

Risks

  • Reveals interests and tools
  • Adds fingerprint bits

What the platform says

Good uses and abuse

Legitimate uses

  • Detect scraper extensions
  • Compatibility

Known abuse

  • Inferring habits from extensions

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits6Rough identifying entropy, when known

A real example: LinkedIn

BrowserGate also scans the DOM for injected extension nodes beside its chrome-extension URL probe.

Sources

How well checked: Checked against real behavior.

On this page