Skip to content

Diagnostics

Two checks you can run against this browser, right now.

Both run in the page and report what they measured, including what they could not measure and why. Nothing is stored and neither needs an account. Run them in the browser you actually work in, then decide whether the result is the one you wanted.

Executes
In this browser
Sent to us
The request itself
Stored
Nothing
Sign-in
Not required

01Checks

What they do

One measures entropy. One measures agreement.

The first tells you how identifiable this browser is. The second tells you whether it contradicts the address it is connecting from, which is the cheaper detection and the one that catches an unconfigured proxy on its own.
  • 01

    Fingerprint check

    Eight browser-level collectors, each hashed on its own and then folded into one composite value. Every signal is shown with the measurement behind it and the reason a fingerprinter reads it. Signals your browser withholds are reported as withheld, not as failures.

    canvas, webgl, webgpu, audio, fonts, screen, client hints, automation tells

    Run the fingerprint check

  • 02

    Proxy consistency check

    Reads the address your request arrived from, then compares its geography against the browser's time zone, its declared locale and the addresses WebRTC discovers. Each comparison is graded with a severity and, where it failed, what resolves it.

    exit ip, geo country, iana time zone, accept-language, ice candidates

    Run the consistency check

02Privacy

The position

Nothing is stored.

Every measurement happens in your browser. One server call echoes back the address your request arrived from, because the comparison needs both halves; that response is built per request and then discarded.
  • 01

    No fingerprint, hash or address is written down

    Not to a database, not to a file, not to an analytics event. The results exist in the page in front of you and go away when you close it.
  • 02

    No third-party script watches these pages

    There is no tag manager, no session recorder and no advertising pixel anywhere on this marketing surface. It is the same claim the rest of the site makes, and it is one you can settle in your own network panel.
  • 03

    The echo endpoint keeps no request log

    It reads the forwarding headers, answers, and returns a no-store response so that neither a shared cache nor your own browser can hold on to it.

You do not have to take that on trust. The endpoint answers a plain GET and shows you exactly what it saw: /api/whoami

03Limits

Not tested here

Two checks that are missing, and why.

Both are common on public checker sites. Neither is honest to ship the way it is usually shipped.
  • 01

    DNS leak testing

    A real DNS test needs wildcard DNS on a domain we control plus resolver-side logging, which means recording your queries. That would contradict the section above, so it is not here. The property worth checking in your own configuration is whether your proxy resolves names at the exit rather than on the local machine.
  • 02

    Open port scanning

    Scanning your own address from inside a browser is unreliable enough to produce false confidence, and a server-side scanner is an abuse magnet that would need rate limiting, an allow list and a log. Neither version earns its result.

These are diagnostics, not a product tour. Deriving time zone and locale from the proxy exit is baseline work in this category; VeilBrowser does it and so do the alternatives. What differs is whose machines the browsers run on.

Contact salesFingerprint documentation