In this article, we also try to help you get 100% anonymity but NOTE that Whoer.net’s anonymity indicator is not fully reliable. You can still have perfect protection if you don’t see 100% anonymity on whoer.net. It checks a couple of rules about your browser fingerprint and it scores your anonymity. It doesn’t mean that sites with browser fingerprint-based machine learning algorithms will score your browser fingerprint with the same score. We could make a profile that has a 20% fraud score on ipqualityscore.com but on whoer.net it says 64% anonymity.
So if you will be only calm if you see the ‘100% anonymity’ on whoer.net continue reading.
Why I’m not getting 100% anonymity?
Once you open whoer.net and you see something below 100% you can check what is the problem.
Simply click on 'More' and whoer.net will tell you the problems about your browser fingerprint.
There you will find a list of settings you should improve. As you can see in the above image the anonymity percent calculator is wrong.
Common problems with the browser fingerprint
So here are the key points that you should focus on while trying to get 100% anonymity.
- The system timezone is the one you set up on Kameleo Profile settings.
- The local timezone is based on your IP’s location. (If you are using a proxy, the proxy’s location will count)
The 2 value should be the same. So adjust the timezone to your IP’s location.
Read more about timezone.
Your DNS server’s country should match your IP’s country. If you are using a proxy this can happen when you are not telling Kameleo to handle the DNS resolution by the proxy.
Read more about DNS resolution and DNS leaks.
A commonly asked question. It says:
The language set in your system and/or browser differs from the language your IP address county. You are possibly trying to hide yourself by anonymity means.
Another example: A computer user’s system language is French and he has an English keyboard. While he is traveling in Germany. This way the language based on his IP will be totally different from the language based on the system. But it is normal, it is not a problem, browser fingerprint-based machine learning algorithms shouldn’t warn.
So as you can see that the above configuration is totally valid. These configuration is coming from the Base Profile. So no worry. If you still looking for a 100% anonymity, search for a base profile that’s headers and system language configuration will match your IP’s location.
Read more about this issue in the Language different article.
It happens when your WebRTC public IP is not matching your IP. Set up Kameleo for automatic WebRTC spoofing.
Read more about WebRTC.
You have a browser tracking block disabled.
Don't worry. This is normal. This value is coming from the Base Profile.
Check this video that shows you a couple of tricks on how to get 100% anonymity