WP fail2ban Blocklist is a collaborative preemptive blocklist for WordPress.

pluginkollektiv

Block List Updater

Automatic updating of the comment block list in WordPress with antispam keys from GitHub.

YoOhw Studio

B.Ng

Blacklist Manager – WooCommerce Anti-Fraud & Checkout Verification & Spam Prevention (Contact Form 7, Gravity Forms, WPForms)

Anti-fraud, checkout verification and spam prevention plugin for WooCommerce and WordPress forms.

Amber Hinds

Steve Jones

Road Warrior Creative

GravityKit

Gravity Forms Block Email Domains

Easily set a list of email domains to block on email fields in Gravity Forms.

Adam Sewell

tinyShield – Simple. Focused. Security.

Fast, effective, realtime, and crowd sourced protection for WordPress. Easily block bots, brute force attempts, exploits and more without bloat.

them.es

I don't like Spam!

Use the Comment Blocklist feature to protect your contact form.

Maikuolan

CIDRAM

CIDRAM: A PHP-level CIDR/IP-based firewall solution.

Amzil Ayoub

Disposable Email Detector

Blocks user registration with disposable or temporary email addresses. Supports WordPress and WooCommerce.

invisnet

There are many plugins that use a database to check for malicious IPs after they connect, and of course <code>fail2ban</code> stops repeated attacks, but what if bad IPs could be blocked before they attack?
By working collaboratively – sharing attack data – WP fail2ban Blocklist does exactly that.
The Blocklist Network Service (BNS) collects attack data from participating sites, performs some analytical magic, and sends back a list of IPs that are attacking sites now but haven’t yet attacked that site. In other words, each site periodically gets a unique list of IPs to block preemptively.
<h4>GDPR</h4>
The BNS doesn’t collect personal data, and bots don’t have rights.
That said, the BNS only collects the minimum data required (time, IP, event), and only for IPs that have behaved maliciously.
Of course, it is possible that some data is generated by people behaving maliciously, but the BNS has no way to differentiate – and nor should it: an attack is an attack.
<h4>Freemius</h4>
To work, the BNS must know:
<ul>
<li>which sites are running the blocklist add-on,</li>
<li>which version is in use,</li>
<li>and a shared secret for secure communication.</li>
</ul>
Freemius already provides all these, and WP fail2ban already uses Freemius; why reinvent the wheel?
Therefore, unlike the core WP fail2ban plugin, you must opt into Freemius for the blocklist to work.

Alternatives to WP fail2ban Blocklist

Top alternatives