Predax Security is a VPN, proxy, Tor and bot blocker for WordPress that doesn’t stop there: a built-in firewall, login-lockout protection, country blocking and spam and disposable-email rejection are all included, switch by switch. Once visitor screening is switched on, it checks every visitor’s IP
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 5.8 and PHP 7.4.
SourceWordPress plugins · Nov 14, 2026
01 / Source details
Aboutthistool.
Predax Security is a VPN, proxy, Tor and bot blocker for WordPress that doesn’t stop there: a built-in firewall, login-lockout protection, country blocking and spam and disposable-email rejection are all included, switch by switch. Once visitor screening is switched on, it checks every visitor’s IP address as they arrive and turns away the ones you don’t want — before they can log in, register, comment or load a page.
Most attacks on WordPress sites — brute-force logins, fake registrations, comment spam, vulnerability scans — arrive over VPNs, open proxies, Tor or rented servers. Predax spots those connections in real time, gives each IP a 0–100 risk score, and blocks by the rules you choose.
See what Predax knows about your own IP — free, no signup.
Off by default. A fresh install sends nothing anywhere. Pick a protection level in the setup wizard and the plugin starts working; until then it does nothing.
What it blocks
VPNs, proxies and Tor — anonymised visitors, if you choose to block them
Datacenter IPs — servers pretending to be people
Known bad IPs — addresses flagged in a continuously updated threat database
Countries and regions you don’t serve
Attack requests — a built-in firewall stops injection, scanner and file-probe attempts
Brute-force logins — repeated failures are locked out, faster for risky addresses
Fake signups and spam — disposable email addresses and bot comments are rejected
Scrapers rotating addresses — optional fingerprint-rotation detection spots one browser arriving from many different addresses (off by default)
Every one of these is a switch. Turn on what you need.
Control AI and SEO crawlers
Decide whether GPTBot, ClaudeBot, PerplexityBot or AhrefsBot can access your site. Predax checks each crawler’s real network, not a user-agent header anyone can fake — so a crawler that ignores robots.txt is still turned away. Search engines such as Google and Bing are allowed by default.
Verified search engines are never blocked by your VPN, datacenter, country or risk rules, so screening can’t cost you search traffic.
Wrongly-blocked visitors can tell you. Their report lands in the Threat Log with the full risk detail beside it. Nothing is unblocked until you decide.
One-click allow-listing from the Threat Log puts a genuine reader back in as fast as they were turned away.
Also included
Security dashboard with live activity and top targeted paths · Threat Log with CSV export · Custom branded block page · IP and CIDR allow/deny lists · XML-RPC and REST API protection · Settings import/export · WP-CLI commands for automation · Safe mode, to get back in if you ever lock yourself out
Free plan
Click Connect with Predax in the setup wizard and your free account and API key are created for you — nothing to copy or paste. The free plan includes 5,000 IP checks a month (1,000 a day) with full VPN, proxy, Tor and datacenter detection. No credit card.
Christmas offer: sign up before 31 December 2026 and your account starts on the Starter plan (100,000 checks a month, 5,000 a day) free for 2 months. It then moves to the free plan on its own. No card is needed and nothing is ever charged.
Verified search engine crawlers are never counted against your allowance, so being crawled by Google or Bing costs you nothing.
Busier sites can move to a paid plan for a bigger monthly allowance — same plugin, same settings, same key.
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; their browser timezone (on the front end when visitor screening is on, and on the login page when login protection is on); and, when disposable-email screening is enabled, the domain part of the email address entered at registration (for example “gmail.com”) — never the email address itself, and never the part before the @. The mailbox-level checks (role account, random-looking name) run locally on your own server. When it is sent: On each page load, login attempt, registration, or comment submission, subject to your configured protection settings. IP results are cached for up to 1 hour and email-domain results for up to 6 hours, so repeat visits 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
Email Domain Screening (only when disposable-email screening is enabled)
Used to check whether the email provider entered at registration is a disposable/throwaway service, against a server-side list of thousands of domains (the plugin’s built-in list covers only ~50).
What is sent: the domain part of the registration email address only — for example gmail.com . The email address itself is NEVER sent: the part before the @ does not leave your site, and the mailbox-level checks (role account, random-looking name) run locally in PHP on your own server. When it is sent: during user registration, and only while the Disposable Email Addresses setting is set to Flag or Block. If the API is unreachable, the plugin falls back to its built-in local list and the registration proceeds normally. Email-domain results are cached for up to 6 hours per domain. Endpoint: POST https://predax.io/api/v1/validate/email Plan usage: email-domain lookups count against your Predax plan allowance, the same as IP checks. Results are cached per domain for 6 hours and the built-in list is checked first, so in practice this is roughly one lookup per new email provider your visitors use. 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 is included in the API request when login protection is on.
Fingerprint Rotation Detection
Off by default. When switched on (Settings → Fingerprint Rotation), the plugin reads the visitor’s request headers – user agent, browser client hints, accepted languages, encodings and content types – and turns them into a short one-way hash on your own server. It keeps, in WordPress transients, only that hash and truncated one-way hashes of the addresses it was seen from, for up to 30 minutes. No header text and no raw IP address is stored by this feature, and nothing from it is sent to Predax. When it blocks or challenges a visitor, the Threat Log records that request like any other rule does.
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 visitor screening or login protection is on. 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 ente
See it in action
Screenshots & previews.
A Tor visitor blocked before reaching the site: the branded block page every high-risk visitor sees, with the block reason.Settings page — configure API key, risk threshold, and protection typesThreat log — view all blocked events with IP, reason, risk score, and timestampDashboard widget — at-a-glance threat stats on the WordPress dashboardCountry blocking — select countries and regions to allow or denySetup Wizard — pick a protection level (Monitor Only, Recommended, or Strict) in one step"Predax Protection This Week" — a native WordPress dashboard widget summarizing blocked threats by categoryDetection Modes — VPN, proxy, Tor, malicious-IP, and datacenter blocking, each independently switchableThreat Log with reported access problems — visitors blocked by a category rule can tell you they are genuine; each report shows the risk detail so you can allow the IP in one click, or dismiss itCrawler Policy — allow verified search engines while deciding separately on AI crawlers (GPTBot, ClaudeBot, PerplexityBot) and SEO crawlers. Enforced by each operator's published IP ranges, not the spoofable user-agent header.
02 / Source details
Gettingstarted.
From your WordPress dashboard (recommended)
01Go to Plugins → Add New Plugin in your WordPress admin
02Search for “Predax Security”
03Click Install Now , then Activate
04The setup wizard launches automatically — click “Connect with Predax” to create your free account and link your API key in one click (or paste in an existing key manually), then choose a protection level
05Go to Predax Security in the admin sidebar to view the security dashboard, and Settings to fine-tune protection types, risk thresholds, and advanced features
Manual installation
06Download the plugin ZIP from this page and upload it via Plugins → Add New Plugin → Upload Plugin (or extract the ipsentry-security folder to /wp-content/plugins/ )
07Activate the plugin through the Plugins menu and follow the setup wizard
03 / Source details
Frequently asked questions.
How do I block AI bots like GPTBot or ClaudeBot from my content?
Switch off “Allow AI crawlers” in Settings → Protection → Crawler Policy. Requests coming from the IP ranges published by OpenAI (GPTBot, OAI-SearchBot, ChatGPT-User), Anthropic (ClaudeBot) and Perplexity (PerplexityBot) then receive a 403 instead of your content. Search engines and SEO crawlers have their own separate switches, so this changes nothing about how Google or Bing see your site.
Isn’t robots.txt enough to stop AI crawlers?
robots.txt is a request that a crawler chooses to honour, and nothing enforces it. Blocking by user-agent is no better, because the user-agent is just a header any script can set to anything. Predax checks whether the request genuinely comes from an IP range the crawler’s operator publishes, and blocks on that verified identity instead. Crawlers that publish no ranges at all are judged by the normal bot and risk rules.
Will blocking AI or SEO crawlers hurt my Google rankings?
No. The three switches are independent: blocking AI or SEO crawlers has no effect on search engines, which stay allowed — and exempt from your other category rules — unless you deliberately turn the search-engine switch off. The settings page warns you clearly if you do.
How is this different from Wordfence or other security plugins?
It solves a different problem — and runs happily alongside them. Scanner-based plugins like Wordfence or Solid Security focus on malware scanning and firewall rules: they look at what a request does once it reaches your site. Predax Security looks at who is connecting : it identifies anonymised and high-risk IPs (VPNs, proxies, Tor, datacenter ranges) in real time using a commercial IP intelligence database, and blocks them before they attempt anything. Many sites run Predax Security alongside a scanner-based plugin — Predax filters out the anonymous, high-risk traffic; the scanner watches what gets through.
Will this slow down my site?
No. API results are cached in the WordPress database for between 5 minutes and 1 hour per IP, following the lifetime the API recommends for that address. After the first check, returning visitors are served from cache with no API call.
Does this block all VPN users?
Only if you enable VPN blocking. By default the plugin is set to monitor VPN traffic (log it but not block it). You control exactly which threat types trigger a block.
What happens to blocked visitors?
By default they see a standard WordPress error page with a 403 status code. You can enable the Custom Block Page option to show a branded page with your own message and a support link.
Does it work with Cloudflare?
Yes. The plugin reads the CF-Connecting-IP header automatically when Cloudflare is detected, so the real visitor IP is used rather than the Cloudflare proxy IP.
Is the free plan enough for a small site?
For most small sites, yes. The free plan provides 1,000 checks per day. With 1-hour caching, this covers approximately 1,000 unique visitors per day. Returning visitors within the hour use cached results and don’t count against your quota.
Verified search engine crawlers don’t count either. When Googlebot, Bingbot or a similar crawler visits, the check is free — so a site that is crawled heavily doesn’t lose its allowance to search engines. Verification is against each search engine’s own published addresses, so a bot merely claiming to be Googlebot is still counted (and still blocked if you have fake-bot protection on).
Can I whitelist my own IP?
Yes. Go to Predax Security → Settings → Protection → IP Allow-list . It shows the address your site currently sees you as, with a button to add it, and you can add any single IP or CIDR range. You can also use the Allow button next to an entry in the Threat Log. Allow-listed addresses are never blocked.
I’ve locked myself out. How do I get back in?
Turn on safe mode. Add define('IPSENTRY_SAFE_MODE', true); to wp-config.php, or run wp ipsentry safe-mode on . Predax Security then blocks no one, without being deactivated and without changing any of your settings. Log in, add your own address to the allow list, then remove the line (or run wp ipsentry safe-mode off ). A red notice in wp-admin reminds you while safe mode is on.
Does it protect the WooCommerce checkout?
The base security plugin protects logins and registrations. For WooCommerce checkout protection (fraud scoring, country mismatch, order velocity, auto hold), use the companion Predax Fraud Guard for WooCommerce plugin (also on WordPress.org).
What data is sent to the API?
The visitor’s IP address, and their browser timezone whenever visitor screening or login protection is switched on. A temporary cookie is used to pass the timezone from the browser to the server. If you enable disposable-email screening, the domain part of the email address entered at registration (for example “gmail.com”) is also checked — never the address itself, and never the part before the @. No page content or other personal user data is transmitted. See the Third Party Services section below for full details.
Will this block my real visitors or hurt my SEO?
No. Verified search engine crawlers — Googlebot, Bingbot and others confirmed by reverse DNS — are never blocked by category rules, so your search rankings are not affected.
For human visitors, the plugin errs toward telling you rather than guessing. The dashboard separates attacks stopped from visitors turned away by your own category rules, so you can see at a glance whether your settings are too strict. Anyone blocked by a category rule can tell you they are genuine, and you can allow their IP in one click.
If you run a blog, news or download site, we suggest the Recommended preset rather than Strict: a meaningful share of ordinary readers browse via a VPN.
FinderPress Media Auditor helps site administrators scan for broken images, missing Media Library files, unreachable media URLs, and other media issues across WordPress content. Use it to audit images, video, audio, PDFs, featured images, and attachment files without sending scan data to an external
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati
