Aiformleads discards spam submissions on the server, before they reach your leads inbox: invisible honeypot field, Google reCAPTCHA v3 or hCaptcha, IP submission window, duplicates, and disposable email domains.
A form published on the internet will receive bots: it's a matter of days. If you don't filter them, you end up paying your team's time to manually clean an inbox full of fake submissions.
Aiformleads—AIsToHire's lead generation tool—brings anti-spam protection within the product: there's no need to install a plugin or contract a separate service. Each form has its security tab, where you decide which filters submissions must pass before becoming a lead.
The five controls are evaluated on the server, in the operation that closes the form, and in this order: filled honeypot field, email format, disposable email domain, IP submission limit, captcha, and finally, duplicate email. The first one that fails stops the submission and returns a message; the lead is not saved. A bot ignoring the page's JavaScript is useless, because the checks are not in the browser: they are behind the API.
The honeypot is a text field that travels in all public forms, placed off-screen and marked as hidden for screen readers: it's neither visible, nor tabbable, nor does it autocomplete. A person cannot fill it; a bot that traverses the HTML can. As soon as it arrives with content, the submission is rejected with a generic message that doesn't tell the bot why it failed.
The captcha is optional and uses your own keys: you choose Google reCAPTCHA v3 or hCaptcha, paste the site key and the secret key, and for reCAPTCHA v3, you set the minimum score you accept (0.5 by default). The public page loads the provider's script only if captcha is configured, and the token is verified from the server against the provider. Your secret key never goes to the browser: the public form configuration only exposes the provider and the site key.
You can see this functionality in context on the Aiformleads page at AIsToHire: https://aistohire.com/aiformleads-forms-lead-capture-108
Invisible honeypot, active without any configuration
The honeypot field travels in the public form positioned off-screen, with aria-hidden and no tab order, so no person sees it or fills it by mistake. If the submission arrives with that field filled, the server discards it and the lead is not created.
Google reCAPTCHA v3 or hCaptcha, with your keys
You choose the provider from a dropdown and paste your site key and secret key. The provider’s script is loaded only on forms with captcha configured, and the token is checked from the server against Google’s or hCaptcha’s verification API.
Adjustable minimum score with no visitor friction
reCAPTCHA v3 doesn’t show puzzles: it returns a score. You decide the acceptable threshold, between 0 and 1, and submissions below it are rejected. If the provider doesn’t respond or no secret key is saved, the form continues to function instead of getting blocked.
Submission limit per IP, with a sliding window
You activate the limit and set how many submissions you allow and how often (in minutes). The count is per form and IP address: once the maximum is reached, subsequent attempts are rejected until the window advances and new submissions are allowed.
Rejected disposable email domains
Submissions with emails from mailinator, guerrillamail, yopmail, 10minutemail, tempmail, trashmail, getnada, or sharklasers are blocked. The check is twofold: the email field performs it as the person types, and the server repeats it upon submission. You can disable it per form or per field if you prefer to accept them.
Duplicates
block, mark, or allow: You decide what happens when an email has already submitted the form: block the submission, accept it by marking it as a duplicate so you see it in the leads inbox, or ignore it. And you can set a time window in days, so repeating after three months doesn’t count as a duplicate.
Everything on the server, nothing trusted to the browser
Honeypot, disposable email, IP limit, captcha, and duplicate checks are evaluated in the same operation that finalizes the form submission. A script that posts directly to the API goes through exactly the same filters as someone filling out the form on screen.
Configurable per form, not for the entire account
Protection resides within each form. You can leave the contact form open with only the honeypot and add captcha, IP limit, and duplicate blocking to the campaign you are promoting with advertising.

Create your form in Aiformleads, activate the honeypot, captcha, and IP limit from its security tab, and receive only valuable leads in your inbox.