Time zone and UTC offset
IANA time zone name plus UTC offset from Intl and Date.
In one line
Can tell your time zone, roughly which region you are in
IANA time zone name plus UTC offset from Intl and Date.
Narrows physical location to a region (about 400 IANA zones; America/Chicago). Mismatch with IP location is a VPN tell. 3 bits at the offset level, more with the full zone name.
What it can and can't do
What the user does: Nothing. It happens when the page or app loads
It can
- See your time zone name, such as America/Chicago, and its offset from UTC
- Show times in your local time
- Spot a VPN when the time zone and the network location disagree
It cannot
- Find your street or city; it narrows you to a region
- Find your exact position
- Show a permission pop up; there is none
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 24 | 2013-01-10 | None |
| Edge | Supported | 12 | 2015-07-29 | None |
| Firefox | Supported | 52 | 2017-03-07 | None |
| Safari | Supported | 10 | 2016-09-20 | None |
| Safari on iPhone | Supported | 10 | 2016-09-13 | None |
| Chrome on Android | Supported | 24 | Not listed | None |
| Samsung Internet | Supported | 2.0 | 2014-10-17 | None |
How a site asks for it
| API | Intl.DateTimeFormat().resolvedOptions().timeZone, new Date().getTimezoneOffset() |
| Browser compat keys | api.Intl.DateTimeFormat.resolvedOptions |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | none needed (no grant) |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: object
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
timeZone | string | IANA name | about 420 zones | exact |
getTimezoneOffset | integer | minutes | -720 to 840 | exact incl. DST history |
Technical limits
- Region only, not city precision
- VPN users show mismatch with IP
The story
What it is
The page can tell your time zone, so it knows roughly where in the world you are.
For you
Times show in your local time, like a game event starting at 8 PM for you. You do not see that the page also learned your region. No prompt appears.
For makers
Makers need your time zone to show times, schedule events and reset daily rewards. Fraud systems compare it to your IP location, since a mismatch is a classic sign of a VPN or fake location.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game resets daily rewards at midnight your time and shows events in your clock. | None named |
| live | A live stream or webinar shows 'starts at 7 PM your time' for each viewer. | YouTube Live, Zoom Webinars |
| travel | A booking site shows flight times in the right local time. | None named |
| security | A fraud engine flags a user whose time zone is New York but whose IP is in Vietnam. | None named |
| ads | An ad network schedules ads for evening hours in your region. | None named |
| analytics | A fingerprinting script adds time zone to a unique ID with language and fonts. | None named |
Risks
- Reveals your region
- Mismatch exposes VPN use
What the platform says
- Mozilla: Fingerprinting protection. Mozilla describes a Firefox option that makes browsers look alike, for example by reporting the same time zone.
Good uses and abuse
Legitimate uses
- Schedule display
- Calendars
Known abuse
- Location inference
- VPN detection
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 3 | Rough identifying entropy, when known |
A real example: LinkedIn
Collector key(s): timezone, timezoneOffset. BleepingComputer confirms timezone.
History
- 2016-06, paper: AmIUnique: timezone 3.04 bits
- 2020-01, Firefox: RFP reports UTC
- 2025-11, Firefox 145: Mozilla states timezone and language are deliberately preserved
Sources
- fingerprintjs source: timezone
- AmIUnique: Beauty and the Beast, Laperdrix et al. 2016 (attribute entropy)
- Mozilla Security Blog 2026-11-10: harder to fingerprint
- MDN resolvedOptions
- BleepingComputer: LinkedIn scans for 6,000+ Chrome extensions
- mdp/linkedin-extension-fingerprinting (LinkedIn script snapshot and ID list)
How well checked: Checked against real behavior.