This browser fingerprint test looks for contradictions. A real browser on a real device tells a coherent story: its clock is in the same time zone as its internet connection, its languages fit the place it connects from, and every source of information names the same operating system. When those details disagree, websites notice, and so do fingerprint testers. The checks above show where your browser agrees with itself and where it doesn't.
How the test works
Everything runs in your browser. The page makes one request to our server, which returns the IP address it sees and the location Cloudflare associates with that address: country, city, region, time zone and network. Our server reads this from the request and stores nothing. The WebRTC check also contacts a public STUN server run by Cloudflare (stun.cloudflare.com), which is how any WebRTC page learns your public address.
Each row gets a colored dot:
- Green: the values agree, or there is nothing to compare.
- Yellow: worth a look. Often harmless, but it stands out.
- Red: a clear contradiction that tests and anti-fraud systems commonly flag.
The label at the top sums it up: Consistent when every row is green, Worth a look when at least one is yellow, and Inconsistent when any row is red.
What each check means
Time zone vs IP location
Your browser reports its time zone through Intl.DateTimeFormat().resolvedOptions().timeZone. We compare it with the time zone of your IP address. The same zone name is green. A different name with the same current offset from UTC, such as Europe/Berlin and Europe/Paris, is yellow and is usually fine. A different offset is red: your clock says you are somewhere other than your connection.
This is the most common problem with proxies and VPNs. The connection moves to another country, but the computer's clock stays at home.
Languages vs IP country
We read your browser's language list (navigator.languages) and check whether any of them is usual for your IP's country. For a German IP, de-DE or de matches. For a US IP, English or Spanish matches. No match is yellow, not red: travelers, expats and international teams have this all the time. It still makes the browser stand out. For countries outside our language table, the row shows your languages without comparing them.
Interface language vs first language
The browser formats dates and numbers in its interface language, which you can read through Intl.DateTimeFormat().resolvedOptions().locale. The first entry in navigator.languages is the language it asks websites for. In an unmodified browser these normally share the same base language. When they differ, for example an English interface with German as the first requested language, fingerprint tests often report it as a sign that the language was changed on purpose. This row is red when the base languages differ.
WebRTC IP vs connection IP
The page opens a WebRTC connection attempt, which makes the browser ask a STUN server for its public address. If that address differs from the IP the website sees, WebRTC is going around your proxy or VPN and revealing another address. That is red. If WebRTC shows a raw local network address such as 192.168.1.20 instead of a random .local name, the row is yellow. If WebRTC is turned off, nothing can leak through it, and the row is green. Run the WebRTC leak test for the full list of addresses.
User agent vs client hints
Chromium-based browsers describe themselves in two places: the user agent string and User-Agent Client Hints. We compare the operating system each one names. Windows in one and macOS in the other is red. It usually means the user agent was changed by an extension, a developer setting or a tool that didn't update the client hints. Safari and Firefox don't support client hints, so in those browsers the row just shows the operating system. The user agent checker shows both sources in full.
Automation flag
navigator.webdriver is true when the browser is controlled by automation, for example when Chrome starts with the --enable-automation or --headless flag (MDN). It exists so automated sessions can identify themselves, and websites use it to treat automated traffic differently. A red result when you aren't running automation means something launched your browser with an automation flag. If you do run automation, follow each site's rules on automated access.
Screen
This row shows the screen size, the size of the browser window's viewport and the pixel ratio. It is red if the window is wider than the screen it reports, which can't happen on a real device and usually means the screen size was changed without changing the window.
Hardware
This row shows the number of logical CPU threads (navigator.hardwareConcurrency) and the memory class (navigator.deviceMemory). Browsers round and cap the memory value on purpose to limit fingerprinting, and Safari and Firefox don't report it, which shows here as "memory hidden". This row is informational.
IP address
This is the address websites see, with the city and country Cloudflare associates with it. If you use a proxy, this should be the proxy's address. Our proxy checker shows more detail, including the network that owns the address.
How to fix common problems
- Time zone is red. Set your browser or system time zone to match the IP's location, or use a browser profile whose time zone follows its proxy.
- Languages are yellow. If the profile should look local, add the local language to the browser's language list. If you are simply abroad, you can leave it.
- Interface language is red. Make the first language in the list match the browser's interface language, or change the interface language to match.
- WebRTC is red. Change the browser's WebRTC handling so it can't use connections outside the proxy, or turn WebRTC off if you don't need calls in that browser.
- User agent is red. Remove user agent switcher extensions and turn off device emulation in developer tools. Let the browser report its own user agent.
- Screen is red. Undo any screen size override, or make sure the window fits inside the reported screen.
Limits of this test
- Location databases disagree. We use Cloudflare's data. Your proxy provider, and the services an antidetect browser uses to look up the proxy's location, may place the same IP in a neighboring city or time zone. A mismatch can come from the databases rather than from your browser.
- IPv4 and IPv6. If your connection reaches our site over IPv6 but WebRTC reports an IPv4 address, or the other way round, the WebRTC row can show two different addresses that both belong to you. Check whether the WebRTC address belongs to your own network before treating it as a leak.
- Not every signal is here. This page doesn't test canvas, WebGL, audio or fonts. Use the canvas fingerprint test for canvas and text measuring.
- A green result is not a verdict from any website. Sites weigh many signals, including behavior and account history, that no browser test can see.
How Multime handles these checks
Multime is a browser-profile manager for Mac and Windows in which each profile is its own Chromium-based browser. The checks on this page map directly to profile settings:
- Time zone, language and geolocation match the proxy's IP by default, or you set them by hand. Multime checks the IP through the proxy when the profile opens.
- Interface language is kept consistent with the page language list, so the formatting locale and the first language agree.
- WebRTC can be set to go through the proxy, replace the IP, be disabled, or stay real.
- User agent is set automatically to match the engine, with the operating system and browser brand you choose.
Screen size in a Multime profile is always your real screen, so the screen row reflects your actual display. In our own test on 22 October 2026 on macOS with the Chrome 152 engine, Pixelscan reported a Multime profile as consistent, with "No masking detected" and "No automated behavior detected". That is one tool on one date. The best check is your own: open this page inside a profile after you set its proxy.