3 ms·
With NoScript, it does not provide a tracking ID. Which shows yet another reason to browse with NoScript.
by pwg 15y ago
With NoScript, it does not provide a tracking ID. Which shows yet another reason to browse with NoScript.
- brudgers 15y ago*The following is your unique fingerprint on the web:* *loading...* I'll bet my fingerprint isn't unique.
- franciscoapinto 15y agohttps://panopticlick.eff.org/ https://panopticlick.eff.org/ You'd be surprised.
- nmcfarl 15y agoOk that’s a scary page.
- brudgers 15y agoNot really. Currently, we estimate that your browser has a fingerprint that conveys 11.9 bits of identifying information.
- Wilya 15y agoThat's a very low value. With JS off or blocked, my browsers convey between 16 and 21 bits (the latter meaning unicity in their dataset). The amount of information conveyed by the HTTP_ACCEPT headers is especially preoccupying. There is nothing in there, apart from maybe the language, that should leak any info, on a modern browser. And certainly not 10 or 16 bits of info.
- flink 15y ago"Your browser fingerprint appears to be unique among the 2,155,876 tested so far." Huh, that's awesome ... in a bad way. According to that page , both my system fonts and browser plugin details are unique among the browsers they've tested thus far.
- marco_polo 15y agoNot necessarily, they fingerprint you using the info the browser gives to them. This site for example uses JS to do the fingerprinting, but it could be just as easily (perhaps less scalable) to do the fingerprinting serverside. TL;DR serverside code can fingerprint you
- Sivart13 15y agoIndeed. Similarly, if you barricade yourself inside your house you'll be well-protected against thieves.