Diese Seite gibt es noch nicht in Ihrer Sprache. Sie lesen den englischen Text.
Glossary
Plugin array
A plugin array is the list of browser plugins any page can read about you at navigator.plugins without asking.
What the list holds today
Plugins as a way of running outside code inside a browser are gone. What remains is a fixed set of entries for the document viewer the browser already ships with, and every desktop Chrome reports the same ones.
The same entries everywhere
The names describe the built-in document viewer, not anything you installed.
A pair of document types behind them
Each entry answers for the same two document types, which is what a thorough check reads next.
Extensions are not in here
What you added from a store lives elsewhere, and a site cannot list it through this reading.
Your browser right now
These values are read in your browser on this page and nothing leaves it. The first row is the length of the list, which is the whole of what a quick check reads.
Ihr Gerät, jetzt gerade
- Plugins in the list
- wird auf Ihrem Gerät gemessen
- Platform
- wird auf Ihrem Gerät gemessen
- The name it reports
- wird auf Ihrem Gerät gemessen
In Ihrem Browser gelesen und hier angezeigt. Nichts wird irgendwohin gesendet.
Why an empty list is loud
A desktop browser reporting nothing here has answered in a way ordinary visitors do not. Emptiness is rarer than any particular list and marks the session at once.
Automation strips it
Builds made to run without a window often report nothing, which is why this reading sits beside the automation flag.
A phone is a separate case
Phone browsers legitimately report nothing, so the list is judged against the machine the browser claims to be.
A long list is no better
Entries no released browser carries separate a session as surely as an empty list does.
What our engine does
Our browser is compiled from the Chromium source, so the entries come from the document viewer that source already contains. Nothing is laid over the page to produce them.
The self-test asks every profile whether the list is there at all, and on the acceptance run of the build shipping today it was.
The list was present and counted
The acceptance run records the length it read rather than a yes or no, so a list that shrinks later is visible.
length recordedThe reading runs in a real browser
The same script the app uses is executed on a page in a launched profile, not simulated.
on a real page
The lists that do still vary
Two neighbouring lists continue to describe your machine, and both are handled by trimming rather than by invention. A profile shows a subset of what is really there.
Installed fonts
The set a page can confirm is narrowed towards what the claimed machine would carry.
Cameras and microphones
The count is reduced towards what the profile claims, and a device that is not on the machine is never announced.
Why nothing is invented
An identifier for hardware that does not exist would itself be the mark, so the answer is only ever shorter than the truth.
How to check your own
The panel above shows what this browser reports, and the length alone tells you which side of the line you are on. A browser console answers the same question by name.
Inside the app the self-test asks in a profile, against the engine that profile launched, and reports the length it found.
What this does not do
- It does not tell two profiles apart. Every desktop Chrome reports the same entries, so nothing here makes one profile look unrelated to another.
- It does not invent a device. A profile shows a subset of the cameras and microphones the machine really holds, and this list stays the fixed one every desktop Chrome reports.
- It does not reshape the list for a profile claiming a phone. The entries come from the browser itself and read the same on every profile, so a check reading this list beside a phone name sees the desktop one.
- It does not list your extensions. What you installed is read another way, and nothing here changes that.
Check it
Every claim above comes from a file you can open.
- The self-test asks every profile for this list
- apps/desktop/src/lib/fpAudit.js
- What the built-in engine presents when a runtime has nothing
- apps/desktop/src/injected/fingerprint.js
- The acceptance run of the build shipping today
- engine/приёмка-отчёт.json
- The parts of a profile have to agree with each other
- apps/desktop/test/fingerprint-consistency.js
Questions
- Why does the list look the same on every computer?
- Because the entries describe the document viewer built into the browser rather than anything installed on your machine. Outside code as a plugin was removed from browsers years ago.
- Should I empty the list?
- No. An empty list on a desktop browser is rarer than any list at all and marks the session immediately.
- Do the entries differ between my profiles?
- Not on a desktop profile, and that is correct. A profile reporting its own private list would contradict every other Chrome on the internet.
- Is the order of the entries read?
- It can be. A check reading the names in order learns more than one that counts them, which is why the entries are left exactly as the browser produces them.
- Does the free check on this site show it?
- The panel above shows the length. The fingerprint check spends its rows on the readings that differ between machines, and this list does not.
See what your own profile answers
The self-test runs inside a profile and shows all 29 measurements, green and red alike.