Stargazer

<h4>An easy and effective solution against Comment Spam</h4>
<p>WP-BlackCheck combines various ideas to protect your blog from spam.</p>
<h4>Fearures</h4>
<ul>
<li>Easy Installation</li>
<li>Block known spammers</li>
<li>Block Trackback/Pingback spam</li>
<li>No need to adjust default templates</li>
<li>Spam counter on the dashboard</li>
<li>Statistics</li>
</ul>
<h4>Languages</h4>
<ul>
<li>Albanian (thanks to Taulant Ceka – http://sem.al )</li>
<li>English</li>
<li>German</li>
<li>Slovakian (thanks to Black Cat Artworks – http://blackcatartworks.eu/ )</li>
</ul>
<p>If you want to see this plugin in your language, feel free to contact me or use <a href="https://www.transifex.net/projects/p/wpbc/resource/plugin/" rel="nofollow ugc">transifex.net</a> to contribute.</p>
<h4>Links</h4>
<ul>
<li><a href="http://my.stargazer.at/" title="Authors blog" rel="nofollow ugc">Blog</a></li>
<li><a href="http://bugs.stargazer.at/" title="Bugtracker" rel="nofollow ugc">Bugtracker</a></li>
<li><a href="http://www.twitter.com/ToeiRei" rel="nofollow ugc">Twitter</a></li>
</ul>
<h4>History</h4>
<p>Blocking spammers via htaccess or other server settings would do the job, but that would require<br />
to keep all the files in sync. So I decided to write a centralized solution that enables<br />
innocent users to remove their IP from the blacklist via removal request. As a blacklist gets queried<br />
way too often, I added some local detection of spammers to reduce load at my side.<br />
By now many additional features have been added, making this plugin a full grown anti-spam solution.</p>


WP-BlackCheck

WP-BlackCheck is an Anti-Spam Solution for Wordpress blocking spam using local detection and a centralized Blacklist Service.

apasionados

<p>Updates the “Comment Blacklist” in Settings / Discussion with a list terms from a remote or local source. By default it get’s the data from Github <strong>(“<a href="https://github.com/splorp/wordpress-comment-blacklist/" rel="nofollow ugc">wordpress-comment-blacklist</a>“)</strong> by <a href="https://github.com/splorp" rel="nofollow ugc">Grant Hutchinson</a>) but you can also get them <strong>from any URL</strong> or from a <strong>local blacklist.txt file</strong>.</p>
<p>This plugin is an enhanced version of the plugin <a href="https://wordpress.org/plugins/comment-blacklist-manager/" rel="ugc">Comment Blacklist Manager</a>. We decided to create this enhanced version of the plugin, because we wanted to be able to add blacklists without using filters and directly from the WordPress administration. You can still use a filter to modify the blacklist sources if that is more convienient for you. And we also wanted to have more information about the plugin in SETTINGS / DISCUSSION; for example when the blacklist was updated and when it will be updated next time, when the blacklist sources were updated, etc.</p>
<p>You can configure three sources for your blacklists:</p>
<ol>
<li><strong>Default blacklist</strong> (which can be disabled): <a href="https://github.com/splorp/wordpress-comment-blacklist/" rel="nofollow ugc">wordpress-comment-blacklist</a> by <a href="https://github.com/splorp" rel="nofollow ugc">Grant Hutchinson</a>). Please keep in mind that if there is no other blacklist source defined, this will be used as default, even if it\’s not selected.</li>
<li><strong>Blacklist from remote URL</strong>: You paste the URL to the blacklist and if the file exists and can be accesed (must return code 200) it will be used as a blacklist source.</li>
<li>If you want to include a <strong>local blacklist</strong> for the site, you can upload a blacklist.txt file to the UPLOADS folder and it will also be taken into account. The blacklist.txt file has to be in the root of the UPLOADS folder; it will not be recognized if it\’s for example in /uploads/2025/12/ and the file has to be accesible via http/https (if the access to the file is protected it can\’t be used).</li>
</ol>
<p>And you can use the filter <code>cblm_sources</code> to replace all the blacklists or to add more. If you replace all blacklists with the filter, the settings done in the WordPress administration will be ignored. We decided to keep the same filter as used by “Comment Blacklist Manager” to make it easy to switch between both plugins.</p>
<blockquote>
<p>Please note: <strong>After the September 2023 update only users with administrator privileges can use this plugin.</strong> If you’re not an admin you will get following error: “You do not have sufficient permissions to access this page”.</p>
</blockquote>
<h4>What can I do with this plugin?</h4>
<p>The plugin updates the “Comment Blacklist” in Settings / Discussion with a list terms from a remote or local source. By default it get’s the data from Github (“<a href="https://github.com/splorp/wordpress-comment-blacklist/" rel="nofollow ugc">wordpress-comment-blacklist</a> by <a href="https://github.com/splorp" rel="nofollow ugc">Grant Hutchinson</a>) but you can also get them from any URL or from a local blacklist.txt file.</p>
<h4>Why do I want to update the “Comment Blacklist” in Settings / Discussion?</h4>
<p>If you want to reduce spam received in your comment forms but also in your contact forms (for example when using Contact Form 7), using blacklisted terms can help.</p>
<p>Contact Form 7 encourages to use: Akismet, reCaptcha and the comment blacklist to reduce contact form spam.</p>
<blockquote>
<p><em>Contact Form 7 supports spam-filtering with Akismet. Intelligent reCAPTCHA blocks annoying spambots. Plus, using comment blacklist, you can block messages containing specified keywords or those sent from specified IP addresses.</em></p>
</blockquote>
<p>The best way to reduce the contact form 7 spam is to use a very extensive term database which is updated regulary with new spam terms. And this plugin does exactly this: Updating the blacklist regularly.</p>
<h4>Why are you using the “Comment Blacklist for WordPress” from Grant Hutchinson as default source for the blacklist?</h4>
<p>Since 2011 Grant Hutchinson has been identifying and compiling over 34,000 phrases, patterns, and keywords commonly used by spammers and comment bots in usernames, email addresses, link text, and URIs.</p>
<p>His blacklist is very extensive and that’s why we love it.</p>
<p>As with all compilations, this blacklist is a work in progress and it is updated more or less every month. And each of these updates will be included automatically with the update process that runs every 24 hours.</p>
<p><em>Sometimes simple is better.</em></p>
<p><strong>If you know another source that is as extensive as this one, drop us a message and we will check if it’s interesting to add it also as a default.</strong></p>
<h4>System requirements</h4>
<p>PHP version 5.6 or greater.</p>
<h4>Comment Blacklist Updater Plugin in your Language!</h4>
<p>This first release is avaliable in English and Spanish. In the “languages” folder we have included the necessary files to translate this plugin.</p>
<p>If you would like the plugin in your language and you’re good at translating, please drop us a line at <a href="https://apasionados.es/contacto/index.php?desde=wordpress-org-apa-comment-blacklist-updater-home" rel="nofollow ugc">Contact us</a>.</p>
<h4>Further Reading</h4>
<p>You can access the description of the plugin in Spanish at: <a href="https://apasionados.es/blog/" rel="nofollow ugc">Actualizador lista negra de comentarios | WordPress Plugin</a>.</p>
<h3>Contact</h3>
<p>For further information please send us an <a href="https://apasionados.es/contacto/index.php?desde=wordpress-org-apa-comment-blacklist-updater" rel="nofollow ugc">email</a>.</p>


Comment Blacklist Updater

Update "Comment Blacklist" spam terms to manage spam in forms and comments

WP-BlackCheck vs Comment Blacklist Updater