themelooks

CoxWall is a powerful and lightweight WordPress security plugin designed to protect your website from modern security threats, brute-force attacks, malware attempts, and unauthorized access.
It provides advanced security tools including firewall protection, login hardening, security headers, file integrity monitoring, WooCommerce security, and detailed audit logging — all in an easy-to-use interface.
Whether you run a blog, business website, membership platform, or WooCommerce store, CoxWall helps keep your WordPress site secure and protected in real time.
Key Features:
<ul>
<li>Login Protection – Limit login attempts per IP, lock out attackers, and receive email alerts.</li>
<li>Hide Login – Move your login URL away from the default <code>wp-login.php</code>.</li>
<li>CAPTCHA – Google reCAPTCHA v2 / v3 on login, registration, and WooCommerce forms.</li>
<li>Firewall – Block SQLi, XSS, directory traversal, malicious bots, and XML-RPC abuse.</li>
<li>Security Headers – Set X-Frame-Options, CSP, HSTS, Referrer-Policy, and more.</li>
<li>File Integrity – Detect changes to WordPress core and plugin files.</li>
<li>WooCommerce – Extra security for WooCommerce stores.</li>
<li>Audit Log – Full event log with IP, user, and timestamp for every security event.</li>
</ul>
Why Choose CoxWall?
<ul>
<li>Lightweight and performance-friendly</li>
<li>Beginner-friendly setup</li>
<li>Modern security protection</li>
<li>WooCommerce compatible</li>
<li>Advanced firewall system</li>
<li>Detailed security logging</li>
<li>Real-time protection and monitoring</li>
</ul>
CoxWall helps you secure your WordPress website with enterprise-level protection while keeping the setup simple and user-friendly.
Features:
<ul>
<li>Login Protection</li>
<li>Hide Login URL</li>
<li>Google reCAPTCHA v2 / v3</li>
<li>Firewall Protection</li>
<li>SQL Injection (SQLi) Blocking</li>
<li>XSS Attack Protection</li>
<li>Directory Traversal Protection</li>
<li>Malicious Bot Blocking</li>
<li>XML-RPC Protection</li>
<li>Security Headers Management</li>
<li>Content Security Policy (CSP)</li>
<li>HSTS Support</li>
<li>Referrer Policy Protection</li>
<li>File Integrity Monitoring</li>
<li>Core File Change Detection</li>
<li>Plugin File Change Detection</li>
<li>WooCommerce Security</li>
<li>Audit Log System</li>
<li>IP Activity Logging</li>
<li>User Activity Tracking</li>
<li>Real-time Security Alerts</li>
<li>Email Notifications</li>
<li>Brute-force Protection</li>
<li>Login Attempt Limiting</li>
<li>IP Lockout System</li>
<li>Malware Defense</li>
<li>Website Hardening</li>
<li>Real-time Monitoring</li>
<li>WordPress Security Suite</li>
</ul>
<h3>External services</h3>
This plugin optionally connects to the following third-party / external services. Each service is only contacted when its corresponding module is enabled and the described conditions are met.
<h4>Google reCAPTCHA (Google LLC)</h4>
What it is and what it is used for: 
Google reCAPTCHA is a bot-detection service. CoxWall uses it to protect the WordPress login, registration, lost-password, comment, and WooCommerce My Account forms from automated attacks.
What data is sent and when: 
When the CAPTCHA module is enabled, two types of requests are made to Google:
<ol>
<li>Front-end (page load) – the visitor’s browser loads the reCAPTCHA JavaScript library directly from Google’s CDN (<code>www.google.com</code>). Google receives the visitor’s IP address, browser and device information, and the site’s public reCAPTCHA site key.</li>
<li>Back-end (form submission) – when a visitor submits a protected form, the plugin sends the reCAPTCHA response token, the site’s secret key, and the visitor’s IP address to Google’s verification endpoint (<code>www.google.com/recaptcha/api/siteverify</code>) to confirm the response is valid.</li>
</ol>
No data is sent if the CAPTCHA module is disabled or if no reCAPTCHA site/secret key has been configured.
Service provider links: 
* Terms of Service: https://policies.google.com/terms 
* Privacy Policy: https://policies.google.com/privacy 
* reCAPTCHA-specific information: https://developers.google.com/recaptcha
<h4>WordPress.org Core Checksums API (WordPress.org)</h4>
What it is and what it is used for: 
The WordPress.org Checksums API provides official MD5 hashes for every file in each WordPress core release. CoxWall’s File Integrity module uses these hashes to detect unauthorized modifications to core files.
What data is sent and when: 
When a file integrity scan runs (manually triggered or on schedule), the plugin sends a GET request to <code>https://api.wordpress.org/core/checksums/1.0/</code> containing:
<ul>
<li>The installed WordPress version number.</li>
<li>The site’s configured locale/language.</li>
</ul>
No personal data, user data, or site content is transmitted. The request retrieves a publicly available checksum list.
Service provider links: 
* Privacy Policy: https://wordpress.org/about/privacy/ 
* API documentation: https://codex.wordpress.org/WordPress.org_API

CoxWall

Professional WordPress security plugin with firewall, brute-force protection, login hardening, security headers, and file integrity monitoring.

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.

CoxWall vs WordPress Brute Force Protection – Stop Brute Force Attacks