HTTP/2 settings and order
Probe evidence or N/A.
What a detector infers
HTTP/2 SETTINGS and pseudo-header order are emitted below JavaScript.
How to resolve it
Add HTTP/2 capture to the transport probe.
Other checks in TLS & the network layer
- the TLS fingerprint is the same on two separate connections
ja4-stable-across-connectionsEverything else on this page reads the browser through JavaScript. - the ClientHello extension order is shuffled per connection, as Chrome does
tls-clienthello-order-variesJA4 and JA3 disagree about ordering on purpose, and that disagreement is the assertion. - the TLS fingerprint this browser presents to a server
tls-fingerprint-readoutThis row reports rather than judges, and the reason it exists is that it is the only place on this page where the browser is described by… - TLS cipher list matches the claimed engine
tls-cipher-suite-vs-engineYour browser announces which engine it is twice, through channels that cannot reach each other. navigator.userAgent is a string any page can… - TLS identity matches the browser
tls-browser-identityJA4 repeatability proves stability, not that the profile matches the claimed browser. - HTTP/3 / QUIC transport
http3-quic-readoutQUIC versions and transport parameters form an independent fingerprint. - IP network classification
network-reputation-readoutASN, network class, and proxy/VPN/Tor indicators describe the route, not the browser, and are never standalone verdicts. - DNS resolver path
dns-path-readoutResolver identity requires an authoritative DNS canary; page JavaScript cannot inspect it.
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 TLS & the network layer 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 TLS & the network layer — the family http2-fingerprint-readout belongs to.