System Profile Check

doc

Analyze memory class, storage estimate behavior, CPU hints, and platform metadata to diagnose stability and fingerprint risk.

System information sits between the network and the browser. It is what the operating system tells the browser, what the browser is willing to repeat, and what code in a page can infer from the gaps. Unlike an IP address, it does not change when you move. Unlike a cookie, it is not something you can delete.

What "system" covers here

LayerTypical valuesSource
Operating systemWindows, macOS, Linux, Android, iOSClient Hints, or inferred from the user agent
VersionMajor platform version, when disclosedClient Hints only, and only if the site asks
Architecturex86, arm64Client Hints, occasionally
Locale and regionLanguage tag, formatting regionHeaders plus client-side probe
TimezoneIANA name and UTC offsetClient-side probe
Device classDesktop, tablet, mobileInferred from input and viewport, not declared

Two of these are reliable — locale and timezone, because the client reports them for functional reasons. The rest are either opt-in or inferred, which means they can be wrong in ways that look authoritative.

Why the OS claim is weaker than it looks

Before Client Hints, the OS was derived from a frozen user agent string, and the derivation was approximate at best. After Client Hints, the OS is available only if the site requests it with Accept-CH and the browser agrees to send it. A site that never asks gets a reduced string and no platform detail, and any "detected OS" it displays is an inference.

This produces a familiar inconsistency: a check page says "Windows" while the user is on a Mac, because the reduced user agent is ambiguous and the parser guessed. The correct reading is not "detection failed" but "the signal was never there".

Locale and timezone: the reliable pair

These are reported because applications need them, not because they are useful for identification:

  • Language tag follows the user's UI preference. It is frequently not the language of the country the user is in, and it is almost never a reliable indicator of nationality.
  • Timezone follows the OS setting. It survives travel if the user does not update it, and it changes automatically on some platforms.
  • Region formatting is separate from both. Date order and currency display can follow a region that neither the language nor the timezone implies.

When these three disagree with each other and with the exit address, the disagreement is informative. When they agree, it proves coherent configuration, not a location.

Device class is inferred, never declared

No API says "this is a tablet". What exists is a set of proxies:

  1. Viewport size and pixel ratio. A large viewport with a high ratio suggests a high-density display, which correlates with laptops and phones differently.
  2. Input capability. Touch points and pointer type. A device with both is convertible.
  3. User agent hints, when present. Mobile versus desktop form factor, if the site asked.
  4. Behavioural signals. Scroll patterns and typing rhythm, which are outside the scope of a static check.

Every proxy has counterexamples. A tablet in desktop mode reports a desktop viewport. A touchscreen laptop reports touch. Classification is a guess with a good prior, nothing more.

Practical reading

  • Trust locale and timezone as configuration. They say what the user set, not where the user is.
  • Treat OS and version as opt-in. If the page did not request hints, the value is inferred and may be wrong.
  • <>Do not equate device class with hardware. It is a heuristic from input and viewport.
  • Compare against the exit address only for plausibility. A timezone that no country in the reported region uses is worth a second look; an ordinary mismatch is not.

Common misreads

  • "It says macOS but I am on Windows." Inference from a reduced user agent, not detection. The page never had the real value.
  • "My language is English, so I must be in an English-speaking country." UI language and physical location are unrelated settings.
  • "The timezone is wrong, so my IP is leaking." Timezone is a local setting. It says nothing about the network path.
  • "It detected a tablet." It inferred one from viewport and input. Inference is not detection.

FAQ

Does system information reveal my identity?

It reveals a configuration: OS family, locale, timezone and device class. Those narrow a population; they do not name a person.

Why is my OS reported incorrectly?

Because it was inferred from a reduced user agent. Accurate platform data requires Client Hints, which the site must request.

Can I hide my timezone?

You can change it, which changes the report. It is not hidden, only replaced by a different setting.

Is device class reliable?

No. It is derived from viewport and input, and laptops, tablets and desktop modes routinely cross the lines.