Correction to my post: I wrote that the page itself isn’t open source. That was wrong. The source is public under MIT at https://github.com/yt1988/who-are-you, so you can check what it collects instead of taking my word for it. Sorry for the mix-up.

Yep, webkay and pages like it are where the idea comes from, nothing new about the basic checks. What I tried to add is the comparison part: does your timezone and language match your exit IP, does traffic leave through a different exit when a proxy splits it, and which of your values are rare. If the older pages already cover what you need, no reason to switch.

Honestly, not at this speed. I can read and fix the code, and I decide what the page checks and how it handles data, but a lot of it was written with an AI assistant. That’s why I said so in the post. If that’s a dealbreaker for you, I get it.

Thanks! If you want quick wins: the biggest signals are usually WebRTC leaking a local or real IP behind a VPN, a timezone or language that doesn’t match your exit IP, and a very unique canvas/font fingerprint. Firefox with resistFingerprinting, or the Tor/Mullvad Browser, cuts most of that down.

Fair point, and that’s why the post says AI helped. I used it for a lot of the code and the English text. What the page checks, and how it handles data (checks run in the browser, no IP or full fingerprint kept, only anonymous per-value counters that ‘Don’t count me’ or GPC turns off), was my call, and so is any bug you find in it.