Stack Shelfetnextras.com

Anonymity checkers

amiunique.org

amiunique.org logo on the cover of the review

AmIUnique displays a browser fingerprint and statistics derived from user-provided data, while describing its purpose as browser-fingerprint research and user information. Viewing a fingerprint also collects it and places a cookie in the browser for 4 months.

For readers assessing browser characteristics, the key distinction is between inspecting a fingerprint and treating it as proof of anonymity.

Editorial review based on public sources, without hands-on testing; facts checked on 2026-10-31.

This page contains no partner link to this service.

Logo
Service logos remain the property of their owners; we use them for identification only.
Name
amiunique.org
Category
Anonymity checkers
Official site
amiunique.org · No link provided
Facts checked

Fingerprint views come with a cookie

The following features and conditions are described on AmIUnique’s pages, checked on 2026-10-31.

  • Fingerprint view: users can inspect their browser fingerprint.
  • Statistics: users can consult statistics based on user-provided data.
  • Cookie condition: viewing a fingerprint places a cookie in the browser for 4 months.
  • Android app: offered for scanning a mobile device fingerprint.
  • Chrome extension: offered for contributing browser fingerprints.

Fingerprint data feeds a research project

AmIUnique says it studies browser-fingerprint diversity and provides data intended to help developers design defenses. Its stated user-facing aim is to inform people about their configuration and how trackable it is. Those are the provider’s descriptions of the project and its purpose.

The site describes fingerprinting as collecting information from a remote device for identification purposes. It says the service is maintained by researchers studying software monocultures and software diversity on the web, and that the site is hosted at Inria. These statements describe the provider’s account; the pages read do not independently verify them.

The diagram shows the fingerprint view and its stated browser-cookie condition.
The homepage describes collection and cookie placement when a fingerprint is viewed. Built from facts published on amiunique.org; checked 2026-10-31.

No plan terms define paid access

The assigned sources describe fingerprint viewing, statistics, and research.

Device attributes form the fingerprint

The fingerprint can draw on browser and device characteristics, rather than a single setting. AmIUnique lists browser and operating-system versions, screen resolution, architecture, fonts, plugins, and microphone and camera information among possible inputs. It also says it collects headers, platform information, storage use, device settings, and rendering information.

The site identifies rendered images from HTML Canvas and WebGL as collected data, and says it uses Plugin Detect to identify plugins. It describes fingerprinting itself as stateless and transparent to the user, and says fingerprinting does not require cookies. That general description sits alongside the separate cookie condition for viewing a fingerprint.

The diagram groups reported browser and device attributes with rendering data and plugin detection.
Inputs and methods described by the vendor. Built from facts published on amiunique.org; checked 2026-10-31.

Check data handling before relying on a result

Before relying on a checker in a work process, ask the provider how the reported data is retained and whether users can request deletion. Ask what the observed sample represents, since a uniqueness statistic needs a comparison basis to be meaningful.

Clarify whether access has a price, what trial or refund terms apply, and which support channels handle account or technical questions. Ask whether integrations or setup steps are required for the intended use. These are evaluation questions, not claims about AmIUnique’s terms or capabilities.

The checker pairs a fingerprint with statistics

The main service combines a browser-fingerprint view with statistics based on user-provided data, giving readers both an individual result and a statistical context.

AmIUnique says its output includes a concise summary of a browser’s main characteristics and global statistics. It also describes a synthetic view with statistics about a device’s uniqueness within its observed sample.

The provider lists an Android app for scanning a mobile device fingerprint. Its Chrome extension is described as a way to contribute browser fingerprints.

The diagram shows the summary and sample-based statistics the vendor says it provides.
The FAQ describes a browser summary and uniqueness statistics. Built from facts published on amiunique.org; checked 2026-10-31.

Collection and scope constrain interpretation

The main documented limitation is the cookie condition: viewing a fingerprint collects it and places a cookie in the browser for 4 months, according to the homepage. The FAQ also warns that fingerprints can track users across websites without informing them.

AmIUnique’s FAQ says attackers may exploit software or configuration vulnerabilities identified through fingerprinting. AmIUnique describes browser fingerprinting as collecting information from a remote device for identification purposes.

The research investigates automatically reconfiguring a user's platform to fuzz its device fingerprint realistically. Several practical details remain open; they are listed under What we could not confirm.

Useful for inspecting browser characteristics

AmIUnique fits readers seeking a view of browser characteristics and statistics based on user-provided data. Its stated purpose also includes informing users about their configuration and how trackable it is.

The statistics are described in relation to the service’s observed sample, so they provide context for the reported fingerprint rather than proof of anonymity. Readers looking for a research project on fingerprint diversity may also find its stated focus relevant.

Compare checkers by reported data

When comparing browser-fingerprint checkers, examine which parameters they report and how they explain the basis for comparisons. In general, also compare privacy statements, access conditions, limits, and any stated costs before relying on a result.

What we could not confirm

  • Pricing: cost of access
  • Plans: available options and terms
  • Trials and refunds: eligibility and conditions
  • Support: contact channels and response times
  • Integrations and setup: requirements for use
  • Data retention and deletion: retention period and request process
  • Observed sample: size and composition
  • Privacy and security: independent assessment

What the fingerprint pages explain

What does AmIUnique mean by browser fingerprinting?

AmIUnique describes browser fingerprinting as collecting information from a remote device for identification purposes. Its pages explain the concept as information drawn from browser and device characteristics, rather than a single browser setting.

Which device characteristics can appear in a fingerprint?

The listed characteristics include browser and operating-system versions, screen resolution, architecture, fonts, plugins, and microphone and camera information. The site also says it collects headers, platform information, and storage use.

How do rendered images feature in the collected data?

AmIUnique says it collects rendered images from HTML Canvas and WebGL. These are described as part of the data the site gathers for fingerprinting, alongside other browser and device information.

How does the site detect browser plugins?

The FAQ says AmIUnique uses Plugin Detect to detect plugins. Plugin information is also included among the browser-fingerprint characteristics described by the provider.

What do the statistics say about uniqueness?

AmIUnique says it provides a synthetic view with statistics about a device's uniqueness among its observed sample. It also says the output includes global statistics and a concise summary of a browser’s main characteristics.

Does fingerprinting require cookies on this site?

The site says browser fingerprinting does not require cookies and describes the process as stateless and transparent to the user. Separately, its homepage says viewing a fingerprint collects it and places a cookie in the browser for 4 months. These statements distinguish the general fingerprinting description from the cookie condition attached to viewing a result.

Rely on the result only for its stated scope

Fits if the purpose is to inspect browser characteristics or review the provider’s sample-based statistics.

Probably not if the requirement is proof that a browser is anonymous; the stated output concerns fingerprint characteristics and trackability.

Main risk… viewing a fingerprint places a cookie in the browser for 4 months, according to the homepage.

Sources

The facts above were taken from the public pages listed here, and each entry shows the date it was read.

How we put this page together

Editorial team of Stack Shelf. Prepared by the editorial team of Stack Shelf from the public sources listed above; the facts were checked on 2026-10-31. Nobody tried the service in practice. We revise the text whenever those sources are updated.

Last updated:

Right of reply

If you represent amiunique.org and think this entry is inaccurate or out of date, write to us and attach evidence. After the refutation is documented, the entry is corrected or removed. Entries are not removed or toned down in exchange for money.

Our contact for replies
No data available
Response time
No data available

Also covered in Anonymity checkers: neighbouring reviews

Back to the reviews