I4∇ROOT
What does your browser tell every site about your machine? — free, no ads, no sign-up

Hardware fingerprint test

Reading…

Asking your browser what it hands out about this machine…

— visitors · — checks run, all time — one visit per person per 20 minutes; every test counts. This counter stores a number, nothing about you.

Found something open? Paste your log and get the fix plan →

Graphics card (GPU)

reading…

—

Your device

reading…

—

Screen & senses

reading…

ALWAYS READABLE

What a site can learn, and why it matters

Live diagnostic log — every reading, raw 
(run the test first)

Why check it here

Every request, explained. Open DevTools → Network and count what this page does: the page itself, plus two tiny pings to this site's own counter — one counts you as a visitor (de-duplicated: at most once per 20 minutes), one counts the test. Each carries a number and a random browser id — never a single hardware reading. Press "Test again" and watch: exactly one more ping, the test counter. The page's security policy (connect-src 'self') forbids talking to anyone but this site, so no third party can ever be contacted — and your readings never leave your screen.

The real names. Not "a GPU was detected" — the actual renderer string trackers collect, the exact device model on Android, the RAM bucket, the battery level. What they see is what you see.

Dangers in plain words. Every reading comes with one sentence on what it tells a tracker about you — identity, money, or location — not a raw data dump you have to interpret yourself.

Both directions. On a wide-open browser you see exactly what leaks; on a hardened one (Brave, Tor, Firefox with protections) you see the masking working — and which readings no browser hides.

Clean. Free. No ads, no account, no cookies, nothing to install. One page that answers one question.

Hardware fingerprinting, in plain words

What is a hardware fingerprint?
A way to recognize you without cookies. Each reading on this page — GPU model, CPU count, RAM, screen, time zone — narrows down who you are. Alone each is harmless; combined they can make your browser one-of-a-few, or one-of-one. Delete cookies, switch to private mode — the hardware stays the same.
Why does my graphics card name matter?
It is one of the strongest single signals. The renderer string often names your exact GPU model and driver stack — enough to separate a gaming rig from an office laptop from a phone, and to keep recognizing the same machine across visits. It also hints at what your machine cost.
What is the ANGLE (…) string I see?
Chromium browsers render WebGL through a layer called ANGLE, and the string carries the vendor and the real card name inside it — for example ANGLE (NVIDIA, NVIDIA GeForce RTX 3060 …). This page pulls the model name out of it for you and keeps the raw string in the log.
Why does my phone show its exact model?
On Android, Chromium-family browsers answer the model hint of User-Agent Client Hints with the device's real model code. Combined with OS build and architecture it can date your phone and estimate what it cost — a signal advertisers openly use for price steering.
How do I reduce what leaks?
Browsers differ by design. Tor Browser and Safari answer with constants; Firefox rounds or blocks several readings (and privacy.resistFingerprinting tightens it further); Brave randomizes. Chrome and Edge hand out the most. Re-run this page in another browser and watch the verdict change.
Is this test private?
Yes — and you can verify it instead of believing it. All readings happen locally and are shown to you only. The page's network policy allows exactly one destination: this site itself, and the only thing sent there is the counter — a visit (+1) and a test (+1), each a number and a random browser id, never anything about your hardware. No third party is contacted, ever; the policy (connect-src 'self') makes anything else technically impossible. Count the requests in DevTools — the live log below lists the same ones.

How it works. Your browser exposes a set of read-only properties and small APIs about the machine it runs on: the WebGL WEBGL_debug_renderer_info extension and the WebGPU adapter for the graphics card, User-Agent Client Hints for device model and OS build, plus hardwareConcurrency, deviceMemory, the Battery and Network Information APIs, screen metrics and your time zone. This page simply reads them, names each one in plain words, and scores how much of your hardware identity this browser hands out. Your readings are never uploaded — the only thing this page sends is its own visit counter (+1, a number, to this site alone). Also here: WebRTC leak test and What is my IP — the 20-server race. Part of I4ROOT — trance music, 100% human-made.