Plugins and MIME types
Lists installed plugins and supported MIME types.
Once a strong fingerprint. Since Chrome 94 the list is a fixed set of PDF viewers, so it now adds little.
What it can and can't do
What the user does: Nothing. It happens when the page loads
It can
- List the PDF viewers your browser has
- List the file types it can open
- Use that list as one small trait of your browser
It cannot
- List other plugins, since modern browsers show a fixed set
- See your files
- Ask permission first
- Tell you apart on its own, since most people share the same list
How it differs between platforms: Since Chrome 94 the list is a fixed set of PDF viewers, so almost every Chrome user looks the same.
Browser support
How a site asks for it
| API | navigator.plugins, navigator.mimeTypes |
| Browser compat keys | api.Navigator.plugins |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Script reads the value
- Value joins the fingerprint payload
Data you get
What comes back: Plugins and MIME types
Shape: list
How often: static
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
plugins | list | None | up to 17 (dataLimit) | Not listed |
mimeTypes | list | None | up to 27 (dataLimit) | Not listed |
Technical limits
- Fixed lists since 2021 (Chrome 94, Firefox 99)
The story
What it is
A script lists installed plugins and file types your browser can open. Modern browsers return mostly a fixed list.
For you
You never see it. In the past this list showed old add ons like Flash and PDF viewers and was very unique. Now most browsers show a short fixed list, so it reveals far less.
For makers
Years ago, plugin lists were a top fingerprint. Browsers have since standardized the answer. Bot detectors still use it, because an empty list is a sign of a headless script.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A bot detector sees an empty plugin list, which real desktop browsers do not have, and raises the risk score. | Akamai Bot Manager, Cloudflare |
| developer | A site checks whether the browser can show a PDF inline or needs to offer a download. | None named |
| ads | An older ad script still adds the plugin list to its device ID, though it adds little now. | None named |
| games | Old browser games needed plugins like Flash. Today they run through standard browser features instead. | None named |
| enterprise | A company portal checks for a PDF viewer before it opens a contract inline. | None named |
| analytics | A visitor counting tool splits traffic by browser family using the plugin list as one clue. | None named |
| education | A school site checks that the browser can open the assignment file type before loading it. | None named |
Risks
- Mostly historic
- Empty list flags bots
Good uses and abuse
Legitimate uses
- PDF viewer detection
Known abuse
- Fingerprint input
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 3 | Rough identifying entropy, when known |
A real example: LinkedIn
Collector key(s): plugins, mimetyps. dataLimit 17 and 27.
History
- 2021, Chrome 94: Fixed PDF viewer list
Related capabilities
Related
- APFC / DNA device fingerprint (abuse prevention features). Can collect about 48 device traits and send them in secret with later requests
Sources
How well checked: Based on official documentation.