Contact forms, support tickets and review submissions are the cheapest way to send you unlimited mail. A CAPTCHA taxes every real sender to inconvenience a script.
Form spam is a resource problem before it is an inbox problem: every submission costs you a ticket, a queue entry, a notification email and a support person’s attention, and you pay all of that before anyone reads the content. Because ZeroBot scores the request rather than challenging the person, you get the effect a CAPTCHA would have had without the visual puzzle, the accessibility problems or the conversion drop on your form. Screen on submit, and keep the check off your page-load path entirely.
php (form handler)
Full endpoint reference and an interactive tester are in the API docs. Get a key from the free tier — no card required.
Real tickets from real customers sit behind hundreds of junk entries, and your first-response time is measured from the junk arriving.
Every submission pages someone. At volume this is a deliverability problem for your own domain, not just an annoyance.
Spam submissions are how injection attempts reach whoever reads the ticket, and how links get seeded anywhere the content is later rendered.
Anything user-generated and public becomes an SEO target for whoever can submit it fastest.
A rejection is feedback. It tells whoever is tuning a script exactly which threshold to stay under. Silently discarding leaves them guessing, and a real visitor who trips it just sees the form succeed.
You can, but it is redundant work on the honest users. If ZeroBot is catching the traffic, consider disabling the CAPTCHA for a set of countries or traffic sources and measuring the spam rate before removing it entirely.
One HTTP round trip, median under 50ms, and it is on submit rather than page load — so it is invisible unless your API is unreachable, in which case the submission is allowed through by default.
Free tier, real verdicts, and documentation with a built-in tester.
Get started free →