LeadShield – Block Fake Leads & Form Spam

Your contact form is filling up with junk: throwaway addresses, gibberish names, bot submissions, and — increasingly — enquiries written by AI that read exactly like a real person. Your sales time goes on chasing ghosts, and if you run Google or Meta ads, every junk conversion teaches the algorithm to find you more of the same. LeadShield screens every submission in real time and blocks the fakes before they land. No CAPTCHA. Real visitors never see a puzzle, never tick a box, never identify a fire hydrant. Detection is invisible and runs on the submission itself. What it checks

• Email — syntax, live mail-server (MX) lookup, a disposable/throwaway domain blocklist refreshed weekly, and typo rescue (someone typing gmial.com is offered gmail.com instead of being lost)
• Behaviour — a hidden honeypot field, how fast the form was completed, and whether a human actually typed, moved a mouse or touched the screen (mobile taps and browser autofill are recognised as human, never penalised)
• IP reputation — known abusive addresses, via live threat data
• Phone — format and region validity when a phone field is present
• Device fingerprinting (Pro and Agency — included in your first 14 days) — catches the same device submitting over and over. Hashed in the visitor's browser; no third-party tracking scripts are loaded on your site
• AI content analysis (Pro and Agency — included in your first 14 days) — reads the whole enquiry in context to spot machine-generated spam text and fabricated identities

Every submission gets a 0–100 risk score and a plain-English reason, so you always know why something was blocked. Exit Rescue (optional) When a visitor has typed into a form and goes to leave without sending it, one short note can remind them it hasn't been sent and take them back to it. It is off by default: switch it on in Settings → LeadShield. It shows at most once per page and never stops anyone leaving, and it runs only in the visitor's browser, so nothing they type is sent anywhere or stored unless they submit the form. Fail-open by design If LeadShield is ever slow or unreachable, your forms submit normally. An outage on our side can never cost you a real lead. This is a deliberate design choice: we would rather let one junk lead through than lose you a customer. Works with your existing forms One setting, no per-form configuration. Automatically protects:

• Contact Form 7
• WPForms
• Gravity Forms
• Elementor Forms
• Ninja Forms
• Formidable Forms
• WooCommerce registration and contact forms
• Any other form on the page, including ones added dynamically by page builders

Pricing

• Free — 100 validations/month, free forever, no credit card
• Pro $99/mo — 10,000/month, plus AI analysis, device fingerprinting, webhooks, CSV export and Google Ads / Meta exclusion exports
• Agency $249/mo — unlimited, one account for all your clients' sites, plus tunable risk thresholds and configurable data retention

Every account starts with 14 days of Pro — no card — and then stays on the Free plan unless you upgrade. Privacy The plugin sets no cookies and no browser storage on your visitors, and loads no third-party tracking. Exit Rescue, if you switch it on, runs entirely in the visitor's browser and sends nothing. Screened lead data is deleted automatically after 90 days by default (configurable, down to zero, on the Agency plan). Exactly what is sent, and when, is listed under External services below.

1.0.2

• New, optional Exit Rescue setting (off by default): one short reminder when a visitor goes to leave a form they've started without sending it. It runs only in the visitor's browser and sends nothing unless they submit.
• Nothing else changes in how your forms are screened.

1.0.1

• A clearer name in the plugin directory: LeadShield – Block Fake Leads & Form Spam.
• Added screenshots of the settings screen and dashboard to the listing.
• Nothing changes in how your forms are screened, and there is nothing to reconfigure.

1.0.0

• Initial release: real-time form screening, settings screen with API key, optional credit badge (off by default), suspicious-blocking toggle and optional form selector.