VPN, proxy, and Tor
Recognize anonymized and relayed traffic across common visitor journeys.
FindIP Shield scores every signup, login, lead, and checkout by the network behind it—VPN, proxy, Tor, hosting, malicious IPs—and can stop, slow down, challenge, or redirect risky submits on the forms you choose. It scores the network, not the device: no device fingerprinting, and never passwords, payment details, or form values.
Follow a sample visitor from the sign-up form to the evidence in your dashboard: where they connected from, why the risk is high, and what your page did about it.
Turn raw visits into clear, inspectable context before adding friction to legitimate customers.
Recognize anonymized and relayed traffic across common visitor journeys.
Separate consumer access networks from automated infrastructure.
See IP, ASN, and country changes inside a visitor session.
Surface scanner, malicious-IP, and reputation signals with reasons.
Shield starts by monitoring. Review the evidence in your dashboard, then switch on a response for the forms that need one.
Add the domain you control and select the privacy mode appropriate for your visitors.
Use the npm package, a versioned CDN script, or Google Tag Manager.
Signup, login, lead, checkout, and page activity become searchable events and sessions.
Review scores and reasons, then stop, slow down, challenge, or redirect risky submits on the forms you pick.
Two ways in, both free. Pick the one that matches how your site is run; they can be used together.
Paste one script tag (or use npm or Google Tag Manager). Sees visits, sessions and form submits. You need access to edit and publish your website’s HTML.
Connect your Cloudflare account and pick one hostname. Screens every request at the edge, starting in Monitor mode. Needs a Cloudflare-proxied hostname.
Shield can act on a risky submit in the page, and your server can confirm any session with the verify endpoint. Your server remains the authority for access, payment, or fraud decisions.
View on npm Read the implementation guide Use the no-code Cloudflare integrationnpm install @findip/shield
import { init, track } from '@findip/shield';
init({
siteKey: 'pub_xxxxxxxxx',
privacyMode: 'balanced',
autoTrack: true
});
await track('signup_attempt');
Installing the snippet changes nothing by itself. When you’re ready, pick a form and a response, such as a quick Turnstile check for suspicious sign-ups, and switch protection on.
Browser protection adds friction for bots and casual abuse. For sign-ups, logins and payments that matter, also confirm the session on your server with the verify endpoint. The Turnstile check needs your Cloudflare Turnstile keys.
Choose how much browser context is appropriate. Shield never needs passwords, card data, or full form contents.
Minimum context. Use infrastructure-level signals with the smallest browser footprint.
Recommended default. Add limited browser and session context for more useful investigation.
More diagnostic context. Enable only when your notices, consent, and use case support it.
The honest edges of the product, so you can judge whether it fits before you install anything.
Yes. Every site gets 10,000 recorded events a day and every feature, with no credit card and no trial clock. There is no paid plan today. If we ever end the preview, lower the default quota or charge for something that is free now, you get at least 90 days' notice by email and in the dashboard. What free means here, and why.
Each site has a daily event quota — 10,000 events per day by default — plus per-minute rate limits. Beyond them, ingest answers 429 and those events are not recorded. Cloudflare edge requests are counted separately from browser events. A real site that needs more can ask for a raise at no charge. See the Free Preview page and the terms.
No. In-page enforcement is friction against bots and casual abuse. A determined attacker controls the browser, so anything decided there can be bypassed. For decisions that matter, verify the session from your server with your secret key — that is a decision no client can bypass.
On a form you configure, Shield can monitor only, slow the submit down, ask for a Cloudflare Turnstile challenge, block the submit, or redirect. On a Cloudflare-connected hostname it can report traffic and apply the access rules you set. It never acts on a form you have not configured.
No. Shield scores the network a visit comes from — VPN, proxy, Tor, hosting, malicious IPs, IP changes within a session — not the device. Its visitor ID is a random first-party value; clearing site data starts a new one. If the question is whether the same device is behind a new account, see how Shield compares with device identification.
The SDK fails open: if a decision does not arrive, the form submits as normal. Shield being down does not take your forms down with it.
No. A score summarizes network signals — a VPN, a hosting network, or a changing IP are common for privacy-conscious and corporate users too. Shield explains the reasons so you can decide; it does not pass judgement on a person. Where no IP intelligence was available, the status is unknown — treat that as unknown, never as safe.
Never passwords, card details, or the contents of form fields. How much browser and session context is collected depends on the privacy mode you choose, and some context features are opt-in. The specifics are in data collection and privacy modes.
No. The API answers questions about an IP you send it. Shield reports the activity on a site where it is installed. The same account covers both.
Create a free Shield site, install the SDK, and receive your first risk event. No credit card required.
Start with Shield freeFree Preview, explained · Monitor first, respond when ready · Terms apply