Skip to Content
Platform.Ontology

Extension presence probing

Detects installed Chrome extensions by fetching their exposed files.

Used to track youDevice detailsBrowser stateWeb browsersWhen the page loadsWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11None
EdgeSupported792020-01-15None
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidNot supportedNot availableNot listedMobile Chrome has no extensions
Samsung InternetNot supportedNot availableNot listedNone

How a site asks for it

APIfetch('chrome-extension://<32-char-id>/<file>') succeeds only if exposed via web_accessible_resources; DOM scanning for injected IDs
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
extension idstringNone32 lowercase letters a to pexact
hitbooleanNoneinstalled or notNot listed
probe list sizeintegerids38 (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

TypeExampleApps
securityA bot defence checks for known automation extensions to stop scraping.LinkedIn
socialA professional network scans for extensions that scrape profiles, and bans accounts that use them.LinkedIn
adsAn ad platform tests for ad blocker extensions to decide whether to show a wall or an alternative ad.None named
gamesA game site detects cheat helper extensions and removes players from ranked modes.None named
bankingA bank detects remote access or screen sharing extensions that scammers use and shows a warning.None named
accessibilityA researcher shows how a site could learn that someone uses a screen reader extension.None named
analyticsA 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

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility1 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits12Rough 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

Sources

How well checked: Checked against real behavior.

On this page