It’s worth checking a fingerprint twice: right after creating a profile or changing its proxy, and then on detectors from time to time. The easiest place to start is the profile start page — it opens as the first tab on every launch.
The profile start page
It shows everything a site learns about the profile before the first click:
- exit IP, geo, provider and proxy ping;
- time zone and language matching the IP;
- WebRTC and geolocation — with no leak of your real address;
- the profile OS matching the computer’s OS.
If every check is green, the profile is consistent with its proxy. A red check is almost always about the proxy or about launching on a different OS, not about the fingerprint itself.
Which detectors to open
Links to the checkers are right on the start page: BrowserScan, Pixelscan, BrowserLeaks, CreepJS, Fingerprint.com and IP2Location. Open them inside the profile — it’s the profile you need to test, not your regular browser.
What to look at
- Consistency: User-Agent, platform, screen, GPU and fonts shouldn’t contradict each other.
- Geo: time zone, language and geolocation match the IP’s country.
- WebRTC: the proxy’s address shows, not your real one.
- OS: the detector sees the same system as the fingerprint claims.
What’s fine
A unique fingerprint is normal: every real device has a unique one too. A “data center IP” rating is about the proxy type, not the browser — if it gets in the way of your task, change the proxy. And differences between two profiles on the same computer are expected: each profile has its own fingerprint.
How we test ourselves
Every engine version goes through a detector run before it ships: Fingerprint.com, Pixelscan, CreepJS, rebrowser-bot-detector, BotD and deviceandbrowserinfo — on macOS and Windows, on the host OS, with and without a proxy.