Timezone is not UTC
A region zone that matches where the connection appears to originate — e.g. 'Europe/Berlin' behind a German exit.
What a detector infers
The check resolves the Intl zone and fails only when it is exactly 'UTC' or 'Etc/UTC'. The mechanism is population statistics, not tampering: virtually every server, container image and CI runner defaults to UTC, while consumer machines are configured to a local region during setup.
So a detector reading UTC learns something about the host class — datacenter-shaped rather than desktop-shaped — and will weigh it more heavily when the egress IP resolves to a residential region that is plainly not UTC. Because a genuine user in Iceland or the UK in winter can legitimately be at UTC, the check is 'info' severity and is not scored.
How to resolve it
Set a real-region timezone that matches your proxy exit region (geoip=True, or timezone='Europe/Berlin'). Leave it as-is if your environment genuinely sits at UTC and that agrees with your egress.
Read in the wild by
Commercial detector A
Pulls the long-form zone name out of `new Date().toString()` and tests it for exact equality with 'Coordinated Universal Time' — one arm of a bundle it evaluates only once hardwareConcurrency, platform and language already match a common automation default.
2.txt:32213-32215 — `r6["tn"] = r4; r5 = _5784["tn"]; r4 = r5 === "Coordinated Universal Time";` (literal also in the string table at 2.txt:1). `tn` is produced by `_5672` = func_01df55 (assigned 2.txt:31506, defined 2.txt:32096), which returns `new Date().toString().match(/\((.+)\)/)[1]`. Gated at 2.txt:32188-32199 on `hwc === 16` / `platform === "Win32"` / `language === "en-US"`, with `tn` initialised to null at 2.txt:32184; sibling arm compares `gpv` to the SwiftShader ANGLE renderer string at 2.txt:32221.
Every attribution traces to a published artifact. See the sources and their limits.
Nearby checks in Environment & locale
- AudioContext latencies are values Chrome's audio stack can produce
audio-latency-render-stateTwo AudioContext latencies are produced by the audio stack at particular moments, and their values are constrained in ways a constant is… - A granted geolocation fix carries a real accuracy
geolocation-has-accuracyEvery position a real location provider returns comes with an accuracy: the radius, in metres, within which the true position probably lies. - The field-trial state of this build is reported (XSLT warning banner)
xslt-banner-readoutChrome is deprecating XSLT, and a fresh Chrome 155 profile shows it: an XML document styled with XSLT is rendered with a red deprecation… - Intl timezone resolves
timezone-presentThis check reads Intl.DateTimeFormat().resolvedOptions().timeZone and records it alongside -new Date().getTimezoneOffset() and… - IANA zone offset matches the JS clock offset (incl. across DST)
timezone-offset-coherenceThis is a two-source cross-check on the same fact. It takes the resolved IANA zone, formats the current instant through Intl.DateTimeFormat… - navigator.plugins is consistent with the PDF viewer
has-pluginsAn empty navigator.plugins is only meaningful when it contradicts something else, and this check is written to respect that. - navigator.pdfViewerEnabled is true
pdf-viewerA direct read of navigator.pdfViewerEnabled. It is N/A when the property is not exposed at all, passes when true, and is marked false… - mimeTypes are consistent with navigator.plugins
plugins-mimetypesThis walks navigator.mimeTypes, and for each entry reads .enabledPlugin and checks that the exact object is present in a Set built from…
Clearcote is a browser built for fingerprint coherence
It is a Chromium fork, maintained by the same people who wrote this reference. It ships as a compiled browser rather than as a stealth script injected into someone else's — which is a description of how it is built, and is not an argument about how it behaves on this check.
This audit takes no position on how Clearcote scores on Environment & locale checks, on this one, or anywhere else. It has no baseline corpus of other people's fingerprints to rank you against and no vendor scoreboard — nearly every check is self-referential, asking one browser the same question through two independent APIs and reporting whether both answers can be true at once. It runs identically on any browser, including ours. Run it on yours and read the result yourself.
See the other checks in Environment & locale — the family timezone-not-utc belongs to.