Published distributions and population data: per-attribute frequencies, TLS handshake statistics seen on real networks, fingerprint-to-application mappings, and longitudinal platform measurements across millions of sites. This is the only section of this catalogue where a percentage means anything, because in every case somebody else measured it and published how.
Published distributions and population data. The only place in this catalogue where a percentage means anything, because someone else measured it and says how.
Live per-attribute distributions from the AmIUnique corpus. Note the path: /stats returns 404.
https://amiunique.org/fingerprints-global-statistics — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://amiunique.org/fingerprints-global-statistics
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
The entropy methodology and aggregate results behind the test, written to be checked.
https://coveryourtracks.eff.org/learn — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://coveryourtracks.eff.org/learn
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://tlsfingerprint.io/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://ja4db.foxio.io/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Public device and browser attribute datasets with an API in front of them.
https://deviceandbrowserinfo.com/info_device — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://deviceandbrowserinfo.com/info_device
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://httparchive.org/reports
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://almanac.httparchive.org/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://www.chromium.org/Home/chromium-privacy/privacy-sandbox/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Why this register cites distributions instead of computing one
The catalogue prints no score, percentile or rarity figure for any entry, because it has tested no tool. Its one population is of browsers: the browser sheet compares your browser with the devices these eight sites have read and prints the size of that population beside every share. The entries in this section are the published alternatives: corpora whose collection method, vantage point and time window are published alongside the numbers, so a reader can judge what the numbers describe.
Every one of them has limits that its own authors state. A research corpus is self-selected. A university network's traffic is one network's traffic. A crawl measures pages as fetched from a fixed vantage point, which under-represents anything served conditionally on client characteristics — a caveat that matters especially when the thing being measured is detection script deployment.
What to do with a distribution once you have one
Use it to answer whether a value is common at all, which is a question a distribution can answer. Do not use it to compute how rare you personally are, which is a question that requires the corpus to resemble the population you are hiding in, and none of these corpora claims to.
The attribution databases in this section serve a different purpose again: mapping a network fingerprint back to the software that produced it. Coverage there is contributed rather than exhaustive, so an absent fingerprint means nobody has submitted it, not that nothing produces it.
Answered from the fields printed above, and from nothing this register has not checked.
Where can I find browser fingerprint statistics?
In this section, and in each case with the caveat its own authors publish. Per-attribute distributions from research corpora, TLS ClientHello statistics observed on a real network, contributed fingerprint-to-application mappings, and longitudinal platform data across millions of crawled sites.
Can this registry tell me how rare my browser is?
On one page. The browser sheet compares each value your browser reports with the devices these eight sites have read, prints how many share it, and says what a tool would have to change. The size of that population is printed beside every share. The datasets in this section are larger, older populations, and each publishes its method.
Are these fingerprint datasets free to use?
Terms vary by publisher and this register does not restate them — the licence column reads not applicable for entries with no source to licence. What this catalogue does record is the address, the HTTP status and the instant the check was made, so you can go and read the terms at the source.
Donut Browser is filed in section 01 of this same catalogue, under the
same rubric, with the same fields printed against it and no exemption:
an open-source anti-detect browser under AGPL-3.0 whose Wayfern Chromium
fork applies fingerprint overrides at engine level over CDP rather than
by patching page JavaScript, with a local REST API and MCP server on your
own machine, self-hostable sync, zero telemetry, and a pre-launch gate
that refuses to start a profile when the proxy's exit geography
contradicts the profile's fingerprint. It is judged here the same way
everything in this section is judged.