Antispam Bee


Say Goodbye to comment spam on your WordPress blog or website. Antispam Bee blocks spam comments and trackbacks effectively, without captchas and without sending personal information to third party services. It is free of charge, ad-free and 100% GDPR compliant.

Feature/Settings Overview

  • Trust approved commenters.
  • Trust commenters with a Gravatar.
  • Consider the comment time.
  • Allow comments only in a certain language.
  • Block or allow commenters from certain countries.
  • Treat BBCode as spam.
  • Validate the IP address of commenters.
  • Use regular expressions.
  • Search local spam database for commenters previously marked as spammers.
  • Notify admins by e-mail about incoming spam.
  • Delete existing spam after n days.
  • Limit approval to comments/pings (will delete other comment types).
  • Select spam indicators to send comments to deletion directly.
  • Optionally exclude trackbacks and pingbacks from spam detection.
  • Optionally spam-check comment forms on archive pages.
  • Display spam statistics on the dashboard, including daily updates of spam detection rate and a total of blocked spam comments.



  • Le développement actif de cette extension est géré sur GitHub.
  • Les demandes d’extraction de bogues documentés sont très appréciées.
  • If you think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the support forums first.
  • Si vous souhaitez nous aider à traduire cette extension, vous pouvez le faire sur WordPress Translate.


Captures d’écran

  • Réglages Antispam Bee


  • If you don’t know how to install a plugin for WordPress, here’s how.


  • PHP 5.2.4 ou supérieure
  • WordPress 4.5 ou supérieur


After you have activated Antispam Bee the plugin will block spam comments out of the box. However, you may want to visit Settings → Antispam Bee to configure your custom set of anti-spam options that works best for your site.


Does Antispam Bee work with Jetpack, Disqus Comments and other comment plugins?

Antispam Bee works best with default WordPress comments. It is not compatible with Jetpack or Disqus Comments as those plugins load the comment form within an iframe. Thus Antispam Bee can not access the comment form directly.
It also won’t work with any AJAX-powered comment forms.

L’extension Antispam Bee stocke-t-elle des données privées de l’utilisateur et est-elle conforme au RGPD ?

Antispam Bee est développé en Europe. Vous avez peut-être entendu dire que nous pouvons être un peu pointilleux ici en matière de confidentialité. L’extension ne stocke pas les données des utilisateurs privés et est 100 % conforme au RGPD.

Will I have to edit any theme templates to get Antispam Bee to work?

No, the plugin works as is. You may want to configure your favorite settings, though.

Antispam Bee fonctionne-t-il avec les IP raccourcies ?

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.

Comment puis-je envoyer un indésirable non détecté ?

If the antispam plugin has passed some spam comments, these comments can be reported for analysis. A Google table was created for this purpose.

Antispam Bee avec Varnish ?

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;

Existe-t-il des services payants ou des limitations ?

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.

