Behnam Moradi

<p><strong>NetShield – Request Blocker</strong> helps WordPress administrators identify and block external HTTP requests that the server cannot reach due to network restrictions, firewalls, or internet access limitations.</p>
<p>On restricted or internal networks, WordPress and plugins often make dozens of outbound HTTP requests on every page load (to Google Fonts, CDNs, analytics services, etc.). When those endpoints are unreachable, each request stalls and waits for a timeout — silently slowing your site down.</p>
<p>NetShield solves this by:</p>
<ol>
<li><strong>Scanning</strong> a curated list of common external endpoints using the WordPress HTTP API.</li>
<li><strong>Identifying</strong> which ones are unreachable from your server.</li>
<li><strong>Blocking</strong> future requests to those endpoints via WordPress’s <code>pre_http_request</code> filter — so they never wait for a timeout again.</li>
</ol>
<h4>Key Features</h4>
<ul>
<li><strong>On-demand network scanner</strong> — test 27 common external endpoints (WordPress.org, Google APIs, CDNs, social platforms, analytics).</li>
<li><strong>Selective blocking</strong> — choose which unreachable addresses to block; toggle any entry on/off without deleting it.</li>
<li><strong>Manual entries</strong> — add any domain, URL, or IP address to the block list manually.</li>
<li><strong>Context-aware rules</strong> — block requests only on the admin side, only on the frontend, or both.</li>
<li><strong>Bulk actions</strong> — enable, disable, or delete multiple entries at once.</li>
<li><strong>Graphical settings page</strong> — modern, tab-based admin UI with real-time stats, toast notifications, and toggle switches.</li>
<li><strong>Master switch</strong> — enable or disable the plugin’s blocking functionality instantly without deactivating it.</li>
<li><strong>Auto-block on scan</strong> — optionally mark all unreachable URLs as blocked automatically after each scan.</li>
<li><strong>Transient caching</strong> — blocked URL lists are cached in WordPress transients for optimal performance.</li>
<li><strong>Clean uninstall</strong> — all data (database table, options, transients, capabilities) is removed on plugin deletion.</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li>WordPress sites hosted on intranets or servers with restricted outbound internet access.</li>
<li>Development environments behind corporate firewalls.</li>
<li>Any WordPress site where external HTTP request timeouts are causing slow admin or frontend load times.</li>
</ul>
<h4>Technical Details</h4>
<ul>
<li>Uses WordPress <code>pre_http_request</code> filter for zero-overhead blocking (no request is even initiated).</li>
<li>Custom database table (<code>wp_nsb_blocked_urls</code>) for storing and managing blocked entries.</li>
<li>REST API endpoints (<code>/wp-json/netshield/v1/</code>) for all admin UI interactions.</li>
<li>PHP 8.1+ with strict typing, readonly DTOs, and backed enums.</li>
<li>No external dependencies — no Composer required, built-in PSR-4 autoloader.</li>
</ul>


NetShield – Request Blocker

Scans and blocks unreachable or unwanted external HTTP requests to dramatically optimize WordPress loading speed on restricted networks.

Maikuolan

<p>CIDRAM (Classless Inter-Domain Routing Access Manager) is a PHP script designed to protect websites by blocking requests originating from IP addresses regarded as being sources of undesirable traffic, including (but not limited to) traffic from non-human access endpoints, cloud services, spambots, scrapers, etc. It does this by calculating the possible CIDRs of the IP addresses supplied from inbound requests and then attempting to match these possible CIDRs against its signature files (these signature files contain lists of CIDRs of IP addresses regarded as being sources of undesirable traffic); If matches are found, the requests are blocked.</p>
<h3>Requirements</h3>
<ul>
<li>PHP >= 7.2.0</li>
<li>PCRE</li>
</ul>
<h3>Updating</h3>
<p>Note: CIDRAM does not interact in any way with your database, and stores its own configuration settings, customisations, and related materials as flatfiles within its own directory. If you’ve not changed any of the default configuration settings and if you’re not using any customisations for this plugin, updating normally via the plugins dashboard, without need for any additional steps, should be sufficient and shouldn’t cause any problems. However, if you’ve modified the configuration settings for CIDRAM, or if you’ve made any customisations, I would recommend making backups of all of these prior to updating, due to that updating will overwrite all settings and customisations (after updating, you can then restore your customisations from your backups). Alternatively, if you update via the CIDRAM front-end updates page, all settings and customisations should be preserved.</p>


CIDRAM

CIDRAM: A PHP-level CIDR/IP-based firewall solution.

NetShield – Request Blocker vs CIDRAM