The business protection field guide

Inspect a result. Then test your workflow.

Public demonstrations can show product output. Your own pilot must establish event association, policy behavior and customer recovery.

ShieldLabs demo

Inspect device, network and risk output in the vendor’s demonstration environment. Use the review to understand the wider account-abuse workflow.

Open the official demo ↗

Fingerprint demo

Inspect an identification and available environment signals. Confirm the current platform and plan before assuming a demonstrated signal is included in a purchase.

Open the official demo ↗

How to use a demonstration

Inspect the fields returned, their definitions and their relationship to the current browser event. Do not convert a single demonstration into an accuracy claim. Your application still needs a server-side evidence boundary, an eligibility policy and a response to missing results.

Use the shortlist guide to prepare a vendor evaluation and the integration checklist to define the protected action.

Before you choose

FAQ

Do these checks run on this website?

No. The directory links to provider websites. Each provider runs its own demo or lookup and sets its available fields and usage limits.

Does a public demo include production access?

A public preview lets you inspect an example result. API access, plan features, quotas and trial eligibility must be checked separately with the provider. A requested demonstration is not an unrestricted public checker.

Why can two tests return different results?

A browser demo can use device and session observations, while an IP lookup evaluates an address. Collection time, signal coverage and product scope differ. Compare the same permitted scenario and keep the original output from each test.