Free tool
See what a website can read from this browser right now: your IP and where it resolves, WebRTC leaks, the canvas hash and WebGL renderer that identify your hardware, automation flags, whether your user agent and platform agree, and whether your IP location agrees with your timezone. Runs in your browser, no sign-up; the results are never uploaded to us.
Independent public audit tools that run deeper suites than this page.
Every check runs in your browser; the results are never uploaded to JustBrowser. The IP and location rows ask api.ipify.org and ipapi.co, and the WebRTC row sends a STUN request to stun.l.google.com.
A fingerprint is not one number. Detection systems compare these signals with each other, so a combination that no real device produces can get a browser flagged even when every individual value looks ordinary.
The public IP your requests arrive from, and the city, region, country and network it belongs to.
Good result: The location row is graded on whether the IP's UTC offset agrees with your browser's timezone. Compare the country with the Language row yourself. A German IP with an American timezone is the classic mismatch.
WebRTC can reveal your real IP through ICE candidates even when you are behind a proxy or VPN.
Good result: No IPs exposed. If WebRTC does reveal an address, the row compares it with the IP row: the same address is reported for information (it would bypass a proxy, so keep WebRTC off behind one); a different address is a leak.
A flag browsers raise when they are driven by automation such as Selenium or Puppeteer.
Good result: false. A true value is read as a bot by most anti-fraud scripts.
An object real Chrome exposes and many headless or stripped-down builds do not.
Good result: Present, if you are using a Chromium-based browser.
Whether native browser functions have been replaced by JavaScript, which is how extension-based spoofers work.
Good result: Functions appear native. Overridden functions and property descriptors are a detection signal in themselves.
The navigator.plugins list. Since Chrome 94, desktop Chrome reports a fixed list of five built-in PDF viewer entries whenever its PDF viewer is enabled.
Good result: Those five entries. An empty list means no PDF viewer: an old headless build, a stripped-down browser, or a policy that disables the viewer. Chrome's current headless mode reports the same five, so on its own this is a weak automation signal.
A hash of how your machine draws text and shapes. GPU, driver, fonts and anti-aliasing all shape it, so it identifies hardware quite precisely.
Good result: Stable across reloads on a real machine. If you use a multi-account browser, each profile should produce a different, stable hash.
The graphics card and driver your browser reports, for example ANGLE (Apple, Apple M2, OpenGL 4.1).
Good result: Consistent with the operating system and screen you report. A macOS user agent with an NVIDIA renderer is a contradiction.
Audio processing produces small, hardware-specific numeric differences that trackers hash.
Good result: Available. Blocked audio is itself a rare, identifying configuration.
The user agent string, and whether navigator.platform agrees with it.
Good result: They agree. Windows user agent with a MacIntel platform is one of the first things detection scripts check.
Preferred languages, the IANA timezone and UTC offset, screen size, colour depth, pixel ratio, CPU cores and memory.
Good result: All plausible together and consistent with the IP location: a 1920x1080 screen at 1x on a device claiming to be a MacBook is wrong.
The DNT header. Very few users enable it, which makes it a distinguishing signal.
Good result: Not set.
Blocking canvas or randomising values on every page load makes a browser stand out rather than blend in: a hash that changes between visits, or a canvas that will not draw, is itself a signal, because no real device does that. What passes is a fingerprint that describes a real device end to end, the same way on every visit, with per-profile noise that stays stable. WebRTC is the one place where absence is the safe result: it can expose the address behind a proxy, so the good outcome is nothing exposed, which is why this checker grades a blocked RTCPeerConnection as a pass and why JustBrowser disables WebRTC in every profile. That is why the checker above grades your user agent against navigator.platform and your IP location against your timezone, and shows the other values as plain readings for you to compare, rather than scoring how unusual any one of them is.
If you manage several accounts, the goal is one such consistent device per account, with its own proxy whose location matches the timezone and language that device reports. JustBrowser builds that identity at the C++ level of a custom Chromium engine, so the values above are produced by the browser itself rather than patched in by a script that this checker's toString test would catch.
A browser fingerprint is the set of characteristics a website can read from your browser without cookies: canvas and WebGL rendering, audio processing, installed fonts, screen size, timezone, language, hardware and dozens of navigator properties. Combined, they identify a device with high accuracy and persist after cookies are cleared.
Yes. It runs entirely in your browser, needs no sign-up, and the results are never uploaded to JustBrowser. Three rows contact third parties directly from your browser: the IP and location rows query api.ipify.org and ipapi.co, and the WebRTC row sends a STUN request to Google's public STUN server (stun.l.google.com) to see which addresses your browser reveals.
Consistency matters more than any single value. Your IP location, timezone and language should agree; your user agent, platform and WebGL renderer should describe one real device; WebRTC should not expose an address your proxy hides; and navigator.webdriver should be false with native, unmodified functions. This page grades the user agent against navigator.platform and the IP location against your timezone, and shows the rest side by side for you to compare.
This page gives a quick, plain-language read of the signals that matter most. CreepJS, BrowserLeaks, Pixelscan, IPHey and Whoer run deeper suites, and this page links to all of them so you can cross-check.
JustBrowser gives each profile its own consistent device identity and proxy, on Windows and macOS. One plan, 7-day trial.
We'd like to use Google Analytics, a Google service, to understand how our website is used. It sets two cookies in your browser and runs only if you click Accept. You can change your choice at any time with Cookie settings. Cookie Policy
Sign-in cookies and the cookie that remembers this choice are always on; the website needs them to work.
Google Analytics, a Google service, helps us understand how our website is used. It sets two cookies, _ga and _ga_TVZHQ99TZW. It is now onoff in this browser. If your browser sends a Global Privacy Control or Do Not Track signal, it stays off. Cookie Policy