Skip to main content

Your browser carries a regional accent.

A website can read your timezone, language order, calendar, numbering system, hour cycle, and formatting rules without asking permission. When those values disagree with a VPN exit or IP region, the contradiction becomes a signal inside alarger browser profile.

Permission
None
Primary APIs
Intl · Date · Navigator
Can narrow region
Yes
Precise location
No
one request · two regional storiesconsistency check
Illustrative mismatch. A timezone can suggest a probable region or retained home configuration, but it does not prove an exact physical location.

See what your browser makes visible.

This demonstration reads the actual regional surface exposed to page JavaScript. It does not request geolocation, look up your IP, transmit the values, or store the result. Choose a hypothetical VPN exit to see how an observer could compare the two contexts.

Browser-side inspectionReady to inspect locally
Your browser contextlive values
IANA timezone
Waiting to inspect
Current offset
—
Primary locale
—
Language order
—
Calendar
—
Numbering
—
Hour cycle
—
Date sample
—
Number sample
—
Currency sample
—
Compare a network locationyou choose the exit
browser time—:—browser zone
exit time—:—selected zone
No network context selectedInspect first, then choose an exit.

The page will compare the selected region with the timezone your browser reports.

The comparison is educational and remains local. Real services may infer network region from an IP address and combine it with many more signals.

Timezone and locale describe different parts of the story.

Timezone describes how the clock relates to UTC. Locale describes language and formatting preferences. They often correlate with geography, but neither is a GPS coordinate.

01America/Denver

Timezone

An IANA zone can describe a region and its daylight-saving rules, not merely one current UTC offset.

02UTC−06:00

Offset

The current difference from UTC changes seasonally in many zones and is shared by many places.

03en-US · es · en

Language order

Navigator exposes an ordered preference list; requests often carry a related Accept-Language header.

049/20/26 · 2:42 PM

Formatting

Date order, separators, month names, and 12- or 24-hour time reveal locale conventions.

05gregory · latn · h12

Intl defaults

Calendar, numbering system, and hour cycle add structured detail to the regional profile.

timezone+offset rules+languages+formatting+network region→ regional consistency profile

Formatting behavior turns preferences into observable text.

A script does not have to trust one locale string. It can ask the browser to format dates, times, numbers, currencies, lists, and names, then compare the output with the claimed locale.

same instant2026-09-20T20:42:00Z
en-US · Denver9/20/26, 2:42 PM1,234.56
en-GB · London20/09/2026, 21:421,234.56
de-DE · Berlin20.09.26, 22:421.234,56
ja-JP · Tokyo2026/09/21 5:421,234.56
Examples are illustrative for one instant. Exact output depends on browser locale data and requested formatting options.

A VPN can hide the route while the browser keeps its home context.

A routed VPN changes the public IP and apparent network region. It does not automatically change the operating system’s timezone or the browser’s language preferences. The pair can narrow a likely real region, reveal a retained home configuration, or simply show that the profile is inconsistent.

device settingsAmerica/Denveren-US · h12 · gregory
public networkAmsterdam exitIP region: Netherlands
site receives both contexts
request metadataNL network
page JavaScriptDenver timezone

distinctive combination: Dutch exit + Mountain Time browser

What this can and cannot establish

The mismatch can expose a probable origin region or prior device configuration behind a VPN. It does not prove where a person is physically located, why the mismatch exists, or whether the user is acting maliciously. Travel, remote desktops, corporate systems, and deliberate privacy protections can produce the same pattern.

Daylight-saving rules make the identifier richer.

Many places share the same UTC offset today. An IANA timezone also carries a rule set: when clocks change, whether they change at all, and what the offset will be on another date. A collector can format winter and summer dates to distinguish zones that currently look alike.

zone probeformat two fixed dates
America/DenverJanuary · UTC−07July · UTC−06changes
America/PhoenixJanuary · UTC−07July · UTC−07fixed
Atlantic/ReykjavikJanuary · UTC±00July · UTC±00fixed
Two zones can match today and diverge later. The named timezone exposes the rule set directly in many browsers.

Ordinary values become stronger when they validate each other.

A timezone is shared by millions of people. So is a language. Fingerprinting systems gain confidence by comparing the relationships between them and the rest of the request.

JavaScriptAmerica/Denver · en-US · h12
HTTPAccept-Language: en-US,en;q=.9
NetworkVPN exit: Amsterdam, NL
Accountregional history or saved preference

profile assessmentmostly stable browser context · changed network context

Changing the network does not rewrite the browser’s regional settings.

ActionLikely resultWhy
Clear cookiesUsually unchanged

The values are reconstructed from browser and operating-system preferences.

Open a private windowUsually unchanged

Private mode isolates storage but normally inherits the same regional configuration.

Connect to a VPNBrowser values stay; network region changes

That disagreement is often more informative than either signal alone.

Travel without changing settingsCan create a mismatch

The IP region moves while the device may retain its home timezone and language order.

Change OS or browser preferencesCan change several fields

Timezone, preferred languages, calendar, numbering, and hour cycle may inherit different defaults.

Use broad anti-fingerprinting protectionMay standardize the story

Shared timezone and locale answers can place many users in the same regional profile.

A coherent shared profile is safer than random regional noise.

Changing only one value can create an unusual contradiction. Strong anti-fingerprinting designs coordinate timezone, locale, language headers, and formatting behavior so many users return the same internally consistent answers.

01

Standardize

Shared timezone and locale defaults reduce the number of distinct regional profiles.

02

Keep layers aligned

Navigator languages, Intl output, Accept-Language, and network claims should not contradict one another accidentally.

03

Avoid one-off spoofing

A rare or inconsistent combination may be easier to recognize than the real values it replaced.