Spam leads

See which lead form submissions come from networks real customers rarely use

Spam leads cost a sales team time before anyone notices the pattern. FindIP Shield records each lead and contact form submission on your site with a risk score and the network reasons behind it, without reading what was typed, so you can see where the junk comes from and add a check only on the forms that need one.

Free Preview · 10,000 events per site per day · No credit card · Terms apply

Hosting / datacenter Proxy VPN Tor Privacy relay Malicious IP
The problem

A form plugin sees the message. It does not see the connection.

A lead form accepts whatever arrives. A content filter can judge the words, and a CAPTCHA on every visitor judges nobody in particular while it costs real prospects a step.

Neither says where a submission came from. Ten enquiries in an hour from a hosting provider's address range look, in the inbox, exactly like ten enquiries from ten offices.

The network is the part of a submission the sender cannot easily rewrite. Seeing it next to each submit is usually enough to tell a campaign that works from a script that found your form.

What Shield shows you

The evidence, then the response you choose

Every lead submit, with its network

Shield records lead_form_view and lead_submitted events with a 0 to 100 risk score and the reasons behind it: hosting or datacenter, proxy, VPN, Tor, malicious-IP history. It reads form attributes only, never the name, email or message.

A response per form, chosen by you

Installing changes nothing. When you are ready, pick the contact form Shield has seen and choose monitor only, slow down, a Cloudflare Turnstile check, or stop. Real prospects with an allow recommendation are never touched.

Rules for the pattern you actually see

Add a custom rule for a network, a country, an ASN or a submit velocity, such as more than a set number of lead submits from one IP in a window. The enforcement log lists every submit that was stopped, slowed or challenged, and why.

Setup

Install on WordPress in three steps

Most lead and contact forms run on WordPress, so that route is shown first. The plugin needs no code and loads nothing until a site key is saved.

Install the plugin

In WordPress go to Plugins, Add New, search for FindIP Shield and activate it. The plugin loads nothing until a site key is saved.

Paste your site key

Create a Shield site for your domain at findip.net and paste the public site key into the plugin settings. Choose strict, balanced or advanced privacy mode and the consent behaviour you need.

Open the dashboard

Visits, sessions and form activity start arriving. With WooCommerce active you also see cart, checkout, payment-failure and order-received context.

Prefer another route? Not on WordPress? Use the script tag, npm, or Google Tag Manager.

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. Shield never reads form values, so it does not judge what was written. It reports the network a submission came from and why that network is risky. It works next to a content filter, not instead of one.

Not unless you configure a response for a form. Installing is monitor only. A VPN or a corporate network is common among real prospects, which is why a risk score is an assessment and not proof. Start by watching, then add a Turnstile check for the highest scores. Shield fails open: if a decision does not arrive, the form submits as normal.

Shield identifies a form by its id, name or action and intercepts normal button submits. A form that a script submits by calling form.submit() directly does not fire a submit event, so it is not intercepted in the page. Check the form on your own site in monitor mode before relying on a response.

No. Shield acts in the page, before the form is sent, and shows the evidence in its dashboard. Routing, scoring and deleting leads stay in your own form handler or CRM. For a decision that no browser can bypass, verify the session from your server before you accept the lead.

Shield is in Free Preview: 10,000 events per site per day, no credit card. Beyond the quota events are not recorded; they are never silently dropped as safe.

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.

Monitor my lead form

Free Preview · Informational risk signals · You control enforcement