Skip to content
All fingerprint checksTLS & the network layer

DNS resolver path

Check id dns-path-readout

What an ordinary browser yields

Resolver/egress context or N/A.

What a detector infers

Resolver identity requires an authoritative DNS canary; page JavaScript cannot inspect it.

How to resolve it

Operate a privacy-documented DNS canary.

Other checks in TLS & the network layer

Who builds this test

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 dns-path-readout belongs to.