Native registration & comments / VERSION 1.0.0

WordPress Proxy & VPN Detection Plugin

Add network checks to native WordPress registration and comments. Download the ProxyRadar plugin with monitor mode, IP rules and explicit error handling.

Source and setup instructions included · Published October 28, 2026

What the WordPress plugin protects

The plugin checks native WordPress registration and comment submissions. You can monitor the result, block a matching network or ask the visitor to retry when detection is unavailable. It does not intercept logins, admin access, WooCommerce checkout, multisite signup or third-party form plugins.

Install and connect

1. Download the ZIP. On a staging WordPress site, open Plugins → Add New → Upload Plugin, select the ZIP, install and activate it. PHP 8.0+ and WordPress 6.0+ are required.
2. Open Settings → ProxyRadar. Enter your API key, or define PROXYRADAR_API_KEY in wp-config.php. A blank key field keeps the saved key; the key is never printed back into the page.
3. Review your privacy notice, then enable checks and leave the mode set to Monitor. When enabled, the plugin sends the visitor IP to ProxyRadar; it does not send names, emails, passwords or comment content.
4. Submit a native registration or comment from a separate browser. Check the latest anonymous decision in the settings page. Existing administrator sessions are excluded.
5. Review your results and switch to Enforce only when your policy is ready. Keep a support path available for legitimate visitors.

Choose what should match

Overall classification includes hosting networks. You can instead match just VPN, Tor, public proxy or hosting flags. Unknown categories do not match a category-only rule, even when the overall classification is positive. Exact IPv4/IPv6 allow and deny lists are supported; allow takes precedence. CIDR rules are not included in this version.

Behind Cloudflare or a reverse proxy

The plugin reads REMOTE_ADDR. Configure your web server to restore the client address only from your trusted reverse proxy, and restrict direct access to the origin where appropriate. Do not enable enforcement while every visitor appears as the same proxy address. The plugin deliberately ignores unverified forwarded headers.

Errors, caching and usage

The request timeout is 15 seconds. Valid positive results are cached for 60 seconds and negative results for 30 seconds in WordPress transients. Failed requests are not cached as negative. Choose Allow on error or Ask to retry on error; retry blocking applies only in Enforce mode. There are no automatic retries. Successful API requests use the normal account quota.

Test and remove safely

Verify both a registration and a comment, an allowed IP, a matching rule and a temporary API failure on staging. In Monitor mode, a deny rule records a would-block result without rejecting the action. Deactivation stops the hooks immediately. Settings remain saved so reactivation does not silently lose your configuration.

All integrations · API reference · Coverage and limitations · Account support