Stop form spam and bots — without a CAPTCHA

The layers that catch a form bot

• Invisible honeypot: a decoy field a human never sees and a scripted bot fills — an instant, near-certain tell.
• Submit timing & interaction: forms filled in under a second, with no real focus or keystrokes, are machines. Pasted-in-one-shot values corroborate.
• Content spam analysis: spam links, known keyword patterns, BBCode/anchor injection — and script mismatch: Cyrillic or CJK text in a Latin-language form, the classic Russian/Chinese spam signature.
• Device & network intelligence: the same submission is scored against bot tells, VPN and datacenter IPs, and the cross-site reputation network — a fraudster burned elsewhere is flagged the instant they reach your form.

Why not just a CAPTCHA?

CAPTCHAs tax every real user to stop a few bots, and modern solver farms beat them cheaply. Prynt runs silently: honest submissions never see a challenge, and only genuinely suspicious ones are stepped up to Prynt Challenge (a risk-adaptive proof-of-work) or blocked outright.

Drop it into any form

A single call wires honeypot, timing and content analysis into any form — the widget handles the submit and blocks bots for you:

const prynt = await Prynt.load({ apiKey: 'pk_live_…', endpoint: 'https://api.pryntid.com' });

prynt.protectForm(document.querySelector('#contact-form'), {
  autoGuard: true,                 // intercept submit, verify, block bots automatically
  expectedScripts: ['latin'],      // flag Cyrillic/CJK spam
  onBlocked: () => showError('This submission was flagged as spam.'),
});

Prefer a framework or CMS? There's a React hook (useProtectForm) and a WordPress plugin that protects comments, registration, login and WooCommerce checkout with one setting.

One-click presets

In your console, turn on ready-made rules with a click: challenge high-risk countries, block form bots, challenge content spam, or challenge VPN & datacenter traffic — then tune them anytime.

Honest by design

Form Shield is a deterrent backed by real enforcement, not theater. The blocking happens server-side where a bot can't reach it, every verdict is logged for your audit trail, and the client checks fail open so your real users are never held hostage to our uptime.