XeroWP
Predax Security – Block VPN, Proxy & Tor Traffic
Predax Security – Block VPN, Proxy & Tor Traffic

Predax Security – Block VPN, Proxy & Tor Traffic

0/5 (0 ratings) — active installs Updated Aug 8, 2026
Brute ForceIP-blockingsecurityTorvpn
Download v1.12.0 Plugin Website
A Tor visitor blocked before reaching the site: the branded block page every high-risk visitor sees, with the block reason.

A Tor visitor blocked before reaching the site: the branded block page every high-risk visitor sees, with the block reason.

Block VPNs, Tor users, proxies, bots, and high-risk visitors before they can attack your WordPress site.

Most WordPress attacks — brute-force logins, fake registrations, comment spam, vulnerability scans — come from anonymised connections: VPNs, open proxies, Tor exit nodes, and rented datacenter servers. Predax Security identifies those visitors the moment they arrive and stops the risky ones at the door, before they can log in, register, comment, or even load a page.

Every visitor IP is checked in real time against a continuously-updated threat intelligence database of known VPN providers, open proxies, Tor exit nodes, datacenter ranges, and web crawlers, and given a 0–100 risk score. You choose exactly what gets blocked — by category, by country, or by risk score threshold.

Privacy-first by design: on a fresh install the plugin is off by default — no visitor data is sent anywhere until you explicitly enable a protection preset via the setup wizard or the Settings → Protection tab.

Key Features

  • Security Dashboard — real-time overview with blocking activity chart, threat breakdown, top targeted paths, protection status, and country analysis
  • Real-time VPN/Proxy/Tor/Datacenter detection — checks every visitor against live threat intelligence
  • Risk score thresholds — block IPs above a configurable risk score (0–100)
  • Country geo-blocking — block or allow specific countries and regions
  • Login protection — block high-risk IPs from attempting to log in
  • Registration protection — stop fraudulent account creation
  • Comment protection — block spam and bot comments at source
  • Visitor protection — optionally check all page visitors (with 1-hour caching to minimise API calls)
  • XML-RPC & REST API protection — extend blocking to XML-RPC calls and REST API requests
  • Disposable email blocking — reject registrations using throwaway email services
  • Custom block page — show a branded 403 page instead of the default WordPress error
  • Whitelist/blacklist — override decisions for individual IPs or CIDR ranges
  • Threat log — view and export all blocked events with IP, reason, and timestamp
  • Event tracking — log successful checks for audit and analytics
  • Settings import/export — back up and restore your configuration as a JSON file
  • WP-CLI commands — manage whitelists, blacklists, and run IP tests from the command line

Free Tier

Click “Connect with Predax” in the setup wizard to create your free account and link your API key automatically — no separate sign-up step, no key to copy or paste. The free plan includes:

  • 1,000 IP checks per day
  • 5,000 IP checks per month
  • VPN, proxy, Tor, and datacenter detection
  • Country and region data

No credit card required.

More Power With Paid Plans

The free tier is plenty for small sites, but busier sites use up the included checks faster. Paid plans raise the monthly limit from 5,000 up to 25,000–25,000,000 IP checks, with higher request rates and bulk lookups. The dashboard shows your live usage each month, so you can see exactly when it’s time to upgrade — same plugin, same settings, just a bigger allowance on your existing API key.

How It Works

  1. You install the plugin and connect your site during the Setup Wizard. Click “Connect with Predax” to create your free account (or log into an existing one) and link your API key automatically — no key to copy or paste. Prefer to do it manually? You can still paste in an existing API key instead.
  2. You pick a protection preset in the Setup Wizard (or enable individual protections from Settings → Protection). This is the explicit opt-in — no data leaves the site until you do this.
  3. A visitor makes a request to your site.
  4. Predax checks their IP against the threat intelligence API (results cached for 1 hour per IP).
  5. If the risk score exceeds your threshold, the visitor is blocked with a configurable message.
  6. All block events are logged in the WordPress database for review.

WP-CLI Commands

