Tornevall Networks DNSBL Implementation
Tornevall Networks DNSBL implementation with FraudBL support for WordPress
Use with caution
Tornevall Networks DNSBL Implem… works, but test it on a staging site before relying on it in 2026. It runs on 10+ sites and was last updated 3 months ago, and scores 57/100 on our health check.
- Small user base (10+ active installs)
- Very few reviews so far
- Needs PHP 8.1 or newer
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Tornevall Networks DNSBL Im… stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| antispam | #78 |
| blacklist | >100 |
| comment spam | >100 |
| fraud | >100 |
| User Registration | >100 |
Version adoption
Share of active sites per release.
About Tornevall Networks DNSBL Implementation
From the official readme · v3.1.5Description
Protect your WordPress site against comment spam, abusive registrations, and other unwanted submissions with Tornevall Networks DNSBL and FraudBL.
The plugin is built to give site owners a practical anti-abuse layer without turning everyday moderation into a maintenance project..
Report issues and feedback: GitHub issues
Plugin URL: WordPress.org plugin page
Documentation: DNSBL API documentation
Support and feedback
Bug reports and feedback can currently be submitted via GitHub issues.
Full Documentation: DNSBL API documentation
Translations can be contributed via translate.wordpress.org.
Installation
- Upload the plugin archive to the
/wp-content/plugins/directory - Activate the plugin through the ‘Plugins’ menu in WordPress
- Configure the plugin via admin control panel
The installation creates a cache table in the WordPress database. This reduces repeated DNS lookups and helps avoid unnecessary load against blacklist services. Both blacklisted and non-listed lookups are cached. The default cache lifetime is 600 seconds and the cleanup interval is 300 seconds.
The plugin also supports a safe IP whitelist. Whitelisted IP addresses are still checked and can appear in statistics, but they are not blocked, redirected or marked as spam. When possible, the activating visitor IP is seeded into that whitelist automatically during first-time setup.
If the database schema becomes out of sync after an upgrade or a manual source-based install, deactivate and reactivate the plugin to recreate the required tables.
Changelog
Fixes the multisite/network wp-signup.php step-two registration flow so Turnstile no longer breaks the second step after a successful first-step check.
3.1.5
- Fixed WordPress multisite/network registrations so the second
wp-signup.phpstep can reuse the successful Turnstile check from step 1 instead of failing and sending the visitor back to the first step.
3.1.4
- Tested with WP7.
- Registration Turnstile and DNSBL/FraudBL checks now also protect WordPress multisite/network signups on
wp-signup.php.
3.1.3
- Tested with WP7.
3.1.2
- Fixed the public removal-form Turnstile lifecycle so the widget waits for Cloudflare’s API before rendering, keeps the returned widget id, and uses that widget id for reset/response handling.
- Fixed stale or empty Turnstile response handling by clearing tokens on expiration, timeout or error and recovering the current widget response before submit when the hidden token field is empty.
- Released the Tools-backed site identity metadata and bumped the plugin release metadata to
3.1.2.
3.1.1
- Added an explicit admin checkbox for Turnstile on the public delisting/removal page.
- The public delist flow no longer inherits Turnstile automatically just because comment or registration Turnstile is configured.
- Site owners can now disable only the removal-page challenge when Cloudflare Turnstile has temporary problems, while keeping comment and registration protection enabled.
3.1.0
- Added the plugin-side DNSBL write integration (
add,delete,update,bulk) around one visible Write token field, bulk queueing, and optional dry-run acknowledgement through the Tools DNSBL endpoints. - Added the shortcode-based removal form (
[dnsbl_removal_form]) with AJAX backend proxy support, built-in main removal-page templating, and live delisting-page permission gating. - Added the Tools-backed checker/removal follow-up via
POST /api/dnsbl/check-ip, together with the checker-style public delist flow and dashboard/settings warnings when live delete / delist access is still missing. - Added advanced optional CIDR removal flow for permitted tokens, including safe
/24../32validation, plugin-local scan progress, a visible hit list of listed addresses, listed-hit-only delete targeting, sequential per-IP delete requests, and Cloudflare Turnstile verification for live removal-form submissions. - The plugin UI now uses one visible DNSBL / Tools API token field, and the Check token permissions tool now always asks Tools for a live answer and reports effective DNSBL access more clearly.
- Preferred resolver hosts now cover all four canonical DNSBL/FraudBL zones, and migrations merge any missing defaults into existing installs without removing custom hosts.
- Shortcode/custom removal pages now expose only the operations allowed by the current token, while the plugin-managed main removal page stays delete-focused.
- Token status panels, delisting-page controls, and checker submits now better reflect real delete capability, including explicit IP reposting when the checker has locked the field before submit.
- Checker follow-up failures now report clearer backend/API errors for remote
419cases, and write/check diagnostics now distinguish true invalid DNSBL tokens from wrong-token-type or inactive admin-key cases. - Checker-mode Turnstile stays hidden during pre-check/background steps, is enforced on actual write submissions, the Delist button now carries the in-flight submit state itself, and checker/delist requests now also show a dedicated busy spinner row.
- CIDR scanning now stays inside WordPress in small local batches so the resolver side is not flooded, while the final delete still goes through the DNSBL write endpoint after the block scan has found at least one listed address and only for the IPs the local scan actually marked as listed, one IP at a time.
- If the user clicks Check if listed while a valid CIDR is still entered in the first checker IP field, the plugin now opens Advanced automatically, moves the CIDR there, and keeps that Advanced CIDR value as the authoritative range for the later scan/delete flow instead of requiring a separate single-IP anchor.
- The admin UI now also shows a dismissible reminder that links directly to the WordPress.org review form for quick feedback.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Tornevall Networks DNSBL Impl… alternatives
All antispam plugins →FAQ
Tornevall Networks DNSBL Implementa…: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 1, 2026
Is Tornevall Networks DNSBL Implem… free?
Yes. Tornevall Networks DNSBL Implem… is free to download and use from the official WordPress.org plugin directory.
Is Tornevall Networks DNSBL Implem… safe to use in 2026?
Tornevall Networks DNSBL Implem… works, but test it on a staging site before relying on it in 2026. It runs on 10+ sites and was last updated 3 months ago, and scores 57/100 on our health check.
How many websites use Tornevall Networks DNSBL Implem…?
Tornevall Networks DNSBL Implem… is active on 10+ WordPress websites and has been downloaded 2,488 times since it launched in November 2014. It was downloaded 71 times in the last 30 days.
Does Tornevall Networks DNSBL Implem… work with WordPress 7.1?
Tornevall Networks DNSBL Implem… is officially tested up to WordPress 7.0.6, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does Tornevall Networks DNSBL Implem… need?
Tornevall Networks DNSBL Implem… requires PHP 8.1 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Tornevall Networks DNSBL Implem… last updated?
The latest version, 3.1.5, was released on July 5, 2026 (3 months ago).
Who makes Tornevall Networks DNSBL Implem…?
Tornevall Networks DNSBL Implem… is developed and maintained by tornevall.
What are the best alternatives to Tornevall Networks DNSBL Implem…?
The most popular alternatives to Tornevall Networks DNSBL Implem… are Akismet Anti-spam: Spam Pro… (5M+ installs), Antispam Bee (700K+ installs) and reCaptcha by BestWebSoft (100K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card