Antispam Bee
by pluginkollektiv 4.8 (226 reviews)

Antispam Bee

Sophisticated antispam plugin for effective daily comment and trackback spam-fighting. Built with data protection and privacy in mind.

Antispam Bee ranks #84 among WordPress.org plugins with 700,000+ active installations, is #6 of 2,878 in the Discussion & Community category, a 4.8/5 rating from 226 reviews, and was last updated Aug 23, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v2.11.13 Current Version v2.11.13
Updated 3 weeks ago Last Update on 23 Aug, 2026
Refreshed 11 hours ago Last Refreshed on
#6 of 2,878 in Discussion & Community Top 1% by installs Downloads -40.7% this week Actively maintained
View on WordPress.org
Rank
#84
No change
Active Installs
700K+
-10.3%
KW Avg Position
10.4
No change
Downloads
11M
+3,310 today
Support Resolved
0%
No change
Rating
96%
Review 4.8 out of 5
4.8 (226 reviews)

Next Milestone 800K

Total Progress 75%
700K+ 800K+
2
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 25,000 more installs to reach 800K+

Rank Changes

64 74 84 94 104 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026
64 74 84 94 104 31-08-2026 01-09-2026 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026
Current #84
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

2.5K 3K 3.5K 4K 4.5K 5K 5.5K 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026
2K 4K 6K 8K 10K 31-08-2026 01-09-2026 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

4.8
226 reviews
Overall 96%
5
213 (94%)
4
2 (1%)
3
1 (0%)
2
2 (1%)
1
8 (4%)

Support Threads Overview

Resolved
Unresolved
2
Total Threads
0
Resolved
2
Unresolved
0%
Resolution Rate

Security History

Source: WPVulnerability

1 known vulnerability on record · 0 in the last 24 months · checked 1 week ago

  1. Antispam Bee [antispam-bee] < 2.11.4

    CVE-2023-41134 · Fixed in v2.11.4

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress site owners and administrators who want to stop comment and trackback spam. It filters spam without CAPTCHAs and without sending personal data to third-party services, keeping the process GDPR compliant.

  • Trust approved commenters
  • Trust Gravatar commenters
  • Consider comment time
  • Language-based comment filtering
  • Country-based blocking or allowing
  • Treat BBCode links as spam
  • Local spam database search
  • Dashboard spam statistics

Frequently Asked Questions

Common questions about Antispam Bee

Antispam Bee works best with default WordPress comments. It does not help to protect form plugins and does not prevent spam registrations. Hopefully we can provide better hooks for third party plugins to use Antispam Bee to fill this gap in the forthcoming new major version.
Antispam Bee works best with default WordPress comments. It is not compatible with Jetpack, wpDiscuz or Disqus Comments as those plugins load a new comment form within an iframe. Thus Antispam Bee can not access the comment form directly.
Whether Antispam Bee works with a comment form submitted via AJAX depends on how the AJAX request is made. If the request goes to the file that usually also receives the comments, Antispam Bee could work with it out of the box (the WP Ajaxify Comments plugin does this, for example). If the comments are sent to the admin-ajax.php, the antispam_bee_disallow_ajax_calls filter must be used to run ASB for requests to that file as well. If the script does not send all form data to the file, but only some selected ones, further customization is probably necessary, as exemplified in this post by Torsten Landsiedel (in German).
Antispam Bee hides its honeypot field with inline styles. If your site sends a Content Security Policy that does not allow inline styles (a style-src directive without 'unsafe-inline'), the browser drops those styles and the field becomes visible to your visitors. Use the antispam_bee_honeypot_styles filter to return an empty string, so no inline styles are rendered at all: add_filter( 'antispam_bee_honeypot_styles', '__return_empty_string' ); Then hide the field from your own stylesheet, which your policy already allows: textarea[aria-label="hp-comment"] { padding: 0 !important; clip: rect(1px, 1px, 1px, 1px) !important; position: absolute !important; white-space: nowrap !important; height: 1px !important; width: 1px !important; overflow: hidden !important; } The same filter can also be used to return a modified set of styles instead of an empty one. Do not hide the field with display: none or visibility: hidden, as many spam bots skip fields hidden that way, which is exactly what the honeypot needs them not to do.
Antispam Bee is developed in Europe. You might have heard we can be a bit nitpicky over here when it comes to privacy. The plugin does not save private user data and is 100% compliant with GDPR.
No, the plugin works as is. You may want to configure your favorite settings, though.
Generally yes. However, commissioning the Antispam Bee plugin for canceled or shortened IP addresses in comment metadata is not recommended. Because the name and the e-mail address of the comments are not unique, an IP address is the only reliable measure. The more complete the stored IP addresses, the more reliable the assignment or detection of spam.
If the antispam plugin has passed some spam comments, these comments can be reported for analysis. A Google table was created for this purpose.
If WordPress is operated with Apache + Varnish, the actual IP address of the visitors does not appear in WordPress. Accordingly the Antispam-Plugin lacks the base for the correct functionality. An adaptation in the Varnish configuration file /etc/varnish/default.vcl provides a remedy and forwards the original (not from Apache) IP address in the HTTP header X-Forwarded-For: if (req.restarts == 0) { set req.http.X-Forwarded-For = client.ip; }
No, Antispam Bee is free forever, for both private and commercial projects. You can use it on as many sites as you want. There is no limitation to the number of sites you use the plugin on. A complete documentation is available on pluginkollektiv.org.

More plugins by pluginkollektiv

Sign In / Register

You need to sign in or register to use this feature.