Lightweight, behavior-based bot firewall. Blocks scanners before WordPress loads, with text attack reports for your hosting company.

sourcecode347

Anti Browser DDoS Protection

Protects WordPress from DDoS with rate limiting, bot detection, blocking, Cloudflare support, logs, charts, and bot list export/import.

Miguel Muller

WordPress Block Analytics Spam

Stop the Spam bot as semalt and buttons-for-website that appear on Google Analytics and have real reports.

GEO Tools

GEO Website Protection & Access Control

Take control of your website visitors with GEO Visitor Control – block countries, IPs, manage bots, log blocked sessions, and customize everything wit …

susheelhbti

TrapFlux Request Firewall is a lightweight request firewall that blocks vulnerability scanners and bot floods by how they behave, not just where they come from.
<ul>
<li>Behavior-based blocking — exploit-path probes (<code>.env</code>, <code>wp-config</code> backups, <code>.sql</code> dumps), malicious user agents, and request floods.</li>
<li>Rate limiting — every visitor is rate limited; hits on exploit paths count double, so scanners get banned far faster than real visitors ever could.</li>
<li>Honeypot traps — invisible links only bots follow; one visit means a permanent ban.</li>
<li>Subnet bans — block a whole CIDR range (e.g. <code>20.100.172.0/24</code>) when attackers rotate IPs on cloud providers.</li>
<li>Text attack reports — one-click downloadable <code>.txt</code> reports (summary + raw log) listing every URL attackers tried to access, ready to hand to your hosting company.</li>
<li>fail2ban-friendly log — one pipe-delimited line per blocked request, so your host can ban attackers at the network level using the plugin’s detections.</li>
<li>Fails open — any internal error and your site keeps working normally. An emergency <code>disable.flag</code> file shuts blocking off instantly via FTP.</li>
</ul>
<h4>Strongest mode (optional)</h4>
By default the firewall runs when plugins load — before WP routing, themes and queries. For maximum resource savings you can point PHP’s <code>auto_prepend_file</code> at <code>firewall.php</code> so blocking happens before WordPress loads at all. See the FAQ.
<h4>Honest limitations</h4>
<ul>
<li>This is a request firewall, not a malware scanner — it will not detect an already-infected site.</li>
<li>It ships with rules for today’s common probes and has no cloud threat feed; review the rules occasionally.</li>
<li>The “Block xmlrpc.php” option breaks Jetpack and the WordPress mobile app — disable that single toggle if you use them.</li>
<li>All assets (CSS/JS) are bundled — the plugin makes no external network requests.</li>
</ul>

Alternatives to TrapFlux Request Firewall

Top alternatives