supersoju

Block Logins with Cloudflare helps protect your WordPress site from brute-force attacks by blocking IPs at the Cloudflare firewall after a configurable number of failed login attempts.
<ul>
<li>Block IPs via Cloudflare after X failed login attempts</li>
<li>Block IPs that generate excessive 404 responses (bots and scanners)</li>
<li>Block IPs attacking via XML-RPC with intelligent detection</li>
<li>Automatic unblocking after a configurable duration</li>
<li>Whitelist IPs to never block or track them (supports IPv6 CIDR ranges)</li>
<li>View and manually unblock blocked IPs from the admin</li>
<li>Block source tracking — see whether each IP was blocked via login, XML-RPC, or 404</li>
<li>Sync existing Cloudflare blocks into the local blocked IPs list</li>
<li>Secure settings page with Cloudflare API token validation</li>
<li>Hourly cron job for automatic maintenance</li>
</ul>
<h3>External Services</h3>
This plugin relies on the Cloudflare API to function. It communicates with Cloudflare’s external servers to block IP addresses at the firewall level.
What is the Cloudflare API and what is it used for? 
The Cloudflare API is a RESTful service provided by Cloudflare, Inc. that allows programmatic management of Cloudflare firewall rules. This plugin uses it to automatically block and unblock IP addresses based on failed login attempts, XML-RPC attacks, and 404 scanning activity.
What data is sent and when? 
The plugin sends the following data to Cloudflare’s API servers:
<ol>
<li>
During settings validation (when you save Cloudflare credentials):
<ul>
<li>Your Cloudflare API token (for verification)</li>
<li>Endpoint: <code>https://api.cloudflare.com/client/v4/user/tokens/verify</code></li>
</ul>
</li>
<li>
When blocking an IP (after a threshold is reached):
<ul>
<li>The IP address to be blocked</li>
<li>Your Cloudflare email address and API key/token</li>
<li>Your Cloudflare Zone ID</li>
<li>A note describing the reason for the block</li>
<li>Endpoint: <code>https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/access_rules/rules</code></li>
</ul>
</li>
<li>
When syncing from Cloudflare (on demand):
<ul>
<li>Fetches existing firewall rules from your Cloudflare zone</li>
<li>Endpoint: <code>https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/access_rules/rules</code></li>
</ul>
</li>
</ol>
No personally identifiable information about your WordPress users is transmitted. Only IP addresses are sent to Cloudflare.
Service provider information: 
– Service: Cloudflare API 
– Provider: Cloudflare, Inc. 
– Terms of Service: https://www.cloudflare.com/terms/ 
– Privacy Policy: https://www.cloudflare.com/privacypolicy/ 
– API Documentation: https://developers.cloudflare.com/api/
Required for functionality: 
This plugin requires a Cloudflare account and will not function without valid Cloudflare API credentials. The external API calls are essential to the plugin’s core functionality.
<h3>License</h3>
GNU General Public License v2 or later

Block Logins with Cloudflare

Block brute-force login attempts by integrating with Cloudflare's firewall to automatically block IPs after failed logins.

GuardGiant brute force protection

The only plugin with 100% brute force protection that doesn’t lock out genuine users.
<h4>Brute Force Protection</h4>
This security plugin implements an approach used by large websites such as Facebook, Google etc.
When a genuine user makes a successful login to their account using their mobile phone, tablet, or computer GuardGiant starts treating their device as Trusted.
<ul>
<li>Failed login attempts from trusted devices are directed towards ‘Lost Password’ forms rather than being subject to account lockouts or additional counter measures.</li>
<li>Users receive an alert when anyone logs into their account from an unrecognized device or browser.</li>
</ul>
<h4>Stop Hackers</h4>
GuardGiant uses a range of strong counter-measures to limit login attempts from unrecognized devices. The default behaviour is:
<ul>
<li>After 3 failed login attempts from the same unrecognized device, a Google ReCaptcha field is added to the login page. ReCaptcha is a strong counter-measure that is very hard for an automated process to solve.</li>
<li>After 10 failed login attempts a temporary block of 2 minutes is applied to the device/IP address. No login attempts can be made during this time.</li>
<li>Each further failed login attempt increases the block time by another minute. This slows down attacks to the point where they quickly become unviable.</li>
</ul>
All behavior is fully customizable to achieve the level of brute force protection that you require.
<h4>Login History</h4>
A fully featured security log gives you visibility to login attempts on your site.
<ul>
<li>Provides geographic location, device type, IP address and more for each login attempt.</li>
<li>Filter login attempts by Trusted or Unrecognized devices.</li>
<li>Search by IP address or username.</li>
<li>Filter by successful or failed attempts.</li>
<li>Easy to display successful logins from unrecognized devices that could indicate a hacked account.</li>
</ul>
This login history log should form an essential part of your brute force login protection plan. GDPR compliant.
<h4>Other Login Security Improvements</h4>
This security plugin implements various improvements recommended by the Open Web Application Security Project® (OWASP) to keep your site safe:
<ul>
<li>Obfuscates login errors to stop hackers detecting valid account names.</li>
<li>Option to disable XMLRPC.</li>
<li>And much, much more.</li>
</ul>
This security plugin is exceptionally easy to use no matter what your level of technical expertise.
The default settings are highly optimized, designed to prevent brute force attacks whilst not disturbing genuine users from logging in. Advanced users can fully customize the behavior of this plugin to suit their own environment.
<h4>Login Security Plugin – Background Information</h4>
The most common threat that WordPress site owners face is a password guessing attack known as a brute force attack. 
A brute force attack is where an attacker uses a brute force tool (or script) to discover your password by systematically trying every possible combination of letters, numbers, and symbols until the correct password is found. A brute force attack will always work eventually, but the problem for the brute force attacker is that it may take many years to do it.
Brute force prevention techniques focus on slowing down these attacks to the point where they become unviable.
Using long and complex passwords (that are not dictionary words) is a good brute force attack prevention method to start with. This greatly increases the time an attacker will need.
A common way to stop brute force attacks is to lock out the WordPress account after a defined number of failed authorization attempts (there are various brute force plugins that do this). 
The problem with this approach is that the site administrator ends up with unhappy users who have been locked out, often needing manual intervention to regain access. This is not sustainable or desirable for sites of any size.
The modern approach to brute force prevention is to track the devices that genuine users use to log in, ensuring they are always treated kindly if they forget their password. Unrecognized devices face a progressive but temporary timed lockout.
<h4>Stop Brute Force Attacks</h4>
Periodic monitoring of your security audit log can help you stop brute force attacks.
Here are patterns that indicate a brute force attack or some other account abuse:
<ul>
<li>Failed login attempts using alphabetically sequential usernames or passwords</li>
<li>Multiple different usernames being used by the same IP address</li>
<li>Logins for a single account coming from many different IP addresses</li>
<li>Failed logins at a specific period e.g. every 5 minutes</li>
</ul>

WordPress Brute Force Protection – Stop Brute Force Attacks

The only plugin with 100% brute force protection that doesn't lock out genuine users.

Block Logins with Cloudflare vs WordPress Brute Force Protection – Stop Brute Force Attacks