Browser Identity
Review

Browser fingerprinting demos and evaluation routes

Use a supported live demo, open-source example, free API allowance or tailored evaluation. Inspect which product is actually being demonstrated.

PUBLIC TESTS AND EVALUATION RESOURCES

Inspect identity and signals separately.

Repeat a permitted visit in the same browser, then change one condition such as storage or network. Compare the identifier, confidence and individual findings. Use unrelated devices as controls.

Links open the provider or project’s own site. This directory does not embed their checkers or receive their results. A browser observation, an IP classification and an account-based evaluation answer different questions.

Directory updated · Divya Kulkarni

Find the right test

Choose a resource by the evidence it exposes. Product evaluations for the full shortlist remain below.

4 of 4 resources

01 / ShieldLabs

ShieldLabs Anonymity Checker

Visitor, device and risk context

Explore current device/network evidence and identification within the public checker’s scope.

Output
Identifiers, named network conditions and risk output available to the public visit.
Access and limits
Public checker; account events and production integration require supported account association.
Evaluation idea
Record a permitted baseline visit and the individual findings. Keep an unavailable assessment distinct from a low-risk result.

02 / Fingerprint

Fingerprint identification playground

Hosted recognition and Smart Signals

Inspect a current identification event and the exposed browser and network signals.

Output
Event/visitor identity and available Smart Signals; fields depend on the demo and product plan.
Access and limits
Public playground; production signal and client entitlements are separate.
Evaluation idea
Read tampering, automation and network outputs separately from the visitor identifier and any aggregate score.

03 / BrowserLeaks

BrowserLeaks JavaScript information

Individual browser surfaces

Inspect JavaScript-visible attributes and supported browser capabilities.

Output
Navigator, screen, locale, timezone and related technical values.
Access and limits
Public diagnostic page. Other BrowserLeaks pages cover separate surfaces such as WebRTC.
Evaluation idea
Inspect one permitted configuration and retain missing fields as unavailable. Explain causes instead of declaring every unusual value fraudulent.

04 / CreepJS

CreepJS official browser test

Fingerprint and JavaScript integrity

Inspect fingerprint behavior and JavaScript lie patterns using the project’s official deployment.

Output
Fingerprint observations, hashes, lie patterns and research-oriented scores.
Access and limits
Public open-source diagnostic. The project repository identifies its official GitHub Pages deployment.
Evaluation idea
Record version, date and relevant API categories. A diagnostic score is not an application account-abuse verdict.

Keep the comparison repeatable

  1. Define the protected action and use only your own or authorized data.
  2. Record the provider, timestamp, assessed entity, field definitions and scale.
  3. Change one permitted condition and repeat the same action.
  4. Include legitimate controls and keep unavailable fields distinct from negative findings.
  5. Evaluate the supported integration and account access before applying the result to customers.

Product access and full-shortlist evaluations

These are the existing vendor routes and their recorded access conditions. A trial request, product walkthrough or documentation page is not another public checker.

Product demonstration and account evaluation

IPQualityScore

Inspect the documented device integration and request appropriate account access; general IP checkers test a different product layer.

Open evaluation route

What to evaluate ↗

Tailored product demo

LexisNexis ThreatMetrix

Request a representative identity-to-decision walkthrough, including accessible identifiers, data governance and integration requirements.

Open evaluation route

What to evaluate ↗

Maintainer’s browser demo

FingerprintJS (open source)

Open the maintainer demo and compare your own permitted browser sessions; keep the open-source output separate from the commercial product.

Open evaluation route

What to evaluate ↗

FAQ

Is a matching fingerprint the same as proof of a person’s identity?

No. A browser or device identifier supports continuity under the product’s documented scope. It is not legal identity, account ownership or proof that two people are the same. Check the actual integration and supported identity fields.

Does this directory collect my checker result?

No. The cards and links are static HTML, and JavaScript only filters this directory. Each linked provider controls collection, results, retention and access on its own site.

Are public demos, sandboxes and product trials equivalent?

No. A public demo exposes a limited interaction. A sandbox exercises documented test behavior, while an account-based or assisted trial evaluates a particular product scope. Keep each output and its access conditions attached.

Can scores from different checkers be compared directly?

Only when their assessed entity, definitions and scales are comparable. Record the individual fields and missing results. A network reputation score, identification confidence and account-risk verdict are different measures.

Summarize this page with