Which trials come from infrastructure
Datacenter and hosting networks are where scripted signups live. Shield flags them with the reason, alongside proxy, VPN, Tor and relay signals, on every signup attempt.
Trial abuse
Free trial abuse prevention that starts with visibility
Serial trial abusers burn compute, quota and support time before they ever reach a payment screen. FindIP Shield shows you which trial signups come from hosting, proxy and rotating networks, so you can add friction only where the risk is, and keep the signup fast for everyone else.
Free Preview · 10,000 events per site per day · No credit card · Terms apply
Hosting / datacenter
Proxy
VPN
Tor
IP rotation in session
Malicious IP
The problem
Trial abuse is a signup problem, not a billing problem.
Stripe reported 6.2 times more abusive free trials between November 2025 and February 2026 than a year earlier, and found that at AI companies more than one in six signups was linked to multi-account abuse. The cost lands before any card is charged: inference, storage, emails, support.
Blocking every VPN is the wrong fix. It turns away privacy-conscious customers and corporate users while a patient abuser simply switches to a clean residential proxy. What you need is the network context behind each signup, and a response that scales with the risk.
Shield gives you that context on the signup form itself, with the final decision kept on your server where it belongs.
What Shield shows you
The evidence, then the response you choose
Networks that change mid-session
A visitor whose IP or ASN rotates between the landing page and the submit is unusual. Shield records the change as a reason you can see on the event.
Trace a trial back to its session
Attach a hashed user ID after signup. When a trial account turns out to be abusive, you can see the session and network that created it and tune your response.
Setup
Install on your signup flow in three steps
For SaaS applications: the npm package fits bundled apps, the script tag fits everything else. Both report the same events.
Create a Shield site
Sign in, add the domain you control, and pick a privacy mode. You get a public site key; nothing connects until it is on a page.
Add the snippet
Paste one script tag before the closing body tag, or run npm install @findip/shield and call init() with your site key. Auto page and form tracking is on by default.
Watch the first real event
Submit a test on your own form. The event, its risk score and the reasons behind it appear on the site dashboard moments later.
Prefer another route? Install through Google Tag Manager without touching the bundle.
Boundaries
What a risk score is, and what it is not
An assessment, not proof. A VPN, a hosting network or a changing IP is common for privacy-conscious and corporate users too. Shield explains the reasons so you can decide; it does not pass judgement on a person.
Friction, not a security boundary. Anything decided in the browser can be bypassed by someone who controls it. For decisions that matter, verify the session from your server with your secret key.
Unknown is never safe. Where no intelligence was available the status is unknown. Shield fails open: if a decision does not arrive, the form submits as normal.
Questions
Frequently asked
Score, do not hard-block on one signal. Start in monitor only, look at which reasons actually accompany abusive trials on your site, then add a Turnstile check or a slow-down for those combinations. A lone VPN signal is usually not enough to act on.
No. Shield reports network signals per session and lets you attach your own hashed user ID. Cross-account linking stays in your system, where you have the business context to do it well.
Yes, anyone who controls the browser can bypass anything decided there. That is why Shield gives you a server-side verify endpoint: check the session with your secret key before provisioning the trial.
Shield records checkout and payment-attempt events with the same network signals, so card-testing patterns from hosting or proxy networks show up on the checkout form as well. See the checkout fraud signals page.
Keep reading
Related
Start by watching one real flow.
Create a free Shield site, install it, and look at the first real event before you decide on any response.
Try Shield on my signupFree Preview · Informational risk signals · You control enforcement