Skip to Content
Platform Ontology

Extension probe defenses

Browsers blunt the trick of probing for installed extensions by their fixed addresses.

While you use it

A page can test chrome-extension://id/file for extensions that expose resources. Chromium MV3 use_dynamic_url and Firefox's per install random address make that probe unreliable, and Safari does not expose stable ids.

What it can and can't do

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

It can

  • Make the extension address change per session in Chromium MV3
  • Give each Firefox install its own random address

It cannot

  • Stop DOM and global injection traces
  • Protect extensions that do not opt in

How it differs between platforms: Chromium needs the extension author to opt in. Firefox always randomizes.

Browser support

Version notes
  • Chrome: use_dynamic_url is an opt in per resource entry
  • Edge: Partial, medium confidence
  • Firefox: Random UUID per install blocks cross site fingerprinting, but a leaked UUID works within a session
  • Safari: safari-web-extension scheme. Packaging details are low confidence
  • Safari on iPhone: Safari scheme as on Mac
  • Chrome on Android: No extensions

How a site asks for it

APIweb_accessible_resources with use_dynamic_url (Chromium MV3); moz-extension://UUID; safari-web-extension://
Browser compat keyswebextensions.manifest.web_accessible_resources
How access is grantednone
What the user seesNone, set by the extension author
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: Browsers blunt the trick of probing for installed extensions by their fixed addresses.
Shape: object
How often: on demand

FieldTypeUnitRangePrecision
use_dynamic_urlbooleanNoneper resource entryNot listed
moz-extension UUIDstringNonerandom per installNot listed

Technical limits

  • Chromium MV3 only for use_dynamic_url
  • Safari packaging details are low confidence

The story

What it is

Defenses that stop a page from learning your extensions by guessing their addresses.

For you

Your extensions are harder to list from a web page when they use these defenses.

For makers

Extension authors enable use_dynamic_url to protect their users.

Where you see it

TypeExampleApps
productivityA password manager enables dynamic URLs so websites cannot detect it.None named

Risks

  • Not all extensions opt in

What the platform says

Good uses and abuse

Legitimate uses

  • Privacy for extension users

Known abuse

  • None

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

Sources

How well checked: Inferred from related behavior.

On this page