The test on this page leverages browser fingerprinting to generate a fingerprint of your browser. This fingerprint is then used to calculate in a bot detection test to compute a bot risk score. A score above 50 means that you are most likely a bot. You can learn more about the bot risk score and browser fingerprinting below.
Browser fingerprinting is a technique used to identify and track users by analyzing their browser and device characteristics. It involves collecting data from the browser, such as the user agent string, GPU, timezone, and system information, to create a unique fingerprint of the user's browser.
No, browser fingerprinting is not 100% unique. While some users with uncommon devices or configurations may have unique fingerprints, most users will have similar fingerprints. For example, iPhones and iPads will have similar fingerprints because the underlying hardware is the same.
Yes, you can change your browser fingerprint by changing attributes that are part of the fingerprint. For example, you can change the user agent string, timezone, languages, and the canvas fingerprint. While some attributes are more difficult to change and require dedicated browser extensions, it is possible to change most attributes since they are collected in the browser.
The fingerprint ID is an identifier linked to your browser fingerprint. It is a hash of the browser fingerprint data. Not all attributes are hashed as is. For certain attributes, we apply preprocessing to obtain a more stable fingerprint.
The bot risk score is a score between 0 and 100 that indicates the risk of a user being a bot. The higher the score, the more likely the user is a bot. It is calculated based on:
No, browser fingerprinting is also used to enhance security, in particular to detect bots. For example, it can be used by your bank to verify if the login attempt comes from the same browser and device as the one used in the previous login. Thus, this adds an extra layer of security to your account in addition to the password.
Yes, fingerprinting lies can be detected. For example, if you change your user agent to Firefox but still uses a Chrome browser, scripts can detect inconsistencies in the fingerprint and flag the fingerprint as suspicious.