Extension presence probing
Detects installed Chrome extensions by fetching their exposed files.
In one line
Can find out which Chrome extensions you have by testing known files
Detects installed Chrome extensions by fetching their exposed files.
Learns which extensions the person runs: job tools, ad blockers, accessibility aids, religious or political filters. LinkedIn probes about 6,236 IDs, mapping the result to a named member.
What it can and can't do
What the user does: Nothing. It happens when the page loads in Chrome or Edge
It can
- Test thousands of extension IDs one by one (LinkedIn tests about 6,236)
- See extensions like ad blockers, job tools, and accessibility aids
- Match your list to a named account if you are signed in
- Use the list to tell you apart from other visitors
It cannot
- Work in Firefox, Safari, or on mobile browsers
- See extensions that hide their files from sites
- See your extension settings or data
- See what other tabs show
How it differs between platforms: Only desktop Chrome and Edge are open to this. Firefox, Safari, and mobile browsers are not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | None |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Not supported | Not available | Not listed | Mobile Chrome has no extensions |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | fetch('chrome-extension://<32-char-id>/<file>') succeeds only if exposed via web_accessible_resources; DOM scanning for injected IDs |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | none needed (no grant) |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: object
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
extension id | string | None | 32 lowercase letters a to p | exact |
hit | boolean | None | installed or not | Not listed |
probe list size | integer | ids | 38 (2017) to about 6,236 (2026) | Not listed |
Technical limits
- Only works if the extension exposes a resource
- Firefox uses random per-install UUIDs; Safari does not expose IDs
- Chromium only
The story
What it is
Checks which browser extensions you have installed by testing for their hidden files.
For you
You never see it. A page quietly tries to open files that only exist if a specific extension is installed. The result can reveal job tools, ad blockers, accessibility aids and more.
For makers
Extensions say a lot about a person: work, health, beliefs. Some sites use the list to catch scrapers or prohibited tools. It can also be used for profiling, which is why it is controversial and heavily criticised.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A bot defence checks for known automation extensions to stop scraping. | |
| social | A professional network scans for extensions that scrape profiles, and bans accounts that use them. | |
| ads | An ad platform tests for ad blocker extensions to decide whether to show a wall or an alternative ad. | None named |
| games | A game site detects cheat helper extensions and removes players from ranked modes. | None named |
| banking | A bank detects remote access or screen sharing extensions that scammers use and shows a warning. | None named |
| accessibility | A researcher shows how a site could learn that someone uses a screen reader extension. | None named |
| analytics | A fingerprinting vendor adds the extension list to a stable device ID. | FingerprintJS |
Risks
- Can reveal work, health or beliefs
- Hidden and hard to opt out
Good uses and abuse
Legitimate uses
- Detect scraper extensions
- Compatibility
Known abuse
- Inferring religion, politics, disability, job search from extensions
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 1 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 12 | Rough identifying entropy, when known |
A real example: LinkedIn
Core of BrowserGate: parallel fetch to chrome-extension URLs for ~6,236 IDs, plus DOM scan; Chrome-family only.
History
- 2017-01, linkedin: LinkedIn probe list starts at 38 ids (alleged)
- 2026-04, linkedin: BleepingComputer confirms 6,236 ids checked
Related capabilities
Related
- Ad blocker detection. Can tell if you use an ad blocker and roughly which filter lists
Sources
- BleepingComputer: LinkedIn scans for 6,000+ Chrome extensions
- BrowserGate: how LinkedIn's script works
- mdp/linkedin-extension-fingerprinting
How well checked: Checked against real behavior.