Marc Armengou

Security Hardener applies WordPress security best practices based on the <a href="https://developer.wordpress.org/advanced-administration/security/hardening/" rel="nofollow ugc">WordPress Advanced Administration / Security / Hardening</a> documentation and widely accepted hardening measures. It uses WordPress core functions and follows best practices without modifying core files.
<h4>Key Features</h4>
File Security: 
* Disable file editor in WordPress admin 
* Optionally disable all file modifications (blocks updates – use with caution)
XML-RPC Protection: 
* Disable XML-RPC completely (enabled by default) 
* Remove pingback methods when XML-RPC is enabled
Pingback Protection: 
* Disable self-pingbacks 
* Remove X-Pingback header 
* Block incoming pingbacks
User Enumeration Protection: 
* Block <code>/?author=N</code> queries (returns 404) 
* Secure REST API user endpoints (require authentication) 
* Remove users from XML sitemaps 
* Prevent canonical redirects that expose usernames 
* Optionally block author feed pages (<code>/author/username/feed/</code>)
Login Security: 
* Generic error messages (no username/password hints) 
* Login honeypot — silently blocks bots before any credential check 
* IP-based rate limiting with configurable thresholds 
* Security event logging (last 100 events) 
* Automatic blocking after failed attempts
Security Headers: 
* <code>X-Frame-Options: SAMEORIGIN</code> (clickjacking protection) 
* <code>X-Content-Type-Options: nosniff</code> (MIME sniffing protection) 
* <code>Referrer-Policy: strict-origin-when-cross-origin</code> 
* <code>Permissions-Policy</code> (restricts geolocation, microphone, camera) 
* Optional HSTS (HTTP Strict Transport Security) for HTTPS sites — max-age set to 1 year
Additional Hardening: 
* Hide WordPress version (meta generator tag and asset query strings) 
* Remove obsolete wp_head items (RSD, WLW manifest, shortlink, emoji scripts) 
* Security event logging system 
* Optionally disable Application Passwords for API authentication
<blockquote>
⚠️ Important: Always test security settings in a staging environment first. Some features may affect third-party integrations or plugins.
</blockquote>
Privacy: This plugin does not send data to external services and does not create custom database tables. It stores plugin settings and a security event log in the WordPress options table, and uses transients for temporary login attempt tracking. All data is preserved on uninstall by default and only deleted if the “Delete all data on uninstall” option is explicitly enabled.

Security Hardener

Basic hardening: secure headers, login honeypot, user enumeration blocking, generic login errors, rate limiting, and more.

Bill Minozzi

<ul>
<li>Not whitelisted IPs need fill out one aditional email field in login form.</li>
<li>Firewall to Block Malicious Requests, Queries, User Agents and URLS. 100% Plug-n-play, no configuration required.</li>
<li>Option to disable xml-rpc API. </li>
<li>Option to disable Json WordPress Rest API (also new WordPress 4.7 Rest API).</li>
<li>Option to login notification by email.</li>
<li>Alert when this plugin is deactivated.</li>
<li>Alert when a new plugin is installed at your site.(usually first thing hacker do after attack you)</li>
<li>Optionally, let you hide your site (and login page) from attackers.</li>
<li>Stay Up-to-Date: Option to set WordPress to automatically download and install themes and plugin updates.</li>
<li>WordPress Debug enabled warning.</li>
<li>Disable file editing within the WordPress dashboard.</li>
<li>Replace insecure login error message.</li>
<li>Multilingual ready.</li>
</ul>
Report not whitelisted IP address attacks to the respective abuse departments of the infected PCs/servers, through free services of blocklist, to ensure that the responsible provider can inform their customer about the infection and disable the attacker.
No fail2ban or another software required.
We hope our plugin makes the Internet better, safer and helps to clean infected PCs.
<h3>Startup Guide</h3>
1) Open the Request API Key page (under Report Attacks Menu) and follow the instructions to get your free API KEY.
2) After receive the Blocklist email with your API KEY, go to Blocklist Settings Tab and fill out your free API info. Check Yes to begin to report attacks. We can report attacks when the same IP attempt attacks you more than 5 time
3) Important: Add your’s IP address to MY IP White List.
4) At eMail Settings tab, you can customize your contact email or left blank to use your wordpress eMail.
5) At Notification Settings Tab, you can record your option by receive or not email alerts about failed logins.
6) Open the Plugin General Settings Tab and click over Yes (to begin to record failed login attempts).
Remember to click Save Changes before to left each tab.
To manage the failed login’s table, go to Failed Logins Table
That is all. Enjoy it.
<h3>Credits (Thanks)</h3>
Translation to Germany by emha.koeln (@emhakoeln)

ReportAttacks — Brute Force & Login Protection

Report login brute force attacks and improve login protection.

Security Hardener vs ReportAttacks — Brute Force & Login Protection