Browser Information

This page reads 21 things your browser hands to every site you visit, scores how identifiable that combination makes you, and builds a short ID out of it. All of it happens on your machine and nothing comes back to us. Which also means I have never seen one real reading from it, including yours.

That is an awkward admission on a page that is partly here to sell you the tool, so here is how I know what I am about to tell you. I fed it invented browsers by hand, changing one value at a time to see what moved. Every figure below came out of that. None of it came from watching visitors.

Hiding a value does not take it out of your ID. It puts a different value in. Block the graphics card and the rating falls two points while your ID stays exactly as steady as it was, and a browser that blocks the same thing a different way lands on a different ID again. Any site that hands you a rarity number has to compare you against a store of other people's fingerprints, which means putting yours in it. This one works the rating out on your machine from what is readable right now, so there is nothing to join.

1. Open the page. It reads your browser as it loads and fills in everything below. You get a brief "Detecting" flash while it does.
2. Read the badge before the tables. It rates you Low, Moderate, High or Very high out of 11 points, with a short note on why and a list of the signals it actually counted.
3. Copy your fingerprint ID. Hit Copy ID to grab the eight character code built from your values. It comes out the same on every reload, so it works as a before-and-after marker.
4. Go through the two tables. The first is your environment, browser and operating system down to timezone and device memory. The second covers graphics and network, where the strongest tracking signals live.
5. Change a setting and reload. Turn on a privacy extension or switch to a stricter browser, then reload: both the ID and the rating move, because hiding a signal changes what the ID is built from and drops the count the rating is made of. Changing your screen resolution moves the ID only, since the rating counts which signals are readable rather than what they say. Resizing the window moves neither, and it is worth knowing why: the fingerprint uses your screen size, not your window, so only the Viewport size row changes. That's the fastest way to prove your privacy setup does what you think.
6. Copy the full report. One click gives you all 21 rows as plain text, ready for a bug report, a support ticket, or your own notes.

I changed each row to a different value, one row at a time, and reloaded. Fourteen of the 21 changed the fingerprint ID. Only three changed the rating, and all three were cases where the value did not merely change, it disappeared: touch support fell to No, and the two graphics rows fell to Hidden.

Your ID is built out of the values themselves. The rating only counts how many signals are readable at all, so swapping New York for Tokyo gave me a brand new ID and an identical badge.

Seven rows moved neither: viewport size, cookies enabled, Do Not Track, online status, download speed, round-trip time and data saver. They are on the page because you often want them anyway, a support ticket usually asks for the viewport. None of the seven feeds your ID or your score. Take the whole connection block away, which is what a browser that reports no connection information does, and four rows drop to "Not reported" while the score does not shift by a single point.

On the invented browser I was testing with, a readable graphics card scored the full 11 of 11 and gave the ID 83947335. Mask the card so the page reads "Hidden" and the score falls to 9 and the ID becomes bc3bfabc. Turn hardware accelerated graphics off completely so the page reads "Not available" and the score is still 9, but the ID is 3b424aa4. Same score, three different IDs, and each one held steady across reloads exactly like the first.

That is what people get wrong about blockers. A blocker changes the answer your browser gives back, and the ID is built out of those answers, so you get a new ID rather than no ID. If your extension is rarer than the thing it hides, you may even have traded down.

Where blockers do pay off is the count. I took away every device detail a browser is allowed to withhold and left it with only the name it calls itself and the screen it is running on. That removes the language list, the core count, the memory figure, touch support, the connection information and the platform string in one go. The score went from 11 of 11 to 6 and the badge went from Very high to Moderate. That is a real difference and it is measurable, it is also roughly the ceiling on what browser settings alone reach here.

Four bands over eleven points, and they are not the same width. Walking the score up one point at a time, 1 to 3 reads Low, 4 to 6 Moderate, 7 and 8 High, and 9 to 11 Very high. High is only two points wide, so a single change can carry you clean through it.

The floor is 1, not 0. Your screen size and color depth are readable in every browser, so the tool counts them every time and no setup scores zero. When I stripped out everything else, browser name unreadable, timezone unavailable, graphics off, no device details at all, the badge read Low at 1 of 11. That is as quiet as this page can go.

Blocking the graphics card is worth 2 points, which sounds decisive and often is not. From 11 it takes you to 9, and 9 is still Very high, so the badge does not move at all. From 9 it takes you to 7 and the badge drops a whole band. Same change, two different stories, purely because of where you started.

The rating is an estimate from what your device shows and it is not a probability. A real "1 in 40,000" figure needs a large store of other people to measure you against, and building one means collecting everybody's fingerprint, which is the exact thing this page is warning you about. So there isn't one, and there is not going to be.

Your fingerprint ID is eight hex characters, which is 4,294,967,296 possible IDs. That sounds like plenty until you try it. I ran 4 million different screen sizes through the same fingerprint with every other value held identical, and 2,118 of them landed on an ID an earlier size already had, which works out at roughly one in every 1,900. One of the pairs is easy to check: a screen of 995 by 1929 and a screen of 1008 by 1060 both come out as cf53d2dd, and loading the page with each gave me the same eight characters twice.

So read the ID as a marker for your own machine over time, not as a name. If it changes after you install something, that install changed what your browser reports, which is genuinely useful to know. If it happens to match somebody else's, that is a coincidence with a rate you can now put a number on, and it does not mean a tracker would confuse the two of you.

People run these two together constantly. Everything on this page is what your browser exposes locally, your build, your screen, your graphics and your device settings, and all of it is read without asking any server for anything. Your IP address is the return address on every request you send, and the server at the far end sees it whether you want it to or not. This tool stays on the browser side, so it does not show your IP at all. For that you want a dedicated lookup.

They matter separately because they fail separately. A VPN hides your IP and does nothing whatsoever to your fingerprint. Going the other way, a hardened browser can flatten a good deal of the fingerprint while your IP still rides along on every single request. Close one and you are still visible through the other.

If you only want one of these values on its own, the user agent checker and the screen resolution checker each do one row properly and skip the scoring.