Behnam Moradi

NetShield – Request Blocker helps WordPress administrators identify and block external HTTP requests that the server cannot reach due to network restrictions, firewalls, or internet access limitations.
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.
NetShield solves this by:
<ol>
<li>Scanning a curated list of common external endpoints using the WordPress HTTP API.</li>
<li>Identifying which ones are unreachable from your server.</li>
<li>Blocking 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>On-demand network scanner — test 27 common external endpoints (WordPress.org, Google APIs, CDNs, social platforms, analytics).</li>
<li>Selective blocking — choose which unreachable addresses to block; toggle any entry on/off without deleting it.</li>
<li>Manual entries — add any domain, URL, or IP address to the block list manually.</li>
<li>Context-aware rules — block requests only on the admin side, only on the frontend, or both.</li>
<li>Bulk actions — enable, disable, or delete multiple entries at once.</li>
<li>Graphical settings page — modern, tab-based admin UI with real-time stats, toast notifications, and toggle switches.</li>
<li>Master switch — enable or disable the plugin’s blocking functionality instantly without deactivating it.</li>
<li>Auto-block on scan — optionally mark all unreachable URLs as blocked automatically after each scan.</li>
<li>Transient caching — blocked URL lists are cached in WordPress transients for optimal performance.</li>
<li>Clean uninstall — 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.

filiw

Anti-Captcha is a transparent spam solution that does not require any end-user interaction. 
It is based on a nonce key, which is dynamically inserted using randomly generated (and obfuscated) javascript.
The aim of this plugin is to prevent automated attacks (by bots) on the following WordPress actions:
<ul>
<li>Posting comments</li>
<li>Registering for a new account</li>
<li>Requesting a lost password</li>
</ul>
When a comment is posted without a valid Anti-Captcha token, it shall be instantly marked as spam. This way, you can always manually approve this comment in hindsight if it appeared to be sincere.

Anti-Captcha (anti-spam botblocker)

Anti-Captcha is a transparent spam solution that does not require any end-user interaction.

NetShield – Request Blocker vs Anti-Captcha (anti-spam botblocker)