Bu sayfa henüz sizin dilinizde yok. İngilizce metni okuyorsunuz.
Glossary
Device fingerprint
A device fingerprint is an identifier built from the machine itself: its screen, its graphics chip, its cores and its memory.
What the machine gives away
A page reads these in the first milliseconds of a visit and asks nothing for any of them. Each reading is ordinary on its own, and the set of them is not.
Screen and pixel density
The size in layout points and how many real pixels sit behind each of those points.
The graphics string
The vendor and renderer names the graphics chip reports, which on many machines name the exact model.
Cores and memory
How many processors the browser admits to and the figure it rounds its memory to.
Touch points
How many fingers the screen accepts. Zero on an ordinary desktop and five on most phones.
Installed fonts
Measured by drawing a string and comparing widths, which is ordinary page work and needs no permission.
What this machine reports now
These five come from the computer you are reading this on. A second browser on the same machine would repeat most of them exactly.
Makineniz, şu anda
- Screen
- makinenizde ölçülüyor
- Device pixel ratio
- makinenizde ölçülüyor
- CPU cores
- makinenizde ölçülüyor
- Memory
- makinenizde ölçülüyor
- Touch points
- makinenizde ölçülüyor
Tarayıcınızda okundu ve burada gösteriliyor. Hiçbir yere gönderilmiyor.
A device is a whole
The readings have to belong to one machine that somebody actually built. A phone screen beside a desktop graphics string describes a computer nobody has ever sold.
So a profile draws a whole device at once rather than assembling one from readings each taken out of a list of its own.
Phone models
Each carries its own screen, pixel density, graphics string, cores, memory and vendor fonts.
22Tablet models
The same rule, with the touch points and the usable screen height of a tablet rather than a desktop.
7Readings in the self-test
Screen, memory, cores and the graphics strings are among them, each reported by name.
29
Where a profile gets its device
The values are derived from the profile seed and handed to the engine as it starts. They are not written over the page by a script after it has loaded.
That is why the document, a frame and a worker answer the same numbers. All three inherit one source instead of being patched one at a time.
Often confused with
Browser fingerprint
The wider set, which also holds what the browser reports about itself and what it draws.
Canvas fingerprint
One drawing surface inside that set. The graphics chip shapes it, so the two overlap without being the same thing.
A hardware serial number
A page cannot read one. Everything here is inferred from behaviour a page is allowed to observe.
A virtual machine
It hands you a different device at the cost of tens of gigabytes, and it announces itself as a virtual machine.
How to read your own device
The panel above shows five readings for this browser. Inside a profile the self-test names every device check it runs and shows what each one answered.
Then compare two profiles on one computer. Readings that differ across the pair are the whole point of the exercise.
What this does not do
- It does not change your hardware. The engine answers with the device the profile was given, while the computer under it stays exactly what it is.
- It does not make the readings unavailable. A browser that returns nothing for its screen or its cores stands out further than any value it could have given instead.
- It does not cover the exit address. A device that reads as a phone arriving from a data centre is a pair that does not fit together.
- It does not cover behaviour or account ties. Both live outside the browser, and neither is touched by any reading on this page.
Check it
Each claim above is one place in the code and one stand.
- A device is drawn as a whole rather than reading by reading
- packages/shared/src/index.js
- A phone has to be a phone in every reading at once
- apps/desktop/test/mobile-really-mobile.js
- The parts of one device have to agree with each other
- apps/desktop/test/fingerprint-consistency.js
- The device checks the self-test runs
- apps/desktop/src/lib/fpAudit.js · apps/desktop/test/fp-audit.js
Questions
- Can two profiles on one computer read as two devices?
- On the readings a page can take, yes. The values come from each profile's own seed, and a separate check in the app says whether another profile shares them.
- Does clearing storage change a device fingerprint?
- No. Storage lives on your side, while these readings are recomputed from the machine on every single visit.
- Is a rare device safer?
- Usually the opposite. Rarity is what makes a set easy to recognise again, so an ordinary machine is the quieter choice.
- Do phones read differently from desktops?
- Strongly, and in several places at once. Touch points, pixel density, memory and the vendor font list all move together.
- How do I see what mine reports?
- The panel above covers this browser. A profile reports all 29 measurements from inside the app, against the engine it launched.
Next to this
Digital fingerprint
The wider word, and the three layers above the machine.
Browser fingerprint
The set a page builds, of which the device is one part.
Hardware concurrency
The core count on its own, and why a count that does not fit its chip stands out.
Fingerprint and its editor
What you can change and what changing it costs.
See the device your profile presents
The self-test runs inside a profile and reports every device check by name, green and red alike.