La documentation complète est disponible sur [](


17 juin 2020
We've tested it for 4 weeks on multiple shops and the spam was reduced over 95%! We now install it on all our client sites. Thank you so much for this plugin!
29 avril 2020
This plugin was good enough to protect all my sites for years.
11 avril 2020
I've been using the plugin for months successfully. Just recently I had some new, weird spam get through. But after reading a couple of support forum threads, I was able to find a solution. Just wanted to say "thanks" for this valuable plugin!
2 mars 2020
It's a great plugin, its pretty good at filteren spam comments even though it have caught some real comments a few times. The best part is that it doesn't require any data sharing, I'm getting really tired of all the data collection everywhere 🙂 Thanks for the plugin
Lire les 168 avis

Contributeurs & développeurs

« Antispam Bee » est un logiciel libre. Les personnes suivantes ont contribué à cette extension.


“Antispam Bee” a été traduit dans 23 locales. Remerciez l’équipe de traduction pour ses contributions.

Traduisez « Antispam Bee » dans votre langue.

Le développement vous intéresse ?

Parcourir le code, consulter le SVN dépôt, ou s’inscrire au journal de développement par RSS.



  • English
    • Fix: Delete comment meta for deleted old spam. For the cleanup of older orphaned comment meta we suggest the usage of WP Sweep
    • Fix: Statistic in dashboard showed wrong value
    • Tweak: Change autocomplete attribute to « new-password »
    • Tweak: Autoptimize compatibility improved
    • Tweak: Renamed blacklist/whitelist to a better phrase
    • Tweak: Added new pattern
    • Tweak: UI and text optimizations
    • Tweak: Better compatibility with some server configurations
    • Tweak: Make spam reason sortable and filterable
    • Tweak: Add spam reason for manually marked spam
    • Maintenance: Deleted unused code
    • Maintenance: Removed Fake IP check (unreliable and producing false positives)
    • Maintenance: Fix some coding standard issues
    • Maintenance: Tested up to WordPress 5.4
    • Maintenance: Tested up to PHP 7.4


  • Improved backend accessibility
  • Prefilled comment textareas do now work with the honeypot
  • Compatible with the AMP plugin (
  • Improved dashboard tooltips
  • Improvements for the language detection API
  • Scalable IP look up for local spam database


  • Introduction of coding standards.
  • Switch to franc language detection API for the language check.
  • Do not longer overwrite the IP address WordPress saves with the comment by using pre_comment_user_ip.
  • Do not show « Trust commenters with a Gravatar » if the « Show Gravatar » option is not set.
  • Skip the checks, when I ping myself.
  • Fixes some wrong usages of the translation functions.
  • Use the regular expressions check also for trackbacks.
  • Add option to delete Antispam Bee related data when plugin gets deleted via the admin interface.
  • Save a hashed + salted IP for every comment
  • New check for incoming trackbacks.
  • Introduction of behat tests.
  • Updates the used JavaScript library for the statistics widget.
  • Bugfix in the « Comment form used outside of posts » option.


  • PHP 5.3 compatibility
  • Bugfix where a spam trackback produced a fatal error
  • For more details see


  • Removed to avoid potential GDPR violation
  • Improves IP handling to comply with GDPR
  • Improves PHP7.2 compatibility
  • Fixes small bug on mobile views
  • Allow more than one language in language check
  • Minor interface improvements
  • Remove old russian and Dutch translation files
  • For more details see


  • Fixes an incompatibility with Chrome autofill
  • Fixes some incompatibilities with other plugins/themes where the comment field was left empty
  • Support for RTL
  • Solve some translation/language issues
  • A new filter to add languages to the language check
  • For more details see


  • Country check is back again (thanks to Sergej Müller for his amazing work and the service page)
  • Improved Honeypot
  • Language check through Google Translate API is back again (thanks to Simon Kraft of for offering to cover the costs)
  • More default Regexes
  • Unit Test Framework
  • Accessibility and GUI improvements
  • An english documentation is now available, too. Some corrections in the german documentation.
  • Some bugfixes – Among other things for WPML compatibility
  • For more details see


  • Updates donation links throughout the plugin
  • Fixes an error were JavaScript on the dashboard was erroneously being enqueued
  • Ensures compatibility with the latest WordPress version


  • added a POT file
  • updated German translation, added formal version
  • updated plugin text domain to include a dash instead of an underscore
  • updated, translated + formatted
  • updated expired link URLs in plugin and languages files
  • updated plugin authors


  • Removal of functions Block comments from specific countries and Allow comments only in certain language for financial reasons – more information


  • Switch to the official Google Translation API
  • Release time investment (Development & QA): 2.5 h


  • Fix: Return parameters on dashboard_glance_items callback / thx @toscho
  • New function: Trust commenters with a Gravatar / thx @glueckpress
  • Additional plausibility checks and filters
  • Release time investment (Development & QA): 12 h


  • Consideration of the comment time (Spam if a comment was written in less than 5 seconds) – more information
  • Release time investment (Development & QA): 6.25 h


  • Sorting for the Antispam Bee column in the spam comments overview
  • Code refactoring around the use of REQUEST_URI
  • Release time investment (Development & QA): 2.75 h


  • Improving detection of fake IPs
  • Release time investment (Development & QA): 11 h


  • Code refactoring of options management
  • Support for HTTP_FORWARDED_FOR header
  • Release time investment (Development & QA): 8.5 h


  • Optimizations for WordPress 3.8
  • Clear invalid UTF-8 characters in comment fields
  • Spam reason as a column in the table with spam comments

For the complete changelog, check out our GitHub repository.