wp ipsentry status — show current configuration and threat counts
wp ipsentry test-ip <ip> — run a live API check on any IP
wp ipsentry whitelist add <ip> — add an IP or CIDR to the whitelist
wp ipsentry whitelist remove <ip> — remove from whitelist
wp ipsentry blacklist add <ip> — add an IP or CIDR to the blacklist
wp ipsentry log --limit=20 — view recent threat log entries

Third Party Services

This plugin connects to external services. By installing and activating this plugin you agree to the terms of each service you enable.

Predax API

This plugin transmits visitor IP addresses to the Predax API (https://predax.io) for real-time threat detection and risk scoring.

What is sent: The visitor’s IP address, and optionally their timezone (when timezone mismatch detection is enabled and visitor protection is active).
When it is sent: On each page load, login attempt, registration, or comment submission, subject to your configured protection settings. Results are cached for 1 hour so repeat visits by the same IP do not generate additional API calls.
Who operates the service: Predax (predax.io)
Terms of Service: https://predax.io/terms
Privacy Policy: https://predax.io/privacy

Account Usage Lookup (admin pages only)

Used to show the “API Usage” meter on the plugin dashboard, and only when an API key is saved.

What is sent: your Predax API key (as the authentication header). No visitor data is sent.
When it is sent: when an administrator views the Predax Security dashboard. The result is cached for 1 hour, so at most one lookup per hour regardless of admin page views.
Endpoint: GET https://predax.io/api/v1/auth/usage
Privacy Policy: https://predax.io/privacy

Deactivation Feedback (optional, admin-initiated)

Shown only when an administrator deactivates the plugin from the Plugins screen and chooses to answer the “why are you deactivating?” prompt.

What is sent: the plugin slug, the plugin version, and a single pre-defined reason code you select (e.g. “it blocked real visitors”). No site URL, no email address, no visitor data, and no IP address are sent.
When it is sent: only when you select a reason and click “Send & deactivate”. Clicking “Skip & deactivate” sends nothing at all.
Endpoint: POST https://predax.io/api/v1/feedback/deactivation
Privacy Policy: https://predax.io/privacy

Community Threat Network (opt-in, disabled by default)

The Community Threat Network is opt-in and disabled by default. No block or monitor events are sent to the community network unless you enable it yourself in Settings Predax Security Advanced.

When — and only when — you explicitly enable it, anonymised block and monitor events (containing: IP address, action taken, block reason, country code, and risk score) are sent to the Predax API at predax.io. This data is used to build a shared threat database that improves detection accuracy for all sites in the network. You can turn community reporting back off at any time in the same settings screen.

Google reCAPTCHA

When reCAPTCHA v3 is enabled (Settings Protection reCAPTCHA), this plugin loads the reCAPTCHA script from google.com and sends form submission tokens to google.com/recaptcha for verification. Google may collect data according to their privacy policy. You must provide your own reCAPTCHA site key and secret key.

Google Privacy Policy: https://policies.google.com/privacy
reCAPTCHA Terms: https://policies.google.com/terms

Browser Fingerprinting

When browser fingerprint scoring is enabled (Settings Protection Fingerprint Scoring), this plugin collects screen resolution, timezone, platform string, WebGL renderer, and plugin count from the visitor’s browser on the login page. Fingerprint data is used locally to score bot likelihood and is stored in WordPress only while the login form is being submitted, then discarded. The visitor’s timezone may be included in the API request to detect timezone mismatch when that feature is enabled.

Cookies set by this plugin

All cookies set by this plugin are functional service cookies, not tracking cookies, and are only written when the relevant feature is explicitly enabled by the site administrator:

  • ipsentry_tz — carries the visitor’s browser timezone to the Predax API when timezone-mismatch detection is active. Written from ipsentry-tz.js on the front-end. Expires after 24 hours. SameSite=Lax. Only set when an API key is configured AND visitor or login protection is enabled.
  • ips_jsc — JavaScript challenge solve token. Written from js-challenge.js when a visitor passes the challenge. Expires after 24 hours. SameSite=Lax. Only set when the JavaScript Challenge feature is enabled.

No tracking or advertising cookies are written by this plugin.

By activating this plugin and entering an API key, you agree to the Predax Terms of Service and Privacy Policy. You are responsible for ensuring your use of visitor IP data complies with applicable privacy laws (GDPR, CCPA, etc.) and your own site’s privacy policy.