Patrick Schlesinger

<p>ReportedIP Hive Light protects WordPress logins against brute-force and password-spray attacks. It is intentionally focused: a per-IP attempt counter, a progressive block ladder, and an optional community lookup. No bloat, no dashboards, no upsell.</p>
<p><strong>Two operating modes</strong></p>
<ul>
<li><strong>Local Shield (default).</strong> Counts failed logins per IP and blocks attackers based on configurable thresholds. The plugin makes zero outbound network requests in this mode — all data stays on your server.</li>
<li><strong>Community Network (optional).</strong> When you enter a free Community Access Key from reportedip.de, the plugin additionally checks the source IP against the reportedip.de community database during login attempts and shares blocked IPs back to the community. Both calls are clearly disclosed in the settings UI.</li>
</ul>
<p><strong>How it works</strong></p>
<ul>
<li><code>wp_login_failed</code> increments a per-IP counter using an atomic upsert (no race conditions under concurrent attacks).</li>
<li>When the counter exceeds your threshold, the IP is blocked for a duration drawn from a progressive ladder (5 min <span aria-hidden="true" class="wp-exclude-emoji">→</span> 15 min <span aria-hidden="true" class="wp-exclude-emoji">→</span> 30 min <span aria-hidden="true" class="wp-exclude-emoji">→</span> 24 h <span aria-hidden="true" class="wp-exclude-emoji">→</span> 48 h <span aria-hidden="true" class="wp-exclude-emoji">→</span> 7 days).</li>
<li><code>wp_authenticate_user</code> short-circuits known-bad IPs before the WordPress core authentication runs.</li>
<li>Cache plugins (WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed) are honoured via the HTTP 403 status plus explicit <code>Cache-Control: no-store, no-cache, must-revalidate, max-age=0</code> and <code>Pragma: no-cache</code> headers on the block page.</li>
</ul>
<p><strong>Privacy</strong></p>
<ul>
<li>IP addresses are processed for the legitimate purpose of network security (GDPR Art. 6(1)(f)).</li>
<li>Usernames are stored only as a SHA-256 hash, salted with <code>wp_salt()</code>. Plain-text usernames are never persisted or transmitted.</li>
<li>In Local Shield mode, no data leaves your server. In Community Network mode, only the IP, hashed username, event type, and timestamp are sent — no domain, no contact details, no traffic data.</li>
</ul>
<p><strong>For developers</strong></p>
<ul>
<li>Filters: <code>reportedip_hive_is_whitelisted</code>, <code>reportedip_hive_get_client_ip</code>, <code>reportedip_hive_event_category_map</code>, <code>reportedip_hive_api_endpoint</code>.</li>
<li>Actions: <code>reportedip_hive_log</code>, <code>reportedip_hive_ip_blocked</code>, <code>reportedip_hive_report_queued</code>.</li>
</ul>
<p>A free Community Access Key is available at reportedip.de. The plugin works without one in Local Shield mode.</p>
<h3>External services</h3>
<p>This plugin can connect to the ReportedIP API at <code>https://reportedip.de</code>. All<br />
external requests are <strong>opt-in only</strong> — they are made exclusively when (a) a<br />
“Community Access Key” has been entered in the plugin settings and (b) the<br />
“Operation Mode” is set to “Community Network”. The default mode is “Local<br />
Shield”, which performs zero external requests.</p>
<h4>Endpoint 1: IP-reputation lookup</h4>
<ul>
<li>URL: <code>https://reportedip.de/wp-json/reportedip/v2/check?ip={ip}</code></li>
<li>HTTP verb: GET</li>
<li>Auth header: <code>X-Key: {your-access-key}</code></li>
<li>Trigger: a login attempt reaches <code>wp_authenticate_user</code></li>
<li>Timeout: 2 seconds (fail-open — login proceeds when the API does not respond)</li>
<li>Data sent: only the source IP address of the current login attempt</li>
<li>Data NOT sent: usernames, passwords, cookies, server identifiers, domain name</li>
</ul>
<h4>Endpoint 2: Blocked-IP report</h4>
<ul>
<li>URL: <code>https://reportedip.de/wp-json/reportedip/v2/report</code></li>
<li>HTTP verb: POST (JSON body)</li>
<li>Auth header: <code>X-Key: {your-access-key}</code></li>
<li>Trigger: a brute-force / spray threshold has been exceeded; the report is<br />
queued in the database and dispatched by a 15-minute cron job</li>
<li>Data sent: the offending IP, an integer category ID for the threat type,<br />
and a short human-readable comment (e.g. “5 failed logins in 15 minutes”)</li>
<li>Data NOT sent: usernames in plain text, passwords, full request bodies,<br />
domain name, contact information</li>
</ul>
<h4>Endpoint 3: Access-key verification</h4>
<ul>
<li>URL: <code>https://reportedip.de/wp-json/reportedip/v2/verify-key</code></li>
<li>HTTP verb: GET</li>
<li>Auth header: <code>X-Key: {entered-key}</code></li>
<li>Trigger: an administrator clicks “Test connection” in the plugin settings</li>
<li>Data sent: only the access key under verification</li>
</ul>
<h4>Hashing of submitted usernames</h4>
<p>When a brute-force attempt is detected and the failing username is recorded<br />
locally, the plugin stores <code>sha256( username + wp_salt() )</code> only — never the<br />
plain text. The salted hash is also what would be transmitted with a report,<br />
preventing recipients from recovering the original username.</p>
<h4>Service provider</h4>
<ul>
<li>Operator: Patrick Schlesinger, Germany</li>
<li>Service URL: <a href="https://reportedip.de" rel="nofollow ugc">reportedip.de</a></li>
<li>Legal notice (Impressum): <a href="https://reportedip.de/impressum/" rel="nofollow ugc">reportedip.de/impressum</a></li>
<li>Terms of use: <a href="https://reportedip.de/nutzungsbedingungen/" rel="nofollow ugc">reportedip.de/nutzungsbedingungen</a></li>
<li>Privacy policy: <a href="https://reportedip.de/datenschutzerklaerung/" rel="nofollow ugc">reportedip.de/datenschutzerklaerung</a></li>
<li>Source code: <a href="https://github.com/reportedip/reportedip-hive-light" rel="nofollow ugc">github.com/reportedip/reportedip-hive-light</a></li>
<li>Contact: <a href="mailto:1@reportedip.de" rel="nofollow ugc">1@reportedip.de</a></li>
</ul>
<p>You can switch back to Local Shield mode at any time in <em>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> ReportedIP<br />
Hive <span aria-hidden="true" class="wp-exclude-emoji">→</span> Connection</em>. Doing so stops all external traffic immediately.</p>
<h3>Bundled assets</h3>
<p>This plugin ships every stylesheet and script it needs inside the plugin<br />
folder. <strong>No CDN, no Google Fonts, no remote stylesheets, no remote scripts<br />
are loaded</strong> — every asset URL begins with the plugin’s own<br />
    wp-content/plugins/reportedip-hive/ path.</p>
