These public vendor tests let you inspect different kinds of output. A browser session demo can show a user journey; a public IP checker describes a connection. Neither establishes the exact fields or quota of your production plan.
Public testing options
| Vendor | Test type | Open test | What to inspect |
|---|---|---|---|
| ShieldLabs | Browser session demo | Open the Anonymity Checker ↗ | A browser-oriented product preview. Compare the network observations and named signals in a controlled session; the preview does not establish your account’s quota or plan. |
| Fingerprint | Browser and checkout demo | Open the VPN detection demo ↗ | A regional-pricing example that demonstrates a VPN-related application decision. Use the vendor’s instructions and inspect the production integration separately. |
| IPQualityScore | Public IP lookup | Open the VPN IP test ↗ | A public IP checker with lookup limits. A public test and an authenticated production API can have different fields and access conditions. |
| IPinfo | IP context preview | Open the IP context preview ↗ | Inspect the visible connection, network and available anonymization data. Verify paid API fields against the selected Core or Max plan. |
| proxycheck.io | Public IP lookup | Open the IP lookup ↗ | Inspect the connection classification and detection context for an IP. Public lookup limits and production API subscription terms are separate. |
SEON documents an SDK and Fraud API workflow, with trial access on request. Its public product material does not establish an equivalent self-serve demo for this directory. Read the SEON review and its linked documentation before requesting a trial.
A repeatable comparison
- Record the public connection and product output with the VPN disconnected. Keep the time and the visible IP.
- Connect the VPN and repeat the same action. For a browser demo, repeat the demonstrated account or checkout step as well.
- Inspect which fields actually changed. Distinguish a network flag from device recognition, account history or an application decision.
- Repeat with a corporate VPN, shared network or privacy relay relevant to your users. An anonymity indicator alone does not prove abuse.
Move from public preview to a pilot
For a production evaluation, use the eighteen buyer questions and verify plan access, SDK collection, latency, error handling and review workflow. Do not infer a service-level accuracy rate from a handful of public checks. Compare the same permitted test scenarios with each shortlisted provider.
Questions about a result
Each vendor operates its own test and determines its available fields and usage limits. For a problem with a vendor account, contact that vendor. For an error in our description or link, use the corrections process.