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.

GDimitrov

FormShield is a powerful form protection plugin that uses advanced pattern matching, behavioral analysis, and IP tracking to protect your WordPress forms from spam and bots without requiring users to solve annoying captchas.
Key Features:
<ul>
<li>No License Restrictions – Protect unlimited forms for free</li>
<li>No Captcha Required – Seamless user experience</li>
<li>Advanced Bot Detection – Uses pattern matching, behavioral analysis, and IP tracking to identify bots</li>
<li>14 Form Integrations – Works with all major form plugins</li>
<li>Real-time Protection – Blocks spam in real-time</li>
<li>Easy Setup – Works out of the box</li>
<li>Form Location Tracking – See exactly where your forms are located (pages, posts, etc.)</li>
</ul>
Supported Form Plugins:
<ul>
<li>Contact Form 7</li>
<li>Gravity Forms</li>
<li>WPForms</li>
<li>Elementor Forms</li>
<li>Ninja Forms</li>
<li>Formidable Forms</li>
<li>Happy Forms</li>
<li>Fluent Forms</li>
<li>WeForms</li>
<li>WSForm</li>
<li>QuForm</li>
<li>Divi Contact Forms</li>
<li>WordPress Comments</li>
<li>And more coming soon!</li>
</ul>
How It Works:
FormShield analyzes user behavior patterns, content patterns, IP history, email validation, and submission frequency to determine if a submission is from a real human or a bot. This multi-layered approach is more effective than traditional captchas and provides a better user experience.
Privacy & Security:
<ul>
<li>Core spam protection runs entirely on your server — no data is sent offsite</li>
<li>Optional AbuseIPDB integration: if you enter an API key, the submitter’s IP address is sent to api.abuseipdb.com to check its abuse reputation. This is disabled by default and requires a user-configured API key</li>
<li>All other features are fully self-contained</li>
<li>GDPR compliant</li>
<li>No user data collection beyond standard WordPress logging</li>
</ul>
<h3>Privacy</h3>
FormShield’s core spam protection runs entirely on your server. No data is transmitted offsite by default.
Optional AbuseIPDB integration: If you configure an AbuseIPDB API key in Settings, the IP address of each form submitter will be sent to <code>api.abuseipdb.com</code> to check for known abuse. This feature is opt-in and disabled unless you provide a key. See https://www.abuseipdb.com/privacy-policy for their privacy policy.
All other processing — honeypot checks, content analysis, behavioral scoring, rate limiting — happens entirely on your WordPress installation.

FormShield

FormShield protects your forms from bot spam using advanced pattern matching and behavioral analysis. No annoying captchas, unlimited forms.

BotFend Anti-Bot Firewall vs FormShield