reCAPTCHA Alternatives for Contact Form Spam
Compare honeypots, Turnstile, hCaptcha and server-side spam checks for contact forms. Learn what each catches and how to combine them in StaticForm.
On this page
A useful reCAPTCHA alternative depends on the spam you receive. A honeypot can catch bots that fill every input. Turnstile and hCaptcha provide an alternative challenge provider. Server-side checks can assess the request and the message itself, including unwanted sales pitches submitted with valid CAPTCHA tokens.
We build StaticForm, so the setup below describes our documented behaviour. It does not claim that one provider blocks a higher percentage of spam than another. Start with the spam protection guide for the complete configuration.
Compare the layers by their job
| Layer | What it contributes | What to consider |
|---|---|---|
| Honeypot form field | Flags a submission when a hidden trap field is filled | Bots can leave it empty. Match the configured field name and keep it out of keyboard navigation. |
| Cloudflare Turnstile | A provider token that StaticForm verifies before accepting the submission | Requires a site key in the page, a secret key in the dashboard and a working provider script. |
| hCaptcha | Another supported provider for token-based verification | Requires its own keys and widget. Test the visitor experience on your actual page. |
| Request header and IP checks | Assess whether a client-side request resembles browser traffic and comes from a known spam source | Command-line testing can be classified as spam. These checks are skipped where documented for server-side submission mode. |
| Content and repeated-sender checks | Assess message content and patterns across submissions | Legitimate enquiries can look unusual. Review classifications rather than assuming any filter is infallible. |
These layers answer different questions. Passing a CAPTCHA does not establish that a message is relevant to your business. A hidden field does not inspect the meaning of the message.
Honeypot: a small first step
In StaticForm, enable the honeypot in your form’s spam settings and choose its field name. The default is website_url. Add that exact name inside the form:
<div style="display: none;" aria-hidden="true">
<input type="text" name="website_url" tabindex="-1" autocomplete="off">
</div>
The field must remain empty for real visitors. Do not use a real website input with the same name: a genuine visitor filling it would trigger the trap. A honeypot offers no challenge for the visitor to solve, but a bot that understands hidden fields can avoid it.
Turnstile or hCaptcha: change the provider
StaticForm supports both Cloudflare Turnstile and hCaptcha, alongside reCAPTCHA v2, v3 and Enterprise. Choose one provider in the form settings and store its secret key there. Put only the public site key in your page.
With the JavaScript helper, place the provider’s widget inside the form. For Turnstile:
<div class="cf-turnstile" data-sitekey="YOUR_SITE_KEY"></div>
Set captcha: { type: 'turnstile' } in your existing StaticForm.attach call. For hCaptcha, use a widget with class="h-captcha" and set captcha: { type: 'hcaptcha' }. The helper loads the provider script and submits the form’s token as cf-turnstile-response or h-captcha-response, respectively. StaticForm rejects submissions with a missing or invalid token when CAPTCHA is enabled.
Use the JavaScript helper guide for the complete attachment code, widget handling and reset behaviour. Test with keys valid for the domain where the page is published.
Server-side checks: inspect more than a token
StaticForm automatically examines request headers and IP signals for client-side submissions. Allowed domains are a separate, optional control: enable it and list the sites where your form lives. Origin and Referer handling is described in the allowed-domain documentation. It is a spam signal, not a secret credential for authenticating your server.
Content checks assess unsolicited pitches and bot-shaped submissions. Repeated-sender checks use one-way hashes to detect documented patterns across forms. These are server-side behavioural signals; this guide does not imply that StaticForm records mouse movements or fingerprints visitors.
If you test a client-side form using curl or an automated client, an HTTP 200 does not establish that email delivery ran. The submission may be stored as spam, with email and webhook actions skipped. Test from a real browser and inspect the dashboard.
How to combine them in StaticForm
- Configure the fields and server-side validation for the data you actually need.
- Enable a honeypot and add its matching hidden field.
- If you want token verification, configure Turnstile, hCaptcha or a supported reCAPTCHA option on both the form and page.
- Optionally restrict allowed domains and expected languages when those constraints match your audience.
- Review the inbox and spam list after launch. Check why real messages were flagged before changing settings.
An optional AI second opinion reviews borderline submissions rather than every message. When enabled, it sends text fields to an external AI model; files, CAPTCHA tokens and the honeypot are excluded. You can exclude sensitive fields or disable the feature. Read what is sent before enabling it for your form.
Choose the smallest set of controls that fits your traffic and keep checking real enquiries. A successful setup preserves a usable contact form while giving you enough information to investigate unwanted messages and missed deliveries.