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.

tornevall

<p>Tornevall Networks DNSBL and FraudBL protection for WordPress. The plugin helps block comment activity, account registrations and other unwanted submissions from addresses flagged by Tornevall Networks DNSBL and FraudBL.</p>
<p>FraudBL is part of the protection layer used by the plugin and is available at <a href="https://www.fraudbl.org/" rel="nofollow ugc">fraudbl.org</a>. For general discovery, broader search terms like fraud, blacklist, comment spam and user registration are usually easier to find than niche technical acronyms alone.</p>
<p>The plugin is intended to provide a lightweight anti-spam and anti-abuse layer for WordPress, with support for local caching to reduce repeated lookups and unnecessary load against blacklist services.</p>
<p>Current admin features include manual DNS lookup tools, self-check tools, visitor statistics, safe IP whitelisting, frontend dry-run support for administrators, Cloudflare Turnstile for comments, and DNSBL plus Turnstile protection for new WordPress account registrations. Tools integration now uses one visible DNSBL / Tools API token field in the plugin UI. The live <strong>Check token permissions</strong> flow always asks Tools directly, warns clearly when the token exists on the other Tools environment (<code>tools.tornevall.com</code> vs <code>tools.tornevall.net</code>), and reports the effective DNSBL permissions for the configured token. Active admin-owned Tools tokens are shown as having automatic DNSBL access through the same <code>X-Dnsbl-Token</code> transport. The plugin now also warns on the WordPress dashboard and settings page when the current token cannot perform live delete / delist operations yet, with a direct link to the active Tools access page. The token status area shows current add/delete/update capability instead of only saying that a token exists, and delisting-page controls stay read-only until delete / delist permission has been confirmed. Internal delist slug routing now uses a dedicated rewrite/query-var path and refreshes rewrite rules on activation and slug changes to avoid <code>/delist</code> 404 cases. The managed public delist page now runs as a checker-style IP-only flow (checks listing first, then submits delist), while custom shortcode pages still support the broader permission-aware operations. The plugin also ships a shortcode delisting/removal form (<code>[dnsbl_removal_form]</code>) with AJAX backend proxy and optional API dry-run acknowledgement, plus a built-in primary removal-page template that is only activated when the configured token has live delete permission.</p>
<p>Report issues and feedback: <a href="https://github.com/Tornevall/tornevall-wp-dnsbl/issues" rel="nofollow ugc">GitHub issues</a><br />
Plugin URL: <a href="https://wordpress.org/plugins/tornevall-networks-dnsbl-implementation/" rel="ugc">WordPress.org plugin page</a><br />
Documentation: <a href="https://tools.tornevall.net/docs/dnsbl-api" rel="nofollow ugc">DNSBL API documentation</a></p>
<h4>Support and feedback</h4>
<p>Bug reports and feedback can currently be submitted via <a href="https://github.com/Tornevall/tornevall-wp-dnsbl/issues" rel="nofollow ugc">GitHub issues</a>.</p>
<p>Full Documentation: <a href="https://tools.tornevall.net/docs/dnsbl-api" rel="nofollow ugc">DNSBL API documentation</a></p>
<p>Translations can be contributed via <a href="https://translate.wordpress.org/projects/wp-plugins/tornevall-networks-dnsbl-implementation" rel="nofollow ugc">translate.wordpress.org</a>.</p>


Tornevall Networks DNSBL Implementation

Tornevall Networks DNSBL implementation with FraudBL support for WordPress

WP-BlackCheck vs Tornevall Networks DNSBL Implementation