Identity
Layer Review

Sybil-prevention demos, trials and evaluation routes

Inspect the actual evidence and participant journey before selecting a product. A public demo, approved API trial, assisted analysis and uniqueness enrollment are different evaluation routes.

PUBLIC TESTS AND EVALUATION RESOURCES

Connect the campaign evidence.

Start with permitted device and network observations, then evaluate account and wallet relationships for the actual campaign. Include unrelated participants on shared networks and retain the provenance of each link.

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 · Petra Novakova

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 / IPQualityScore

IPQualityScore proxy and VPN lookup

IP and connection context

Inspect network context that can corroborate a browser investigation.

Output
Supported IP classifications and risk fields when the lookup completes.
Access and limits
Public lookup route; verification or access restrictions may apply. Device-product entitlement is separate.
Evaluation idea
Use an owned or permitted address. Keep network reputation, browser integrity and account eligibility distinct.

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.

What an evaluation can establish

A browser demo shows the result for an observed visit. Wallet analysis examines recorded addresses. A credential flow establishes its stated verification property. Test the relevant layer and eligibility boundary on your own authorized cases.

Evaluation routes checked October 21, 2026. Civic Pass is discontinued.
ToolEvaluation routeAccess and scope
ShieldLabsLive signal demo and Start FreeInspect your own permitted visit, then test a new campaign using the supported integration. No wallet signature is required to inspect the product page.
Trusta LabsApply for TrustScan API accessApplication review precedes a trial key. Confirm the current endpoint and supported chains before implementation.
Human Passport (formerly Gitcoin Passport)Developer portal, API guidance and partner analysisStart with the documented product route. A wallet-analysis engagement and a real-time Scorer integration have different setup and cost.
NomisProject API applicationUse the project form for API access. The public wallet-score flow may require wallet interaction; inspect its requirements before choosing to connect or mint.
Worldcoin / World IDWorld ID sandbox and IDKitUse the isolated sandbox for integration testing. Production verification and credential enrollment are separate routes.
BrightIDApplication and verification documentationReview the app, verification and project sponsorship steps. Do not treat installing the app as completion of verification.
VerisoulAssisted demo and product evaluationThe current pricing route is demo-led. Confirm API access, included features, volume units and the terms of an evaluation.
HumanodeBotBasher setup documentationReview supported community integration and participant verification. A public guide does not establish a hosted free campaign allowance.
CivicRead the sunset noticeThere is no active Civic Pass evaluation route. Use the official notice to audit historical dependencies and choose a current alternative.
FingerprintPublic device demo and developer trialInspect your own browser’s output, then validate supported device changes and server-side retrieval on permitted traffic.

Use the same permitted cases

  1. Define the campaign’s participant entitlement.
  2. Separate device, wallet and credential assertions.
  3. Include known repeated participation, legitimate multi-wallet use and newcomers.
  4. Test trusted association, missing evidence and duplicate redemption.
  5. Review exclusions, participant effort, operating work and complete cost.

Read the complete guide and evaluation protocol.

FAQ

Does a browser checker determine Sybil eligibility for a wallet?

No. A public browser result is one evidence layer. Campaign eligibility also depends on the chosen identity or wallet-analysis method, account association and published eligibility rules. The product routes below explain the available approaches.

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