Timezone mismatch
A timezone mismatch is when your browser's clock zone differs from the zone of your IP's location, a common sign of a proxy or VPN.
What a timezone mismatch is
Your browser knows the time zone of the operating system and reveals it to any page through JavaScript, for example as Asia/Ho_Chi_Minh or as an offset of minutes from UTC. Separately, the website can geolocate your IP address to a country, and every country has a known set of time zones. A timezone mismatch is the case where the two disagree: the IP says Germany, the browser says it is set to Vietnamese time.
A person sitting in Germany on a German connection almost always has a computer set to Central European Time. The mismatch does not prove anything by itself, but it is cheap to detect and correlates strongly with proxies, VPNs, and remote profiles.
Why it matters
Fraud and account-security systems treat the time zone as a consistency check on the IP, not as an identifier. The combination of a proxy address and a home time zone is exactly what an inexperienced proxy user produces, so it is weighted accordingly. Our anonymity score deducts 10 points when the browser's zone is neither the zone our geolocation data assigns to your IP nor any zone used in that country. The rule is lenient on purpose: a zone that is valid anywhere in the IP's country passes, since city-level geolocation is not reliable enough to demand an exact match.
How to check
The anonymity score page reads your browser's time zone and compares it with the IP's location, showing both values and the verdict. The browser fingerprint page lists the zone among the other signals, and the IP checker shows the time zone our data assigns to the address so you know what to set.
How to fix it
Set the operating system clock zone to match the proxy's country, or use the time zone override that antidetect browsers provide per profile; the better ones derive it from the proxy automatically. After changing it, reload the test. Also check that the browser's language settings tell the same story, since a language mismatch is the usual companion of a timezone mismatch.
Common misconceptions
The time zone is not read from the clock's displayed time but from the zone setting, so simply changing the hour does nothing. And matching the zone is not the same as matching daylight saving rules: a manual UTC offset that ignores DST will drift out of agreement twice a year.