<p>The full list of bundled, locally-served assets:</p>
<ul>
<li><code>assets/css/design-system.css</code> — design tokens and components used on<br />
every plugin admin page.</li>
<li><code>assets/css/admin.css</code> — admin-page overrides on top of the design<br />
system.</li>
<li><code>assets/css/wizard.css</code> — standalone styles for the first-run setup<br />
wizard.</li>
<li><code>assets/js/admin.js</code> — handles tab switching and the AJAX<br />
“Test connection” button. Its only network call is <code>fetch()</code> against<br />
WordPress’ own <code>admin-ajax.php</code> (same origin); no third-party endpoint<br />
is contacted.</li>
<li>Inline SVG icons (the shield logo, the menu icon, and trust-badge<br />
glyphs) are emitted from PHP via <code>wp_kses()</code> with an explicit allow-list<br />
— no <code><img></code> element points at an external host.</li>
</ul>
<p>The complete list of files distributed in the WordPress.org ZIP is<br />
visible at <em>Plugins <span aria-hidden="true" class="wp-exclude-emoji">→</span> Plugin File Editor</em> once the plugin is installed.</p>
<h3>Third-party services and licences</h3>
<ul>
<li><strong>GPLv2 (or later) licence text</strong> is bundled with the plugin in the<br />
  LICENSE file at the plugin root and is also referenced from the<br />
