Check the timezone your browser reports
See your browser's IANA timezone, current UTC offset and locale. These values come from device settings and can differ from an IP-based location for perfectly ordinary reasons.
Your browser timezone
Computed for this visitRunning the test locally in your browser…
How this signal works
Websites can read the timezone configured by your operating system without asking for location permission. The named timezone and current offset help format dates correctly, and they also contribute a small amount of information to a browser fingerprint.
Risk systems sometimes compare the browser timezone with the approximate timezone inferred from an IP address. A mismatch may be caused by travel, a VPN, corporate routing, mobile-carrier gateways, a device set manually to another region or a geolocation database error. It is context, not proof of deception.
What this result cannot tell you
- UTC offsets change with daylight-saving rules while the named timezone normally remains stable.
- Users can select any timezone in their device settings, and privacy tools may standardize it.
- IP geolocation is approximate, so a timezone mismatch should never trigger a hard decision by itself.
Use browser and network signals in your app
The verification API collects the broader fingerprint, binds it to the network request and returns the result to your backend.