This is an EFF project that allows you to understand how easy it is to identify and track your browser based on how it appears to websites. Anonymous data will be collected through this site.
This is an EFF project that allows you to understand how easy it is to identify and track your browser based on how it appears to websites. Anonymous data will be collected through this site.
Here’s my result (Tested on Safari on iPad)
You should post the # of bits of identifying info it was able to derive. Best I’m able to do is 15 bits or so. Never seen it below 14, meaning you’re able to be nearly uniquely fingerprinted everywhere.
Tor browser gives 6.8 bits, with javascript disabled https://files.catbox.moe/d74wf1.png
It seems that my Safari does not have very strong tracking protection.
Nvm, I got the same result you did with Firefox and Safari, I realized I was testing on my wifi with a pihole… switched to mobile network only and protection dropped to partial.
Do you need to turn an option on or off in Safari? I got a strong protection result, same as for Firefox.While everyone’s at it, you may want to check for leaks with Mullvad VPN’s service, it picked up a DNS leak for me that got past a few other sites:
edit: also ipleak.net, which tests a few other things, like torrent ips
Huh, it says I’m leaking DNS servers and WebRTC IPs, but I don’t have secure DNS enabled, and I’m not really sure why WebRTC leaking my IP is a problem considering I’m already “leaking” my IP just by visiting a website.
In my case I had reset a device and didn’t disable IPv6. Once I fixed that the bottom two tests still say I’m “leaking”, but all three show only one IP each, for my VPN’s servers (maybe different IPs, but one for each.)
If I were actually leaking, IPs shown would be for a local DNS, or my residence, etc.