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.

Carrero

<p>ES Football Bypass for Cloudflare is a WordPress plugin created by David Carrero Fernandez-Baillo to help Spanish website owners protect their legitimate sites from collateral damage caused by mass IP blocks ordered during football matches. The project is open source (GPLv2) and available on GitHub: https://github.com/dcarrero/cf-football-bypass</p>
<p>The plugin automatically monitors football events in Spain by querying hayahora.futbol and, based on the result, manages Cloudflare DNS records to toggle between Proxied and DNS Only modes. This prevents legitimate visitors from being affected by judicial blocks targeting pirate football streaming.</p>
<h4>The Problem</h4>
<p>In Spain, during football matches, mass IP blocks are enforced by judicial orders to combat pirate streaming. These blocks also affect legitimate websites that have nothing to do with football, causing traffic and revenue losses.</p>
<h4>The Solution</h4>
<p>When football is detected:<br />
– Automatically disables the Cloudflare proxy for selected DNS records<br />
– Your website switches to DNS Only mode, avoiding potentially blocked Cloudflare IPs<br />
– After the configured cooldown period, automatically re-enables the Cloudflare proxy</p>
<h4>Two interface modes: Simple and Advanced</h4>
<p>Since version 1.9.6 the plugin ships with two interface modes that you can switch from Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Interface mode:</p>
<ul>
<li><strong>Simple</strong> (default on new installs, recommended for agency/client sites): shows only the essentials. Block status, manual proxy ON/OFF buttons, basic email notifications on state changes, Cloudflare credentials, bypass behavior and uninstall options. Logs, feed diagnostics panel, staleness threshold, log retention and external cron token are hidden to reduce noise for non-technical users. Logs are still written to disk — you can always switch to Advanced if you need to diagnose something.</li>
<li><strong>Advanced</strong> (default on upgrades from earlier versions): shows everything, including the full feed diagnostics panel, the logs tab, the technical console and the advanced options. Ideal for developers, power users, or when you need to diagnose behavior or configure a server-side cron.</li>
</ul>
<p>There is also a standalone subpage “Is there football now?” that simply answers YES or NO based on the public feed, with a short note about the data source. Perfect to share the link with a final client that just wants to know if there are active blocks right now.</p>
<h4>Key Features</h4>
<p>Full Automation<br />
– Automatic monitoring every X minutes (configurable 5-60 min)<br />
– Automatic bypass activation/deactivation<br />
– Integrated WordPress cron system</p>
<p>Dual Cloudflare Authentication Support<br />
– Global API Key (traditional)<br />
– API Token with specific permissions (more secure)</p>
<p>Granular Control<br />
– Specific DNS record selection (A, AAAA, and CNAME)<br />
– Configurable bypass duration (60-600 minutes)<br />
– Customizable cooldown interval after disabling Cloudflare<br />
– Manual control for special cases</p>
<p>Informative Dashboard<br />
– Real-time football status<br />
– Last check performed<br />
– Bypass status (active/inactive)</p>
<p>Additional Tools<br />
– Cloudflare connection test button<br />
– Manual football status check<br />
– Manual activation/deactivation buttons<br />
– Detailed logging for debugging and auditing<br />
– Protected endpoint for external cron</p>
<h3>External Services</h3>
<p>This plugin connects to the following external services:</p>
<h4>hayahora.futbol</h4>
<p>The plugin periodically queries the endpoint https://hayahora.futbol/estado/data.json to check whether there are active IP blocks during football events in Spain. This query runs automatically based on the configured cron interval (default: every 15 minutes) and can also be triggered manually from the admin panel.<br />
– Data sent: An HTTP GET request with the site’s home URL in the User-Agent header. No personal or visitor data is transmitted.<br />
– URL: https://hayahora.futbol/<br />
– About the service and privacy: https://hayahora.futbol/#sobre-los-bloqueos<br />
– Terms of use: The service is free, open source, and does not collect personal data from plugin users or their visitors.</p>
<h4>Cloudflare API</h4>
<p>The plugin uses the official Cloudflare API (https://api.cloudflare.com/client/v4/) to read DNS records and toggle the proxy status (Proxied/DNS Only) for selected records. It requires API credentials that you provide in the plugin settings. Credentials are stored in the WordPress database and sent via HTTPS headers to Cloudflare.<br />
– Data sent: API credentials (in headers), DNS record modifications (record ID, type, name, content, proxied status).<br />
– URL: https://api.cloudflare.com/<br />
– Terms of Service: https://www.cloudflare.com/terms/<br />
– Privacy Policy: https://www.cloudflare.com/privacypolicy/</p>
<h4>Server IP Detection Services</h4>
<p>The plugin detects your server’s outgoing IP address (displayed in the Settings page) by querying three public services. Only the server’s own IP is returned; no personal or visitor data is transmitted. Results are cached for 1 hour.<br />
– https://api.ipify.org/ – Provided by ipify. Privacy Policy: https://www.ipify.org/<br />
– https://checkip.amazonaws.com/ – Provided by Amazon Web Services. Privacy Policy: https://aws.amazon.com/privacy/<br />
– https://icanhazip.com/ – Provided by Cloudflare. Privacy Policy: https://www.cloudflare.com/privacypolicy/</p>
<h4>Affiliate Links</h4>
<p>The plugin’s operation page includes affiliate links clearly marked with “(aff)” to VPN services and security tools. These links are optional and do not affect the plugin’s functionality.</p>
<h3>Cron and Automation</h3>
<h4>How does the cron system work?</h4>
<p>The plugin uses WordPress internal cron (wp_cron) which runs when there are visits to the website. This is usually sufficient for most sites.</p>
<h4>What if my site has low traffic and cron doesn’t run regularly?</h4>
<p>Go to Settings > ES Football Bypass for Cloudflare and copy the token from the “External cron” section. With that token you can set up a real server cron:</p>
<p>*/15 * * * * curl -s “https://yourdomain.com/wp-cron.php?cfbcolorvivo_cron=1&token=YOUR_TOKEN_HERE” > /dev/null 2>&1</p>
<p>You can regenerate the token by clearing the field and saving settings (a new one is generated). This endpoint only runs the plugin check, without depending on visits.</p>
<h4>What is the “Cooldown after disabling Cloudflare”?</h4>
<p>This is the waiting time (default 60 minutes) that the plugin respects before checking if Cloudflare can be re-enabled after detecting a block. During this period, the proxy remains in “DNS Only” mode even if the JSON stops marking the domain, avoiding rapid activation/deactivation cycles.</p>
<h4>How do I verify that cron is working correctly?</h4>
<p>In the Operation tab, click “WP-Cron Diagnostics” to see the next execution and the result of the last check. You can also review the integrated logs.</p>
<h3>Logs and Auditing</h3>
<h4>Where can I see the action history?</h4>
<p>In the ES Football Bypass for Cloudflare > Logs menu. It shows the latest automatic executions (internal or external cron) and manual actions with date, detail, and user.</p>
<h4>Can I disable logging?</h4>
<p>Yes. In Settings > ES Football Bypass for Cloudflare you can disable logging or adjust retention days (minimum 1). Logs are stored in the uploads directory under <code>es-football-bypass-for-cloudflare/logs/</code> protected with .htaccess.</p>
<h4>How do I verify that cron is working correctly?</h4>
<p>You can check if it’s scheduled in Tools > Site Health > Info > Scheduled Events, looking for the ‘cfbcolorvivo_check_football_status’ event. You can also review WordPress error logs where the plugin records all its actions.</p>
<h3>Server Requirements</h3>
<ul>
<li>WordPress 5.0 or higher</li>
<li>PHP 7.4 or higher</li>
<li>PHP Extensions: curl, json</li>
<li>Permissions: Ability to make outbound HTTP requests</li>
<li>Cron: Functional WordPress cron system</li>
</ul>
<h3>Support</h3>
<ul>
<li>Author: David Carrero Fernandez-Baillo</li>
<li>Website: https://carrero.es</li>
<li>Contact: https://carrero.es/contacto/</li>
</ul>
<p>If you need help, send a direct message on X or use the contact form. Issues and improvements are also welcome in the repository: https://github.com/dcarrero/cf-football-bypass</p>
<p>This plugin was born from the real need to protect legitimate websites from the mass blocks affecting the Spanish digital industry during sporting events.</p>
<h3>Specific Use Cases</h3>
<p>High Traffic Sites<br />
– Allows selecting only critical records (www, root domain)<br />
– Keeps other services (mail, ftp, etc.) always proxied<br />
– Minimizes impact on CDN and cache</p>
<p>Sites with Multiple Subdomains<br />
– Granular control per subdomain<br />
– Different strategies for different services<br />
– Total configuration flexibility</p>
<p>Emergencies and Manual Override<br />
– Manual control buttons for special situations<br />
– Does not depend solely on automatic detection<br />
– Allows quick reaction to failures</p>
<h3>License</h3>
<p>GPLv2 or later. You are free to use, modify, and distribute this plugin under the terms of the GPL.</p>


ES Football Bypass for Cloudflare

Automatically manages Cloudflare configuration during football matches to avoid mass IP blocks affecting legitimate websites in Spain.

ReportedIP Hive Light vs ES Football Bypass for Cloudflare