Spam protection
Bot detection
Bot detection is the set of checks that tell automated form submissions from real visitors, using signals such as request headers, IP reputation, honeypots and message content.
Also called: spam bot detection, anti-spam, form bot protection
A form on a public page will be found by bots. Some are crude scripts that post the same text to thousands of forms. Others try to look like a browser. Bot detection is the work of telling them apart from the people who actually want to reach you, without making those people jump through hoops.
Signals that are used
- Hidden traps. A honeypot field that only a script would fill in.
- Request headers. Real browsers send a consistent set of headers. A script built on a plain HTTP library usually does not.
- Origin. A browser tells the server which page the form was sent from. Spam scripts often leave that out or send another site.
- IP reputation. Addresses already known to send spam.
- Content. Link shorteners, cold sales pitches, names with digits, text in a language you do not expect.
- Challenges. A CAPTCHA when the other signals are not enough.
Why layers beat a single check
Each signal has gaps. A honeypot misses bots that render the page, a CAPTCHA frustrates real visitors, and an IP list is always behind. Adding the signals into a spam score lets a weak hint add up with another weak hint, while a message that triggers one odd signal alone is still let through.
Block, or keep for review?
Dropping a suspected bot silently means that every false positive is a lost enquiry. Keeping the suspect submission in a separate spam list lets you check it and restore it.
In StaticForm
StaticForm combines its checks into a spam probability for each submission: the honeypot and CAPTCHA you configure, an allowed-domains check on the Origin header, request header analysis, IP-based analysis and content analysis, plus an optional AI second opinion for borderline messages. A spam submission still gets a 200 OK answer, is stored in the spam list with its score and the reasons, and skips your email and webhook actions. You can mark any submission as spam or legitimate yourself. Testing a client-side form with curl will almost always land in the spam list, because it does not send the headers of a real browser; test from a browser instead.
Learn more
Related terms
- Honeypot fieldA honeypot field is a form input hidden from people but visible to bots. Real visitors leave it empty, so any value in it marks the submission as spam.
- CAPTCHAA CAPTCHA is a challenge that separates people from automated scripts, used to stop bots from submitting forms, creating accounts or scraping a site.
- Form submissionA form submission is one completed send of a form: the values the visitor entered, plus details such as the time, that a backend receives, checks and stores.