The default monospace font is the claimed OS's
Under a Windows claim, Consolas measures 549.8 px for ten 'm' at 100 px and generic monospace resolves to it; Courier New and the common Linux faces measure 600.1 px. N/A under other claims, on non-Chromium engines and for Japanese, Korean, Thai and Chinese UI languages. Information only (severity: info).
What a detector infers
The generic monospace family resolves to a font the platform chooses. On Windows, Chrome's default fixed-width font is Consolas when the UI locale's fixed font is Courier-based and ClearType is on at browser startup, and Courier New otherwise; on Linux, fontconfig typically supplies Liberation Mono or DejaVu Sans Mono.
One measurement shows the difference: ten 'm' at 100 px measure 549.8 px in Consolas, against 600.1 px on genuine Linux Chrome — which kept 600.1 while claiming Windows. The row also asks for Consolas by name: it ships with every Windows since Vista and always measures 549.8 px, so a name that resolves to some other width has been mapped to a different face, as fontconfig does on Linux. The row is information only, for reasons the source makes plain.
Courier New and Liberation Mono are metric-compatible by design, so a Windows machine with ClearType off, common over Remote Desktop, measures exactly like Linux. The Japanese, Korean, Thai and Chinese UI languages have fixed fonts of their own and are N/A. And anyone can change the default font in settings. A reading that matches the claimed OS is mildly reassuring; one that does not is a prompt to look at the other font rows, not a finding.
It differs from system-font-vs-claimed-os, which reads the CSS system-font keywords the host's font APIs resolve.
How to resolve it
Nothing to fix from this row alone: ClearType, the UI locale and user preference all move it legitimately. If it disagrees with the claimed OS together with the other font rows, the font stack belongs to a different system from the one claimed.
Nearby checks in Network & WebRTC
- A server-reflexive candidate only appears when a STUN server answered
srflx-only-from-answering-stunA server-reflexive (srflx) ICE candidate is the public address a STUN server reports back in its reply to a binding request. - Every server-reflexive address is one the STUN server actually handed out
srflx-was-seen-by-stunA server-reflexive candidate exists only after a STUN server received a binding request from that public address and replied with it. - Emoji come from the claimed OS's emoji font
emoji-font-vs-osEmoji are drawn from the operating system's colour emoji font, and the fonts differ in a way measureText can see without rendering a pixel. - Canvas text is anti-aliased the way the claimed OS rasterises it
glyph-aa-levels-vs-osCanvas text is rasterised by the platform's font engine, and the engines leave different fingerprints in the alpha channel. - The JS heap ceiling fits the memory the browser reports
heap-ceiling-vs-device-memorynavigator.deviceMemory and V8's heap ceiling, performance.memory.jsHeapSizeLimit, look unrelated but are computed from the same number: the… - The address WebRTC exits from matches the address this page was served to
webrtc-ip-vs-connectionThis is the one check on this page that cannot be answered from inside the page, and the only one that makes a network call. - Relay-forced WebRTC exits the same address this page arrived from
webrtc-turn-egressEvery other WebRTC check on this page reads what the browser is willing to show it. - Host candidates use an mDNS hostname rather than a literal LAN address
webrtc-mdns-hostWhen WebRTC enumerates the ways a peer might reach you, it offers host candidates describing your machine's own network interfaces.
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 Network & WebRTC 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 Network & WebRTC — the family monospace-default-vs-os belongs to.