Free Preview · 10,000 events/site/day · free for real

See the risk behind every website visit.

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.

  • Stop, slow, challenge, or redirect
  • npm, script tag, or GTM
  • No credit card
  • Three privacy modes

Also for mobile apps: iOS & Android

30-second tour

See one suspicious sign-up, explained

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.

  • IP intelligence, connected to activity on your site
  • The reasons behind every risk score
  • What Shield recommended, and what actually happened

Understand a suspicious signup

A sign-up on a sample shop came through a VPN, and the same visitor switched networks. Shield shows the reasons, recommends a check, and records that the page did not act.
Read the transcript
  1. An IP lookup tells you about an address.
  2. Shield connects that intelligence to activity on your site.
  3. See the reasons behind the risk.
  4. Follow the session across networks.
  5. Shield recommended a challenge. The page did not act.
  6. See what’s happening on your website.
  7. Try Shield free, on your own site!

Risk signals that make website activity explainable

Turn raw visits into clear, inspectable context before adding friction to legitimate customers.

VPN, proxy, and Tor

Recognize anonymized and relayed traffic across common visitor journeys.

Hosting and datacenters

Separate consumer access networks from automated infrastructure.

Network rotation

See IP, ASN, and country changes inside a visitor session.

Malicious infrastructure

Surface scanner, malicious-IP, and reputation signals with reasons.

From installation to useful signal in four steps

Shield starts by monitoring. Review the evidence in your dashboard, then switch on a response for the forms that need one.

Create a Shield site

Add the domain you control and select the privacy mode appropriate for your visitors.

Install one snippet

Use the npm package, a versioned CDN script, or Google Tag Manager.

Receive risk events

Signup, login, lead, checkout, and page activity become searchable events and sessions.

Investigate, then respond

Review scores and reasons, then stop, slow down, challenge, or redirect risky submits on the forms you pick.

See how to add Shield to your site

Two ways in, both free. Pick the one that matches how your site is run; they can be used together.

Website snippet

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.

Add Shield with a website snippet

Create a Shield site, copy the script snippet into your website, publish, and see the first visit arrive with its explanation.
Read the transcript
  1. Already use FindIP? Use the same account.
  2. Add your website.
  3. Copy your snippet into your website.
  4. Publish your change, and open your site.
  5. Shield received your first visit!
  6. Your first visit, explained.
  7. Add Shield to your website.
Add Shield to my website

Cloudflare, no code

Connect your Cloudflare account and pick one hostname. Screens every request at the edge, starting in Monitor mode. Needs a Cloudflare-proxied hostname.

Connect Shield through Cloudflare

Authorize the Cloudflare connection, choose one hostname, and start in Monitor mode, with a decision and its reason for every visit.
Read the transcript
  1. Using Cloudflare? Connect Shield without editing your website.
  2. Authorize the Cloudflare connection.
  3. Choose the hostname to monitor.
  4. Start in Monitor mode.
  5. See traffic decisions, and their reasons.
  6. Watch first. Choose your blocking rules when you’re ready.
  7. Screen visitors at the edge.
How the Cloudflare connection works
Developer friendly

Install in minutes, keep control in your application

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 integration
npm install @findip/shield

import { init, track } from '@findip/shield';

init({
  siteKey: 'pub_xxxxxxxxx',
  privacyMode: 'balanced',
  autoTrack: true
});

await track('signup_attempt');
Form protection

Choose what happens on a form

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.

  • Protect one form at a time, from the forms Shield discovered
  • Stop, slow down, verify, or just record
  • Every outcome recorded next to the recommendation

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 what happens on a form

Protect a sign-up form with a verification check, switch protection on, and see a suspicious sign-up verified and recorded.
Read the transcript
  1. Choose the form you want to protect.
  2. Choose how this form responds to risk.
  3. Switch protection on.
  4. A matching signup gets extra verification.
  5. Verification passed. Continue signing up.
  6. See what was recommended, and what happened.
  7. Your forms. Your rules.

Privacy choices are part of the product

Choose how much browser context is appropriate. Shield never needs passwords, card data, or full form contents.

Strict

Minimum context. Use infrastructure-level signals with the smallest browser footprint.

Balanced

Recommended default. Add limited browser and session context for more useful investigation.

Advanced

More diagnostic context. Enable only when your notices, consent, and use case support it.

Limits, and what Shield does not do

The honest edges of the product, so you can judge whether it fits before you install anything.

Is the Free Preview really free, and will it stay free?

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.

What are the Free Preview limits?

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.

Is Shield a security boundary?

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.

What can Shield actually do when it sees something risky?

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.

Does Shield fingerprint devices?

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.

What happens if Shield is slow or unavailable?

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.

Does a high risk score mean the visitor is malicious?

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.

What does Shield collect?

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.

Does using the FindIP API give me Shield data?

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.

Start seeing visitor risk today.

Create a free Shield site, install the SDK, and receive your first risk event. No credit card required.

Start with Shield free

Free Preview, explained · Monitor first, respond when ready · Terms apply