Matthias Pfefferle

Bernhard Kau

Pascal Birchler

Simon Kraft

pluginkollektiv

websupporter

Torsten Landsiedel

Florian Brinkmann

Alain Schlesser

<p>Say Goodbye to comment spam on your WordPress blog or website. <em>Antispam Bee</em> 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.</p>
<h3>Feature/Settings Overview</h3>
<ul>
<li>Trust approved commenters.</li>
<li>Trust commenters with a Gravatar.</li>
<li>Consider the comment time.</li>
<li>Allow comments only in a certain language.</li>
<li>Block or allow commenters from certain countries.</li>
<li>Treat BBCode links as spam.</li>
<li>Use regular expressions.</li>
<li>Search local spam database for commenters previously marked as spammers.</li>
<li>Notify admins by e-mail about incoming spam.</li>
<li>Delete existing spam after n days.</li>
<li>Limit approval to comments/pings (will delete other comment types).</li>
<li>Select spam indicators to send comments to deletion directly.</li>
<li>Optionally exclude trackbacks and pingbacks from spam detection.</li>
<li>Optionally spam-check comment forms on archive pages.</li>
<li>Display spam statistics on the dashboard, including daily updates of spam detection rate and a total of blocked spam comments.</li>
</ul>
<h3>Support</h3>
<ul>
<li>Community support via the <a href="https://wordpress.org/support/plugin/antispam-bee" rel="ugc">support forums on wordpress.org</a></li>
<li>Read <a href="https://antispambee.pluginkollektiv.org/documentation/" rel="nofollow ugc">the documentation</a></li>
<li>We don’t handle support via e-mail, Twitter, GitHub issues etc.</li>
</ul>
<h3>Contribute</h3>
<ul>
<li>Active development of this plugin is handled <a href="https://github.com/pluginkollektiv/antispam-bee" rel="nofollow ugc">on GitHub</a>.</li>
<li>Pull requests for documented bugs are highly appreciated.</li>
<li>If you think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the <a href="https://wordpress.org/support/plugin/antispam-bee" rel="ugc">support forums</a> first.</li>
<li>If you want to help us translate this plugin you can do so <a href="https://translate.wordpress.org/projects/wp-plugins/antispam-bee" rel="nofollow ugc">on WordPress Translate</a>.</li>
</ul>
<h3>Credits</h3>
<ul>
<li>Author: <a href="https://sergejmueller.github.io/" rel="nofollow ugc">Sergej Müller</a></li>
<li>Maintainers: <a href="https://pluginkollektiv.org" rel="nofollow ugc">pluginkollektiv</a></li>
</ul>


Antispam Bee


Using it since years and had no spam in my blog ever. Simple, clean, works.


Best Antispam Plugin


I've tested this plugin and seems to working very well. Most spam comments are gone, some of them (just a little) are able to avoid spam filters.



There is something need to be fixed and I'm already posted in support forum. I hope that it will be fixed soon.


Very good spam filter plugin.


Works quite well without calling out to a remote service, and doesn't require your visitors to be using JavaScript. (Seriously, I posted a test comment using Dillo and it showed up in the moderation queue!) No need to deal with API keys or licensing.



There are some optional tactics that will call a remote service for things like language identification, but so far it's doing the job fine without them!



The only problem I've had with it is that it only acts on comments, not on other features like contact forms.


Privacy-friendly spam filter

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

Matt Lowe

<p>Unspam by Squelch Design is the simplest <a href="http://squelchdesign.com/wordpress-plugin-squelch-unspam/" rel="nofollow ugc">WordPress anti-spam plugin</a> you can find for <strong>reducing your comment spam</strong> problem. Once installed there’s nothing<br />
to configure, and nothing changes to your visitors: No captcha or silly games. Once installed<br />
the plugin will simply randomize the names of the fields in the comments form on your blog and reject comments that are sent to the<br />
standard WordPress field names, or where bots have blindly submitted data to the honeypot fields.</p>
<p>What this means for spammers is that they have to do quite a lot more work to send spam to your website. It may also make sending<br />
spam to your website unreliable as changes to your theme may upset their spam submission tools. Or they may have to resort to using<br />
humans to send spam to your website (not much I can do about that I’m afraid) which will cost them more money.</p>
<p>Currently implemented:</p>
<ul>
<li>Names of fields are randomized every night at 12:00,</li>
<li>Submissions to the standard WordPress field names are automatically deleted,</li>
<li>Honeypot fields added to comments form,</li>
<li>WooCommerce support.</li>
</ul>
<p>Additional (planned) features:</p>
<ul>
<li>Contact Form 7 integration</li>
<li>Statistical collection,</li>
<li>Automated blocking of persistent IPs,</li>
<li>Opt-in centralized collection of comment spam and statistics for additional research.</li>
</ul>


Squelch Unspam

Unspam makes it harder for spammers to automatedly send spam to your blog by changing the names of the fields in the comment forms.

Antispam Bee vs Squelch Unspam