Omajemite Don

BotFend Anti-Bot Firewall is a professional-grade WordPress security suite designed to stop automated attacks, malicious bots, and brute-force attempts before they consume your server resources. Built with a high-performance V4 architecture, it features a smart aggregation engine and an early-loading Web Application Firewall (WAF) that neutralizes threats at the server level.
Developed by Omajemite Don, BotFend protects your site without slowing it down.
<h3>Core Features:</h3>
<ul>
<li>Advanced Web Application Firewall (WAF): Uses <code>auto_prepend_file</code> via <code>.htaccess</code> or <code>.user.ini</code> to block attacks before WordPress even loads.</li>
<li>Intelligent Bot Detection: Identifies and blocks malicious bots, crawlers, and scrapers using advanced signature detection.</li>
<li>Behavioral Analysis: Monitors visitor behavior patterns to detect and block automated threats that mimic human activity.</li>
<li>Browser Fingerprinting: Generates unique browser fingerprints to track and identify persistent attackers across sessions and IP changes.</li>
<li>Advanced 404 Detection: Detects and blocks malicious path scanning, vulnerability probing, and excessive 404 abuse patterns.</li>
<li>WordPress Protection: Comprehensive protection against XML-RPC attacks, REST API abuse, author scanning, and WordPress-specific vulnerabilities.</li>
<li>Signature Detection: Real-time pattern matching against known attack signatures and malicious payloads.</li>
<li>Smart Log Aggregation: High-performance database architecture that centralizes logging to prevent database bloat and memory crashes, even under heavy attack.</li>
<li>Perpetual Offender Tracking: Automatically upgrades temporary bans to permanent blocks for IPs that repeatedly attack your site.</li>
<li>Real-Time Threat Intelligence: Integrates with external databases to verify IP reputations on the fly.</li>
<li>Tor Node Blocking: Automatically detects and blocks malicious traffic originating from the Tor anonymity network.</li>
<li>Comprehensive UI: Clean, intuitive WordPress admin interface with bulk actions, detailed threat analysis timelines, and visual statistics.</li>
</ul>
<h3>Pro Features (Available with License):</h3>
<ul>
<li>Full Firewall Auto Prepend: Execute firewall protection at the earliest possible stage of WordPress execution</li>
<li>Cloudflare Integration: Synchronize blocked IPs to Cloudflare firewall rules at the edge, blocking attacks before they reach your server</li>
</ul>
<h3>External Services</h3>
IMPORTANT: All external services are DISABLED BY DEFAULT. You must explicitly enable each service in the plugin settings before any data is sent.
This plugin can connect to the following external services to provide enhanced threat protection. No data is sent unless you explicitly enable these features.
<h3>1. AbuseIPDB API</h3>
<ul>
<li>Purpose: Checks the reputation of suspicious IP addresses against a global database of reported abusers</li>
<li>Data sent: The IP address of the visitor being checked</li>
<li>When: When AbuseIPDB integration is enabled AND an IP address needs verification (cached for 24 hours)</li>
<li>How to disable: Set “Enable AbuseIPDB” to OFF in plugin settings (default: OFF)</li>
<li>Terms of Service: https://www.abuseipdb.com/legal</li>
<li>Privacy Policy: https://www.abuseipdb.com/privacy</li>
</ul>
<h3>2. IPHub API</h3>
<ul>
<li>Purpose: Detects VPNs, proxies, and non-residential IP addresses</li>
<li>Data sent: The IP address of the visitor being checked</li>
<li>When: When IPHub integration is enabled (default: OFF)</li>
<li>How to disable: Set “Enable IPHub” to OFF in plugin settings (default: OFF)</li>
<li>Terms of Service: https://iphub.info/legal/terms</li>
<li>Privacy Policy: https://iphub.info/legal/privacy</li>
</ul>
<h3>3. IP Geolocation Services</h3>
<ul>
<li>Purpose: Determine the country of origin for IP addresses to apply geographic blocking rules</li>
<li>Data sent: The IP address of the visitor being geolocated</li>
<li>When: When geolocation is enabled (default: OFF) AND an IP needs geolocation (results cached)</li>
<li>How to disable: Set “Enable IP Geolocation” to OFF in plugin settings (default: OFF)</li>
<li>Services used:</li>
</ul>
<h4>ip-api.com</h4>
<ul>
<li>Purpose: Primary geolocation service</li>
<li>Terms: https://ip-api.com/terms</li>
<li>Privacy: https://ip-api.com/privacy</li>
</ul>
<h4>ipapi.co</h4>
<ul>
<li>Purpose: Fallback geolocation service</li>
<li>Terms: https://ipapi.co/terms/</li>
<li>Privacy: https://ipapi.co/privacy/</li>
</ul>
<h4>ipwhois.io</h4>
<ul>
<li>Purpose: Secondary fallback geolocation service</li>
<li>Terms: https://ipwhois.io/terms</li>
<li>Privacy: https://ipwhois.io/privacy</li>
</ul>
<h3>4. Tor Project Exit List</h3>
<ul>
<li>Purpose: Downloads the official list of active Tor exit nodes to block anonymous attacks</li>
<li>Data sent: None (only downloads a public list)</li>
<li>When: Every 6 hours when Tor blocking is enabled (default: OFF)</li>
<li>How to disable: Set “Enable Tor Blocking” to OFF in plugin settings (default: OFF)</li>
<li>Service URL: https://check.torproject.org/torbulkexitlist</li>
<li>Terms of Use: https://www.torproject.org/about/trademark/</li>
<li>Privacy Policy: https://www.torproject.org/about/privacy_policy/</li>
</ul>
<h3>5. dan.me.uk Tor List (Alternative Source)</h3>
<ul>
<li>Purpose: Alternative source for Tor exit node list when primary source is unavailable</li>
<li>Data sent: None (only downloads a public list)</li>
<li>When: Only used as fallback when primary Tor list fails and Tor blocking is enabled</li>
<li>How to disable: Disable Tor blocking in plugin settings (default: OFF)</li>
<li>Service URL: https://www.dan.me.uk/torlist/</li>
<li>Terms/Privacy: This is a public service with no formal terms or privacy policy. Use is governed by standard HTTP protocol.</li>
</ul>
<h3>6. Threat Intelligence Feeds</h3>
<ul>
<li>Purpose: Download curated lists of known malicious IP addresses</li>
<li>Data sent: None (only downloads public blocklists)</li>
<li>When: When threat intelligence is enabled (default: OFF) and feeds need refreshing</li>
<li>How to disable: Set “Enable Threat Intelligence” to OFF in plugin settings (default: OFF)</li>
<li>Feeds used:
<ul>
<li>FireHOL: https://firehol.org/ (Public domain blocklists)</li>
<li>Blocklist.de: https://www.blocklist.de/ (Terms: https://www.blocklist.de/en/terms.html)</li>
<li>Emerging Threats (Proofpoint): Real-time threat intelligence feeds</li>
<li>Terms: https://www.proofpoint.com/us/legal/license</li>
<li>Privacy: https://www.proofpoint.com/us/legal/privacy-policy</li>
</ul>
</li>
</ul>
<h3>7. Google reCAPTCHA</h3>
<ul>
<li>Purpose: Provides bot verification on login, registration, and comment forms</li>
<li>Data sent: Browser interaction data sent to Google’s servers</li>
<li>When: When reCAPTCHA is enabled AND a user interacts with a protected form</li>
<li>How to disable: Set reCAPTCHA site key and secret key to empty in plugin settings</li>
<li>Terms of Service: https://policies.google.com/terms</li>
<li>Privacy Policy: https://policies.google.com/privacy</li>
</ul>
<h3>8. Cloudflare API Integration (PRO VERSION)</h3>
<ul>
<li>Purpose: Synchronize blocked IPs to Cloudflare firewall rules at the edge, blocking attacks before they reach your server</li>
<li>Data sent: IP addresses, threat scores, authentication credentials, and configuration parameters during API calls</li>
<li>When: During manual sync operations, scheduled automatic syncs, and license validation</li>
<li>How to disable: Available only in Pro version with valid license</li>
<li>Terms of Service: https://www.cloudflare.com/terms/</li>
<li>Privacy Policy: https://www.cloudflare.com/privacypolicy/</li>
</ul>
<h3>Data Handling Summary</h3>
<ul>
<li>No data is sent to any external service unless you explicitly enable that feature</li>
<li>All API results are cached to minimize external requests</li>
<li>Regular visitor IPs are never sent – only suspicious or attacking IPs trigger external lookups</li>
<li>You can disable ALL external services in the plugin settings</li>
<li>Plugin works perfectly with all external services disabled</li>
</ul>
<h3>Privacy</h3>
This plugin respects user privacy: 
– No tracking of regular site visitors 
– No analytics or usage data collected 
– All external services are opt-in (disabled by default) 
– Full transparency: All external service calls are documented above

