The anonymizer type, not just one flag
VPN, proxy, Tor and privacy relay are reported as separate flags next to hosting, datacenter and malicious-IP signals, so a VPN and an open proxy on a hosting range do not read the same.
VPN and proxy signups
VPN and proxy signup detection for your website
Know when a signup arrives through a VPN, a proxy, Tor or a privacy relay, with the reason spelled out. FindIP Shield runs the same network intelligence as the FindIP API on every signup attempt on your site, and leaves the response up to you.
Free Preview · 10,000 events per site per day · No credit card · Terms apply
VPN
Proxy
Tor
Privacy relay
Hosting network
Malicious IP
The problem
You want to know, not to blanket-block.
Some of your best customers sign up through a VPN. So do some of the people testing your signup for weaknesses. Treating both the same way, by blocking or by ignoring, loses something either way.
A JavaScript check in the page cannot tell them apart, because the page only sees what the browser chooses to show. The network that carried the request can be classified, but that needs IP intelligence, not a regex.
Shield reports the classification for each signup attempt, reports VPN, proxy, Tor and privacy relay as separate flags, and lets you decide per form what, if anything, to do.
What Shield shows you
The evidence, then the response you choose
The network behind the session
ISP, ASN, hosting versus consumer access, and whether the IP or ASN changed during the session. All of it on the signup event, none of it from the form values.
A proportionate response
Let VPN signups through, ask a Turnstile check of proxy signups, stop Tor signups, or just record everything. Per form, changeable at any time, every outcome logged.
Setup
Install with one script tag
For any site where you can add a script tag. Pin a version with an integrity hash if your security policy needs it.
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? Need the same signals from your own backend instead? Use the FindIP VPN detection API.
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
No. The browser SDK reports the signup event; the classification happens on FindIP infrastructure from the visitor IP, using the same intelligence as the FindIP lookup API. The browser cannot hide the network it arrived through.
Yes. Relays are reported as their own flag, separate from VPNs, proxies and Tor, so you can treat them differently.
We recommend against blocking on a VPN signal alone. Watch first, see which reasons accompany the signups you later regret, and respond to those combinations. The product wording is deliberate: a score is an assessment, not proof.
The status is reported as unknown, never as safe. Treat unknown as unknown.
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 siteFree Preview · Informational risk signals · You control enforcement