plugin header (<code>License URI: https://www.gnu.org/licenses/gpl-2.0.html</code>).</li>
<li><strong>No third-party PHP, JavaScript, or CSS libraries are bundled</strong> with<br />
the plugin. There is no Composer <code>vendor/</code> directory, no jQuery copy,<br />
no minified third-party bundle. WordPress itself supplies any global<br />
scripts (<code>jquery</code>, <code>wp-list-table</code>, etc.) and the plugin only depends<br />
on WordPress core APIs.</li>
<li>The only external HTTP service the plugin can talk to is the<br />
  https://reportedip.de/wp-json/reportedip/v2/ API, and only when the<br />
administrator has explicitly enabled Community Network mode — see<br />
the “External services” section above for the full data flow.</li>
</ul>
<h3>Privacy</h3>
<ul>
<li>IP addresses are processed under GDPR Art. 6(1)(f) (legitimate interest in network security).</li>
<li>Usernames are stored as a salted SHA-256 hash; plain-text values are never persisted or transmitted.</li>
<li>In Local Shield mode (default) no data leaves your server.</li>
<li>In Community Network mode the data listed above is sent to reportedip.de.</li>
<li>Data retention is configurable in <em>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Privacy</em>. The default attempt window is 15 minutes; the API queue retention is 7 days.</li>
<li>Activate “Delete all data on uninstall” in <em>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Privacy</em> to remove all plugin tables and options when the plugin is deleted.</li>
</ul>
<h3>Disclaimer</h3>
<p>ReportedIP Hive Light is provided “as is”, without warranty of any kind, express or<br />
implied, including but not limited to warranties of merchantability, fitness<br />
for a particular purpose, and non-infringement. The author shall not be liable<br />
for any claim, damages, or other liability arising from the use of this<br />
software (this is the standard GPLv2-or-later disclaimer; see the LICENSE<br />
file for the full text).</p>
<p>The plugin provides defense-in-depth against brute-force and password-spray<br />
login attacks. It does <strong>not</strong> replace strong passwords, two-factor<br />
authentication, server-level firewalls, or web-application firewalls. No<br />
single security measure offers a 100 % guarantee against compromise. You<br />
remain responsible for the overall security posture of your WordPress site.</p>
<p>The optional Community Network mode forwards data to the third-party service<br />
operated at https://reportedip.de — see the “External services” section<br />
above for the full data flow. Site operators that enable Community Network<br />
mode are responsible for assessing the lawful basis under their applicable<br />
data-protection regime (in the EU, GDPR Art. 6(1)(f) — legitimate interest<br />
in network security — typically applies) and for updating their own privacy<br />
policy accordingly.</p>


ReportedIP Hive Light

Lightweight brute-force login protection with optional community-powered IP reputation checks.

miniOrange

miniorange

<p>Limit Login Attempts provides a comprehensive security package to secure your site. We provide  Limit login attempts, Brute force Protection, Google reCAPTCHA, Spam Protection, Rename Login URL, IP blocking, DOS protection, Login Security, Rate Limiting, and traffic blocking to secure your site against bots.<br />
Limit Login Attempts will protect from the advanced brute force by Limit login, Ip blocking, rename login URL, and protection from spam/bot by Google Recaptcha.</p>
<h4>Features :-</h4>
<h4>LIMIT LOGIN ATTEMPTS</h4>
<p>Limit Login Attempts to protect your site from attacks that try to gain access/login to a site with random usernames and passwords. A Brute Force Attack is the simplest kind of method to gain access to a website. You can limit the login attempts made by an IP and block it as well. <a href="https://security.miniorange.com/login-and-spam-protection/" rel="nofollow ugc">Limit Login Attempts</a></p>
<h4>LOGIN SECURITY</h4>
<p>We help you protect your website against brute force login attacks by blocking an IP address of the hacker after a specified limit of failed login attempts.<br />
When using Limit Login Attempts, you can block the user after certainly failed login attempts thus providing extra login security.</p>
<h4>SPAM PROTECTION</h4>
<p><a href="https://security.miniorange.com/login-and-spam-protection/" rel="nofollow ugc">Spam protection</a> protects your site using Google reCAPTCHA.</p>
<h4>Rename Login URL</h4>
<p>Every website has default login URLs, which all hackers, bots, and malicious attackers are aware of. Once they reach your login page, they only need to guess your password to gain access, which is why protecting your site’s login page by Rename login URL is critical for its security.</p>
<h4>Google Recaptcha</h4>
<p>Google Recaptcha secures you from Brute force attacks on the login and registration page.</p>
<h4>BRUTE FORCE ATTACKS PROTECTION</h4>
<p>By default, WordPress allows users to try different passwords as many times as they want, this is also known as a brute force attack. However, you can change this and add an extra layer of login security to protect your site.<br />
Brute Force Limit Login Protection with IP Blocking security help you monitor login attempts from your users and hackers. We keep track of user’s login attempts and we send alerts to administrators for unusual activities if someone exceeds allowed failed login attempts.</p>
<h4>BLOCK REGISTRATIONS FROM FAKE USERS</h4>
<p>Spam protection of Limit Login Attempts helps you detect suspicious email addresses instantly and provides a means for effective spam protection.<br />
* Realtime Global IP blocking  – It protects your website from malicious IPs and lets the genuine traffic on your WordPress.<br />
* Rate Limiting  – It controls the number of incoming requests from a specific IP to your website<br />
* Login Security – Limit Login Attempts and track user login attempts<br />
* Anti Spam Protection: Spam protection protects your website from spammers by using  google Recaptcha for comments<br />
* User Registration Security – Disallow Disposable / Fake email addresses<br />
* Brute Force Login / Attacks Protection (Login Security)  – We keep track of users’ login attempts and we send alerts to administrators for unusual activities if someone exceeds allowed failed login attempts.<br />
* IP Blocking – Manual and automatic blocking of IPs ( Blacklisting and whitelisting included ).<br />
* Protection for WordPress files – We provide you the option to prevent access to users from browsing directory content and editing files from WP Dashboard (Themes and plugins).<br />
* Google reCAPTCHA protection for login, and registration.</p>
<h4>Advanced Features :-</h4>
<ul>
<li>Advanced Blocking  – Block users based on: IP range, Country, Browser / User-Agent, Referer, and HostName (DNS)</li>
<li>Htaccess Website Security Protection- Secure your website from unintended users with access website security protection which blocks user requests on the server(apache) level. <a href="https://security.miniorange.com/htaccess-vs-plugin-level-firewall-on-wordpress/" rel="nofollow ugc">htaccess vs firewall</a></li>
<li>Comment SPAM Filter and Site SPAM Check/Spam Protection – We check if your website is generating SPAM to protect your website from getting blocked by search engines.</li>
<li>SPAM Protection and google reCAPTCHA for comments – Google reCAPTCHA protects your website from spam and abuse. Google reCAPTCHA uses an advanced risk analysis engine and adaptive google reCAPTCHAs to keep automated software from engaging in abusive activities on your site.</li>
<li>Notification to admin and end users  – Send Email Alerts for IP blocking and unusual activities with a user account</li>
<li>DOS (Denial of service) attacks protection   – Protect your resources from DOS attacks by slowing down attackers by delaying response and increasing delay in each of his requests and eventually blocking them entirely.</li>
<li>Country Blocking –   If you have a website that gets inundated with SPAM or hacking attempts from visitors or bots originating from certain countries we can help you block those attempts.</li>
</ul>


Limit Login Attempts

Unable to use this plugin without registration. You should mention it in description. I have to give one star to this app, because that's not a fair play.

Account required

Limit Login Attempts with IP blocking, brute force protection, Google recaptcha on login as well as registration from spam protection, rename login ur …

ReportedIP Hive Light vs Limit Login Attempts