BotFend Anti-Bot Firewall

Professional security plugin protecting WordPress from malicious bots, spam, and server attacks using an advanced Web Application Firewall.

trustsig

TrustSig Security protects WordPress forms and API endpoints from scripted bots and brute-force attacks. No puzzles. No “I am not a robot” checkboxes. No third-party signup required to start. Coverage depends on the protection mode you choose — see “Protection modes” below.
<a href="https://ps.w.org/trustsig-security/assets/screenshot-1.png" rel="nofollow ugc"></a> 
<a href="https://ps.w.org/trustsig-security/assets/screenshot-2.png" rel="nofollow ugc"></a> 
<a href="https://ps.w.org/trustsig-security/assets/screenshot-3.png" rel="nofollow ugc"></a>
<h4>Why TrustSig</h4>
<ul>
<li>Protects every important form out of the box — login, registration, comments, password reset, WooCommerce checkout, BuddyPress signup, Easy Digital Downloads, Elementor Pro forms, WPForms (including the Mesmerize / Materialis contact form), Contact Form 7, SureForms, and any custom form via shortcode.</li>
<li>Stops brute-force login attempts with built-in lockout after repeated failures.</li>
<li>Invisible to humans — real visitors are verified in under a second by a non-interactive browser check. No CAPTCHA, no images to click.</li>
<li>Three protection modes — Monitor (log only), Challenge (default, soft block with auto-retry), Enforce (hard block).</li>
<li>Zero configuration — activate the plugin and protection is live immediately. Anonymous free tier needs no account.</li>
<li>Works with caching plugins, WPML, multisite and most themes — forms are signed server-side with a per-site secret.</li>
<li>Developer-friendly — PHP helper <code>trustsig_verify()</code>, REST endpoint <code>/wp-json/trustsig/v1/verify</code>, filters and actions for custom forms.</li>
<li>Optional admin-ajax and REST API guard for advanced sites.</li>
<li>GPLv2 — fully open source.</li>
</ul>
<h4>How it works</h4>
TrustSig injects a lightweight browser SDK, signs every rendered form with a per-site secret, and verifies submissions against the TrustSig Edge service. Real visitors pass an invisible check in about a second; scripted clients that never run JavaScript are stopped.
When a request arrives without a valid token, TrustSig does not silently fail 
open. Depending on the mode you choose it serves a lightweight “please wait” 
interstitial that re-verifies the browser and then transparently continues the 
original request — or blocks it.
The plugin works out of the box with no account and no API keys (anonymous 
free tier). Connecting a TrustSig dashboard account is optional and only adds 
analytics and higher limits.
<h4>Protection modes</h4>
<ul>
<li>Monitor — verify and log only, never block. Used for safe rollout; the 
upgrade path also pins existing sites here so behaviour never changes 
silently on update.</li>
<li>Challenge (default for new installs) — a missing or invalid token shows 
the interstitial, then continues or blocks.</li>
<li>Enforce — a missing or invalid token is blocked immediately.</li>
</ul>
<h4>What it protects</h4>
Browser forms are protected automatically with no code:
<ul>
<li>WordPress core — login, registration, comments, lost/reset password</li>
<li>WooCommerce — login, registration, checkout, pay order, lost password</li>
<li>BuddyPress — registration</li>
<li>Easy Digital Downloads — login, registration</li>
<li>Elementor Pro forms</li>
<li>WPForms — contact and other forms, on by default (covers the Mesmerize / Materialis contact section)</li>
<li>Contact Form 7 — feedback submissions, on by default (guarded on the REST endpoint CF7 submits to)</li>
<li>SureForms — form submissions, on by default (guarded on the REST submit-form endpoint)</li>
<li>Any other form (site-wide “protect all forms” option, the <code>[trustsig_form]</code> 
shortcode, or a hidden <code>trustsig-response</code> input)</li>
</ul>
It also includes optional brute-force lockout for repeated failed logins, an 
opt-in admin-ajax / REST API guard, and a developer verification API.
<h4>For developers</h4>
<ul>
<li>PHP: <code>trustsig_verify( array( 'token' => $t, 'action' => 'my_form' ) )</code> 
returns <code>pass</code> | <code>fail</code> | <code>challenge</code>. Filters: <code>trustsig_pre_verify</code>, 
 trustsig_result. Action: <code>trustsig_blocked</code>.</li>
