Extension traces in the DOM and globals
Browser extensions leave marks in the page that the page can see.
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
| API | document.querySelectorAll for injected nodes; compare window globals against a clean iframe; MutationObserver on documentElement |
| Browser compat keys | api.MutationObserver |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Clear site data |
| Inside an iframe | Same as top level |
Typical flow
- Page calls the API
- Browser answers with no prompt
- 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
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
injected nodes | list | None | ids, classes, custom elements, attributes on html or body | Not listed |
new globals | list | None | names missing from a clean window | Not listed |
chrome-extension:// URLs | list | None | image or script sources inside the document | Not 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
| Type | Example | Apps |
|---|---|---|
| news | A news site notices an ad blocker and shows a notice. | None named |
| social | A site checks for scraping extensions. | None named |
Risks
- Reveals interests and tools
- Adds fingerprint bits
What the platform says
- Chrome for Developers: Content scripts. Explains how extensions run scripts in pages and what they can change.
Good uses and abuse
Legitimate uses
- Detect scraper extensions
- Compatibility
Known abuse
- Inferring habits from extensions
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 6 | Rough identifying entropy, when known |
A real example: LinkedIn
BrowserGate also scans the DOM for injected extension nodes beside its chrome-extension URL probe.
Related capabilities
Related
- Extension presence probing. Can find out which Chrome extensions you have by testing known files
- Ad blocker detection. Can tell if you use an ad blocker and roughly which filter lists
- Extension probe defenses. Can hide an extension from the address probe, if the extension opts in
- Spectroscopy DOM scan for extension traces. Can look through its own page for traces that extensions leave behind
Sources
How well checked: Checked against real behavior.