• 1 Post
  • 3 Comments
Joined 9d ago
cake
Cake day: Nov 08, 2026

help-circle
rss

Partly, yes. Sites can usually tell RFP is on, so you’re in a smaller group than “all Firefox users”. But inside that group everyone reports the same canvas noise, timezone, screen buckets and so on, so it’s hard to tell one RFP user from another. That’s the same idea Tor Browser and Mullvad Browser use, and it’s usually better than a real, unique fingerprint.

Also, the site doesn’t see your local network. It sees your public IP, which everyone behind your router shares anyway. Being the only Linux user at home doesn’t stand out to a site, being a rare combo among everyone who visits it might.


Thanks! UTC by choice is a good one, the page can’t tell that apart from RFP, so that note is only a guess.

The device tier is rough. It’s based on what the browser reports, like CPU core count and the memory value, which Chromium caps, so plenty of decent machines land in entry-level. Fair feedback, noted.


Not much on its own. A timezone or language that doesn’t match the exit IP mostly tells a site you’re on a VPN, which you’re fine with. It only starts to narrow you down when the combination is rare, for example an uncommon language plus a timezone few people on that exit server use, or when WebRTC leaks your real IP.

What actually lets a site recognize you again is the stuff that stays the same when your IP changes: cookies and logins first, then canvas, WebGL, fonts, screen size and similar. So if you only care about recognition, that part of the report matters more than the VPN mismatch part.


I'm the author, so treat this as self-promotion. It's free, MIT-licensed, and AI helped me write a lot of the code. **What it is:** [Who Are You](https://who.1ms.dog/) runs the checks any ordinary website can run without a permission prompt and then writes out, in plain sentences, who the site would think you are: rough location from the exit IP, time zone and languages, OS and screen, fonts, canvas/WebGL/audio fingerprint, WebRTC, client hints, DNT/GPC. **Why I built it:** most fingerprint test pages give you a uniqueness score. What I kept wanting to know was *what contradicts what*. The page flags the mismatches that usually give a VPN or proxy away: - system time zone or browser language doesn't match the exit IP country - WebRTC shows a different IP than the one the site sees - a split-tunnel setup where some requests leave through a different exit - the TCP/TLS fingerprint belongs to a different OS than the user agent claims (a user-agent switcher can't fix that one) Each finding has a short "how to fix / or leave it if you're not trying to look local" note. **Data, since this is c/privacy:** the checks run in your browser. To say how many visitors share a value, the site keeps anonymous per-value counts, with no IP, no full fingerprint and no record of single visits. "Don't count me" or a GPC signal turns the counting off. If that's still too much, the source is here and you can host it yourself: https://github.com/yt1988/who-are-you I'd especially like to hear from Tor Browser, Mullvad Browser and LibreWolf users: what does it get wrong about you, and which check is missing?
fedilink