<li>REST: <code>POST /wp-json/trustsig/v1/verify</code> with <code>{ "token": "..." }</code>.</li>
</ul>
<h4>Known limitations</h4>
<ul>
<li>XML-RPC (<code>xmlrpc.php</code>) is intentionally out of scope and is not verified. 
Disable XML-RPC separately if it is unused on your site.</li>
<li>admin-ajax and the REST API are only protected when explicitly enabled in 
Settings, to avoid breaking third-party integrations.</li>
<li>File-upload and AJAX submissions cannot show the interstitial; under 
Challenge or Enforce mode a missing token on those is blocked, never 
silently allowed.</li>
</ul>
<h3>External services</h3>
This plugin relies on the TrustSig Edge service to decide whether a request 
comes from a human or an automated client. This bot-detection verdict cannot be 
produced locally, so the service is required for the plugin’s core 
functionality.
Service provider: TrustSig — https://trustsig.eu
Remote script loaded in the browser: 
 https://edge.trustsig.eu/trustsig.js is loaded on pages that contain a 
protected form, on the login screen, and on the verification interstitial. The 
script runs the non-interactive browser check and produces a verification 
token.
Data sent from the visitor’s browser / your server to 
 https://edge.trustsig.eu/verify:
<ul>
<li>the TrustSig verification token generated by the SDK in the visitor’s browser;</li>
<li>your site’s host name (e.g. <code>example.com</code>) on the anonymous free tier, or, if 
you connect a dashboard account, the secret key you entered;</li>
<li>as part of any HTTPS request, the visitor’s IP address and standard request 
metadata (such as the user-agent) are visible to the service.</li>
</ul>
When data is sent: when the SDK loads on a protected page, when a protected 
form is submitted, and once per browser when the optional verified-session 
cookie is bootstrapped.
Data stored locally on your site: TrustSig writes a verification log to 
your own WordPress database (custom tables) that includes visitor IP addresses, 
the action attempted, and the verdict. This data is not sent to TrustSig; you 
can clear it at any time from Settings → TrustSig → Tools.
By installing and activating this plugin you (the site administrator) consent to 
this data being sent to TrustSig so that requests can be verified. Inform your 
own site’s visitors as required by your local privacy obligations.
<ul>
<li>Terms of Service: https://trustsig.eu/terms-of-service/</li>
<li>Privacy Policy: https://trustsig.eu/privacy</li>
</ul>

TrustSig Security


Deployment was easy, I am not tech savy but was able to get it running in less than a minute. I always had constant email spam from my site, after installing TrustSig it dropped to zero. 10/10


Easy setup and spam stopped

Stop bots, spam and brute-force attacks on every WordPress form. No CAPTCHA. No account. No keys. Installs and protects in one click.

BotFend Anti-Bot Firewall vs TrustSig Security