CleanTalk Spam Protection
CAPTCHA-free cloud anti-spam for comments, registrations, WooCommerce and 100+ form plugins, with a firewall for known bots. From $12/year.
Free, privacy-focused comment and trackback spam filter that runs on your own server with no CAPTCHA, account or API key.
Antispam Bee is a free, open-source plugin maintained by the German volunteer group pluginkollektiv. It focuses on one job, stopping spam in WordPress comments, pingbacks and trackbacks, and it does that without CAPTCHAs, without an account and without sending commenter data to a third-party spam database. That makes it a popular choice for European sites that want to keep GDPR paperwork simple.
Out of the box it adds a hidden honeypot to the comment form and checks how quickly a comment was submitted. You can then switch on further rules: trust commenters with an approved comment or a Gravatar, treat BBCode links as spam, match regular expressions, compare against your own local database of past spam, and allow comments only in certain languages or from certain countries. Each blocked comment records a spam reason, and you can choose to delete spam for specific reasons straight away or clear the spam folder after a set number of days.
Privacy is the standout strength. The core checks run locally. The optional country check sends a shortened IP to iplocate.io, the language check sends only the comment text, and the Gravatar check sends a hash of the email address, so you can leave those off if you want nothing to leave your server. There is no paid tier, no site limit and no upsell.
The limits are just as clear. The developers say it does not protect form plugins or stop spam registrations, it does not cover login or WooCommerce checkout, and it cannot reach comment systems that load in an iframe such as Jetpack Comments or Disqus. Sites behind a proxy also need to pass the real visitor IP for the country check to work.
Choose Antispam Bee for blogs and content sites that mainly suffer from comment spam and want a free, self-hosted filter. Pair it with a CAPTCHA or form-level anti-spam plugin if you also need to protect registrations, logins or contact forms.
Best for: Blogs and EU-based content sites that want free, self-hosted comment spam filtering without sending data to a spam service.
Antispam Bee is an excellent free comment filter with a strong privacy story and sensible, configurable rules. Its scope is narrow, though, so anyone needing to protect forms, logins or registrations will need another plugin alongside it.
What Antispam Bee highlights on its WordPress.org page and its own website, split by version.
11 of 46 features we track in CAPTCHA & Spam, feature score 25/100
Supports Google reCAPTCHA (v2 checkbox, invisible or v3 score-based).
No CAPTCHA providers; filters comments without challenges.
Supports Cloudflare Turnstile, the privacy-friendly CAPTCHA alternative.
No Cloudflare Turnstile support.
Supports hCaptcha challenges.
No hCaptcha support.
Own image, math or puzzle CAPTCHA with no third-party service.
No image or math CAPTCHA.
Hidden fields and timing checks that catch bots without a visible challenge.
Hidden honeypot field plus a check on how fast the comment was submitted.
Submissions checked against a cloud spam database of known spammers.
Uses a local database of your own past spam, not a shared cloud database.
Blocks bots without asking visitors to solve anything.
Blocks spam without any visible challenge to commenters.
Protects WordPress comments from spam.
Core purpose: comment, pingback and trackback spam filtering.
Protects the login and lost-password forms.
Login forms are outside its scope.
Protects the user registration form.
FAQ states it does not prevent spam registrations.
Protects WooCommerce checkout, login and registration forms.
No WooCommerce checkout, login or registration protection.
Works with popular form plugins such as Contact Form 7, WPForms or Gravity Forms.
FAQ states it does not protect form plugins.
Protects forms built in Elementor, Divi or similar builders.
Builder forms are not covered.
Protects BuddyPress, bbPress, Ultimate Member or similar.
Limited to WordPress comments; no forum or community plugin support documented.
Block or allow specific IPs, emails, words or user roles.
Regex rules, local spam database and trusted-commenter options, but no plain IP/email list UI.
Block submissions by country or language.
Allow or block countries and restrict comments to chosen languages.
Log of blocked submissions with counts and reasons.
Spam reasons per comment, dashboard stats and an optional log file for Fail2Ban.
Hide the challenge for logged-in or trusted users.
Change challenge text, errors, theme or language.
No visitor-facing challenge or message to customise.
No tracking cookies, data minimisation or a documented GDPR mode.
No cookies and no personal data stored; developers describe it as GDPR compliant.
Core protection runs entirely on your own server.
Core checks run locally; only optional country, language and Gravatar checks call outside.
CAPTCHA scripts are only loaded on pages that have a protected form.
No front-end scripts at all; plugin scripts load only in the admin dashboard.
Works across a WordPress multisite network.
Protects Contact Form 7 forms.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects WPForms forms.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects Gravity Forms forms.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects Elementor Pro form widgets.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects Ninja Forms forms.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects Formidable Forms forms.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects Fluent Forms forms.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects Forminator forms.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects Divi contact form modules.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects EDD checkout, login or registration.
Only checks WordPress comments; no checkout, login or registration protection.
Protects BuddyPress registration and activity.
Only checks WordPress comments and does not prevent spam registrations.
Protects bbPress topics and replies.
Only checks WordPress comments; bbPress topics and replies are not covered.
Protects Ultimate Member login and registration.
Does not prevent spam registrations, so Ultimate Member forms are not covered.
Protects MemberPress signup and login.
Does not prevent spam registrations, so MemberPress signups are not covered.
Protects MC4WP newsletter sign-up forms.
FAQ says it does not protect form plugins; it only checks WordPress comments.
Protects wpDiscuz comment forms.
FAQ says it is not compatible with wpDiscuz, which loads its own comment form.
Protect any custom form via shortcode, function or hooks.
No API for custom forms; only a filter to run on AJAX comment requests.
Blocks known spam bots before pages load.
No firewall; it only filters comments and trackbacks as they are submitted.
Rejects throwaway or fake email addresses.
No disposable email check among its spam filters.
Stops bots testing stolen cards at WooCommerce checkout.
No WooCommerce checkout protection.
Blocks spam or abuse through the REST API or XML-RPC.
Checks incoming pingbacks (via XML-RPC) and trackbacks; no wider REST or XML-RPC blocking.
Review blocked submissions and approve false positives.
'Mark as spam, do not delete' keeps spam in the Spam folder with the reason for review.
Test keys, debug logs or a test mode to check setup safely.
On WordPress.org
Unlimited
Free for personal and commercial sites with no site limit.
Prices are list prices from the vendor's site, checked 14 Oct 2026. Many vendors discount the first year.
Free installs from WordPress.org, the vendor's own claim, and our estimate of paid installs.
Active installations reported by WordPress.org.
The vendor does not publish a total.
There is no paid version.
16,933 downloads last week, 13.2M all time
| Version | 2.11.13 |
|---|---|
| Last updated | 23 Aug 2026 (72 days ago) |
| Tested up to | WordPress 7.1.4 |
| Requires | WordPress 4.6+, PHP 5.2+ |
| Support threads (2 months) | 0 of 2 resolved |
| On WordPress.org since | 10 Jan 2009 |
CAPTCHA-free cloud anti-spam for comments, registrations, WooCommerce and 100+ form plugins, with a firewall for known bots. From $12/year.
Free plugin that adds hCaptcha to WordPress core, WooCommerce and 60+ form, builder and community plugins, with honeypot and IP controls.
WebFactory's free CAPTCHA and login-protection plugin with reCAPTCHA and a built-in math CAPTCHA; WP Captcha PRO adds hCaptcha, Turnstile and a firewall.
Free plugin that adds Cloudflare Turnstile CAPTCHA to WordPress, WooCommerce and 30+ form, membership and community plugins.
Honeypot anti-spam plugin that blocks bots on comments and many form plugins with no CAPTCHA, API key or external calls; Extended adds…
Freemium CAPTCHA plugin: free reCAPTCHA for core WordPress forms; Premium adds hCaptcha, Turnstile, WooCommerce, form plugins and geoblocking.
Yes. Antispam Bee has a free version on WordPress.org.
WordPress.org reports 700K+ active installations of the free version.
No: not included. No CAPTCHA providers; filters comments without challenges.
No: not included. No Cloudflare Turnstile support.
No: not included. Uses a local database of your own past spam, not a shared cloud database.
Yes: included. Core purpose: comment, pingback and trackback spam filtering.
No: not included. Login forms are outside its scope.
No: not included. No WooCommerce checkout, login or registration protection.
No: not included. FAQ states it does not protect form plugins.
No: not included. FAQ says it does not protect form plugins; it only checks WordPress comments.
Yes. It is free for personal and commercial projects on any number of sites, with no paid version.
No. The developers state it works best with default WordPress comments and does not protect form plugins or stop spam registrations.
The core checks are local. Optional country, language and Gravatar checks contact external services with a shortened IP, the comment text or an email hash respectively.
No. Those load the comment form in an iframe, so Antispam Bee cannot see or protect it.
Last updated 6 Oct 2026. Spotted something wrong? Suggest an edit.