Consistency Check - Locale and Geo Alignment

doc

Compare browser language, timezone, and geolocation signals to detect mismatches and reduce risk flags.

Consistency checks exist because every single signal can be wrong in isolation and right in aggregate. A timezone does not prove a location. A language header does not prove a country. But when four or five independent signals point at different places, the disagreement is the finding — and it is usually caused by a configuration, not by an attack.

What gets compared

SignalSourceTypical false disagreement
Exit address and countryRegistry and ASN lookup of the observed addressTunnel, CGNAT, corporate egress
TimezoneBrowser-reported offsetManually set, or not updated after travel
Language headerAccept-LanguageSet once and never changed
System localeOS-level formatting and regionDifferent from the UI language by design
User agentBrowser stringGeneric, or spoofed by an extension

The useful question is not "do these match" but "which of these could plausibly differ while the user is telling the truth". Most mismatches fall into that bucket.

Four kinds of mismatch

  1. Legitimate divergence. A user in one country connecting through a work VPN in another. The address and the timezone disagree, and both are accurate. This is the most common case and it is not a problem.
  2. Stale configuration. The timezone was set years ago and survived three moves. The address is current; the offset is not. A real inconsistency, but harmless.
  3. Deliberate divergence. Language set to a foreign locale to get a specific content version, or a browser configured to look like another region. The user caused it knowingly.
  4. Signals that should never disagree. A timezone offset that no country in the reported region uses, or a locale that does not exist. These are worth looking at, because they suggest a misconfiguration deeper than a preference.

Only the fourth kind justifies treating the result as a red flag, and even then the conclusion is about configuration, not intent.

Why the check reports rather than judges

A consistency checker cannot know why the values differ. A tool that labels any mismatch as suspicious will flag every remote worker, every traveller, and every user who set their system language to English while living elsewhere. That population is large enough that the label becomes noise. What the check can do is present the values side by side, mark which ones are implausible, and leave the interpretation open.

Where judgement does enter:

  • Geographic impossibility. An offset that the reported country does not observe, or a country that the ASN does not belong to.
  • Internal contradiction. Two headers that cannot both be true of the same device — for example a user agent claiming a platform that the client-side probe contradicts.
  • Repeated oscillation within a session. Values that change between requests without a corresponding network change suggest a proxy rotating exits, not a user changing settings.

Reading the result in practice

  1. Start with the address. Confirm what the site actually sees, not what the machine reports locally.
  2. Compare the timezone to the address. A mismatch is the most common signal and the least alarming.
  3. Check the language independently. Accept-Language and system locale are separate fields and often disagree legitimately.
  4. Ask what changed recently. A new tunnel, a new laptop, or a fresh install explains most mismatches.
  5. Look for impossibility, not difference. Difference is normal. Impossibility is the signal.

Common misreads

  • "My timezone does not match my IP, so I am being watched." It means the two were set at different times. Nothing more.
  • "Everything matches, so I am consistent." Consistency is not anonymity. A coherent profile is easier to link, not harder.
  • "A mismatch means a VPN." It may mean a VPN, a corporate network, an old setting, or a browser extension. Four causes, one symptom.
  • "Fixing the timezone will make me consistent." It removes one mismatch and may create another if the address is the thing that is "wrong" for your actual location.

FAQ

Is a consistent profile better for privacy?

No. Consistency makes a profile coherent, which makes it easier to link across sessions. Anonymity and consistency are different goals.

How many signals need to disagree before it matters?

It is not a count. One impossible value matters more than four plausible ones that happen to differ.

Should I set my timezone to match my VPN?

Only if you want the profile to look locally coherent. It does not improve privacy, and it makes the settings less useful to you.

Does the check see my real location?

No. It sees the exit address of the request. If a tunnel is in use, that is the address it reports.