Description
What if your site could learn from attacks on other sites?
WP fail2ban Blocklist makes that possible.
Participating WordPress sites share information about recent attacks, so your site can benefit from what others have already encountered — and contribute what it sees in return.
Instead of waiting for an attacker to make its first attempt against your site, your firewall can stop it before it even reaches WordPress.
Blocklist is an add-on for WP fail2ban, which detects malicious activity and works with fail2ban to block attackers at your server’s firewall. Blocklist takes that protection further, turning individual observations into shared intelligence.
It’s collaborative protection: your site helps protect others, and they help protect you.
Current attacks, not historical reputations
WP fail2ban Blocklist isn’t another IP reputation database. It’s concerned with attacks happening now, rather than maintaining a permanent list of addresses with a history of suspicious activity.
The network shares observations of recent attacks between participating WordPress sites. Each site receives its own list of hostile IP addresses, based on activity across the network and what that site has already encountered.
An address that was hostile yesterday isn’t necessarily hostile today. Blocklist focuses on recent activity rather than assigning permanent reputations.
The network comes to you
Rather than requiring each participating site to contact a central server for updates, the Blocklist Network Service (BNS) connects to your site through the WordPress REST API.
During that exchange, the service collects selected security observations from your site and delivers its own list of recently hostile IP addresses. Your site contributes to the network and receives intelligence from other participants through the same connection.
The network uses observations from participating WP fail2ban sites, not third-party threat feeds. It cannot warn about an attack source that nobody in the network has encountered yet; your normal WP fail2ban protection remains important.
More about how Blocklist works.
Free and Premium
The Blocklist is free to use with WP fail2ban Free.
Free installations contribute observations to the network and receive a reduced selection of current hostile addresses. WP fail2ban Premium receives the full current Blocklist intelligence available for the site.
Both use the same collaborative network and the same underlying fail2ban and firewall protection.
Built to work with your firewall
Blocklist extends WP fail2ban rather than replacing any part of it. It writes received addresses as syslog events for fail2ban to recognise. Your host firewall does the blocking, before the next request reaches WordPress.
The standard WP fail2ban hard filter can recognise Blocklist messages. For more control, you can give Blocklist a dedicated jail, with its own filter and ban settings. The important thing is that a Blocklist warning should result in an immediate ban (maxretry = 1).
Installation
- Install and activate WP fail2ban (Free or Premium).
- Install and activate WP fail2ban Blocklist.
- Connect through Freemius to register your site with the Blocklist network.
- Open the WP fail2ban Dashboard and find the Blocklist Status widget.
- Configure your
fail2banjail to act immediately on Blocklist messages (maxretry = 1). Use the existingwordpress-hardjail or a dedicated jail with thewpf2b-blocklist-hardfilter. If you use a dedicated jail, enable the corresponding Custom Jail setting in WordPress.
Your first connection
Unlike most WP fail2ban features, Blocklist doesn’t start providing protection immediately after activation.
The BNS connects to your site through the WordPress REST API, at /wp-json/wp-fail2ban/v1/blocklist. That endpoint must be reachable: a hosting firewall, CDN, or another security plugin must not block the service’s requests.
The first visit may take a few hours. The Blocklist Status widget checks connectivity and updates when the BNS first connects, so you can see that your site has joined the network.
Don’t be surprised if you receive few or no IP addresses initially. That’s normal. Blocklist shares intelligence about recent attacks, and it takes time for your site to begin receiving useful results.
Once the first connection has been established, you can hide the Blocklist Status widget and use the full Blocklist dashboard widget instead.
For more detailed configuration, including dedicated fail2ban jails, see the Blocklist documentation.
FAQ
Does Blocklist replace WP fail2ban?
No. Blocklist is an add-on to WP fail2ban. WP fail2ban records security events from your own installation; Blocklist extends that protection using observations from other participating sites.
You should continue to use your normal WP fail2ban protection alongside Blocklist.
Does Blocklist block IP addresses inside WordPress?
No. Blocklist writes events for fail2ban to recognise, and your server’s firewall enforces the resulting bans. Without a working fail2ban jail and firewall action, the add-on cannot provide pre-emptive protection.
Why does Blocklist require a Freemius connection?
Blocklist needs to identify participating sites and authenticate communication with them. WP fail2ban already integrates with Freemius, so the add-on uses that connection rather than requiring another account.
Unlike the normal operation of WP fail2ban Free, Blocklist requires this connection to participate in the network.
I’ve installed Blocklist, but I’m not receiving any IP addresses. Is something wrong?
Usually not. The BNS may take a few hours to make its first connection, and new installations may initially receive no addresses. Check the Blocklist Status widget for connectivity and first-contact information. An empty list by itself doesn’t indicate a problem.
Why does my site receive a different number of addresses from another site?
Each site’s list is selected individually, taking account of what that site has already encountered. Different results are normal, and Free and Premium also receive different-sized selections.
Can I use Blocklist alongside other blocklists?
Yes. WP fail2ban Blocklist is designed to coexist with other blocklists, including those managed by your hosting provider or firewall.
The important thing is that each service manages its own rules without overwriting or interfering with those managed by another. Overlapping IP addresses aren’t a problem: more than one blocklist can identify the same attacker.
You can continue using your existing blocklists while benefiting from the intelligence shared through the WP fail2ban network.
Can I exclude an IP address from Blocklist?
Yes. The Blocklist ignore list lets you exclude specified addresses from received warnings. This can be useful for a trusted network, VPN, or other service you do not want blocked because of activity observed elsewhere.
Can I tell how many attacks Blocklist prevented?
Not directly. Once your firewall has blocked an address, later connections may never reach WordPress. Neither WP fail2ban nor Blocklist can see those rejected connections from inside WordPress.
Your firewall logs may provide additional information, but the number of Blocklist warnings isn’t the number of attacks prevented.
Screenshots
Changelog
3.0.1
- Status dashboard widget: plain-language Blocklist reachability and last contact.
- Quick-start Status card for Blocklist. (Requires WP fail2ban 6.3 or later).
- Settings tab under WP fail2ban Settings. (Requires WP fail2ban 6.0 or later).
- Clarify queued IPv4/IPv6 summary counts and lifetime entry/request totals.
- Update filters for Inline Host support.
- Compatibility changes for upcoming WPf2b release.
- Fix Site Health issue when parse_ini_file() is disabled. (h/t Volker Nagy)
2.2.2
- Fix issue with parsing jails which use journald.
- Fix harmless warning with PHP 8.3.
- Fix documentation links in Site Health checks.
2.2.1
- Fix issue with opting into Freemius (h/t @Nyanchovy).
- Fix Site Health passing test reported as failing (h/t @Patmos).
- Improve debug code.
2.2.0
- Add
WP_FAIL2BAN_ADDON_BLOCKLIST_DEBUG. - Add
WP_FAIL2BAN_ADDON_BLOCKLIST_DEBUG_TRY_ALL_KEYS. - Improve i18n.
2.1.1
- Fix harmless warning with PHP 8.1.
- Compatibility changes for upcoming WPf2b release.
2.1.0
- Add Site Health checks.
- Fix REST authentication issue (CORS headers) with some web servers.
2.0.1
- Fix harmless warning in dashboard widget; appears only before first polling.
- Fix REST authentication when both free and premium installed.
- Fix help links.
2.0.0
- IPv6 support. (Requires WP fail2ban 5.0 or later).
- Change filter filenames to start with
wpf2b-instead ofwordpress-. - Add queue info to admin dashboard widget.
1.1.2
- Add mouseover hints to dashboard widget.
- Improve secret key lookup.
1.1.1
- Fix bug with secret key lookup.
1.1.0
- Add event queue info to dashboard widget.
- Increase maximum queue to 16384 events.
- Fix bug handling too many events.
1.0.2
- Minor bug-fix.
1.0.1
- Minor bug-fix.
1.0.0
- First WordPress directory release.

