Static ISP
Recommended for this use caseOne assigned ISP address for the whole term
from$3.99/ IP / 30 days
Buy Static ISPFree tool
See whether your browser profile looks like one consistent, real device.
A browser fingerprint check reads the details any site can see (user agent, platform, Client Hints, WebGL renderer, screen, touch support, timezone, language and WebRTC) and shows which ones contradict each other or your IP. It is built for antidetect browser profiles, and the comparison runs in your browser.
Consistency
– / –
Checking…
Checking…
Checking…
Checking…
Most come from a user agent, GPU or timezone set by hand. Let the browser take them from one device template and the proxy.
Your browser details are compared in your browser and never sent to us or stored. Like any website, we see your IP's location to compare it; it is not stored.
Pricing
One assigned ISP address for the whole term
from$3.99/ IP / 30 days
Buy Static ISPA fresh IP per connection, or the same one for up to 30 minutes
from$2.99/ 1 GB
Buy Rotating ResidentialFixed datacenter IPs for a set term
from$2.99/ IP / 30 days
Buy DatacenterStripe · PayPal · Crypto (USDT / USDC) · New users get 10% off with code WELCOME10
How it works
Every site can read dozens of details from your browser without asking: the user agent, the operating system it runs on, the graphics card, the screen, touch support, timezone and language. Together they describe a device. Sites that guard logins, ads and payments do not need the exact values to be rare; they look for combinations that no real device produces.
Antidetect browsers let you set these details per profile. That is where most problems start: a Windows user agent copied onto a Mac, a timezone left on your own city, a GPU that only exists on Apple hardware. This check reads the same signals a site can read and tells you which ones disagree.
Each check compares two things a site can read that should agree on a real device.
| Check | What it compares |
|---|---|
| User agent vs platform | The operating system in the user agent with navigator.platform and, in Chromium browsers, User-Agent Client Hints. |
| Browser vs Client Hints | The browser version in the user agent with the Client Hints version. |
| Graphics (WebGL) | The WebGL renderer with the operating system: Direct3D exists only on Windows, Metal only on Apple systems. |
| Touch support | Touch points with the kind of device. |
| Screen | Checked for plausible values. |
| CPU and memory | Checked for plausible values. |
| Timezone, language and WebRTC | Your browser with the IP this page was loaded over, the same way as our IP quality check. |
The score counts checks that passed out of those that could pass or fail. Notes are shown so you can judge them, but they are not counted: many real devices have an unusual screen or no Client Hints.
Start from one device template in your antidetect browser instead of changing values one by one, and let it take the timezone, language and WebRTC address from the proxy. Our antidetect browser guides show where these settings are in each browser. Then run this check again in the same profile.
A consistent profile also needs a consistent IP. If the address changes between sessions, the location changes with it. A Static ISP proxy keeps one fixed ISP-registered IP for each profile.
FAQ
No. It means the signals this page can read agree with each other and with your IP. Sites use more than these signals, including behaviour and account history, so treat the score as a consistency check, not a guarantee.
No. The user agent, GPU, screen and other details are read and compared in your browser and never sent to us. Like any website, we see your IP and its location when the page loads; it is shown back to you and not stored. If you accepted analytics cookies, we count that the tool was used and how many mismatches it found, nothing more.
Because real devices produce it too. A software renderer, an unusual screen or a missing Client Hints header are worth a look, but they are not proof of a spoofed profile, so they do not lower the score.
Usually because of an extension that changes the user agent, or a browser setting that reports another system. Turn the extension off and run the check again. If the mismatch stays, tell us which one it is so we can review the rule.