Gryphon Verified Client IP
Determines the true client IP by verifying Forwarded and similar headers, traversing only trusted proxy hops.
Consider an alternative
Gryphon Verified Client IP shows warning signs in 2026 — compare the alternatives below before installing. Was last updated 6 months ago, and scores 36/100 on our health check.
- Small user base (<10 active installs)
- Very few reviews so far
- Only tested up to WordPress 6.9 (latest is 7.1)
- Needs PHP 8.1 or newer
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Gryphon Verified Client IP stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| Client IP | >100 |
| ip address | >100 |
| proxy | >100 |
| user ip | >100 |
| visitor ip | >100 |
About Gryphon Verified Client IP
From the official readme · v1.2.1Description
Gryphon Verified Client IP determines the client IP by walking the forwarding chain, only trusting addresses that match your configured proxy networks (by CIDR range). It stops at the first untrusted hop, which is the true client IP. The resolved address replaces REMOTE_ADDR early in the WordPress lifecycle, allowing other plugins to use it.
The component is secure by default and only trusted proxies are traversed; spoofed headers are ignored. Both IPv4 and IPv6 are fully supported, including protocol translation.
Multiple header formats are supported including standard RFC 7239 Forwarded, common X-Forwarded-For, Cloudflare CF-Connecting-IP, or any custom header.
The component includes a diagnostics panel that can be enabled to record incoming requests with full header dumps and algorithm step traces for debugging.
For more detail, see the GitHub project site Gryphon WordPress Verified Client IP.
Compatibility Note
If your server uses Apache mod_remoteip or nginx set_real_ip_from, those modules will pre-resolve REMOTE_ADDR from forwarding headers before PHP runs. Disable the web server module and let this plugin handle IP resolution instead, or let it pre-resolve and use this plugin for any additional proxies not covered by the engine.
Installation
From plugin directory
- Go to Site Admin → Plugins → Add Plugin
- Search Plugins for “Gryphon Verified Client IP”
- Click Install Now
- Click Activate
Navigate to Settings → Verified Client IP in the WordPress admin.
Configure with your proxy setup, or accept the defaults if suitable.
Manual installation
- Download the plugin zip file.
- In WordPress Admin, go to Plugins → Add Plugin → Upload Plugin.
- Upload the zip and click Install Now.
- Click Activate Plugin.
Or manually upload the gryphon-verified-client-ip folder to wp-content/plugins/ and activate via the Plugins screen.
Navigate to Settings → Verified Client IP in the WordPress admin.
Configure with your proxy setup, or accept the defaults if suitable.
Frequently asked questions
The plugin has no effect. What should I check?
Check that REMOTE_ADDR matches a trusted proxy in an enabled scheme. Use the Diagnostics tab to record a request and inspect the step trace.
The plugin is a no-op even though my proxies are configured.
Apache mod_remoteip or nginx set_real_ip_from may be pre-resolving the IP before PHP starts. In the Diagnostics tab, if the Remote Address column already shows the visitor’s IP rather than the upstream proxy’s IP, a web-server-level module is the cause. Disable the relevant module or accept that addresses are already partially resolved.
I’m resolving the wrong IP.
Check that your Forward Limit matches the exact number of proxies in your chain. Use the step trace in Diagnostics to see each hop the algorithm evaluated.
Cloudflare is not working.
Enable the Cloudflare scheme and add Cloudflare’s published IP ranges to the trusted proxies list.
Can I extend the plugin with my own code?
Yes. Three hooks are available: Filter vcip_resolved_ip (string $ip, array $steps): string — modify the resolved IP before it replaces REMOTE_ADDR. Filter vcip_trusted_proxies (array $schemes): array — dynamically add or modify proxy schemes before matching. Action vcip_ip_resolved (string $newIp, string $originalIp, array $steps) — fired after REMOTE_ADDR has been replaced.
What happens when the plugin is deactivated?
Deactivation only flushes object caches — no settings or data are removed. Uninstalling the plugin removes all vcip_* options and diagnostic transients.
Is diagnostic data stored permanently?
No. Diagnostic records are stored as WordPress transients with a 24-hour expiry and are automatically removed when you uninstall the plugin. Because the data includes IP addresses and HTTP headers, only record what you need for debugging and clear the data when you are done.
Changelog
Reformat readme.txt to display properly in WordPress plugin library. Add Settings and Guide links to plugins page
1.2.1
- Reformat readme.txt to display properly in WordPress plugin library.
- Add Settings and Guide links to plugins page
1.2.0
- Update plugin display name and slug, again, to Gryphon Verified Client IP.
- Update namespace and package names to Gryphon Verified Client IP.
1.1.0
- Update plugin display name and slug, for WordPress plugin naming requirements, to Essential Verified Client IP.
- Update namespace and package names to Essential Verified Client IP.
1.0.1
- Minor fixes for initial release.
1.0.0
- Initial release of Verified Client IP plugin.
- RFC 7239
Forwarded,X-Forwarded-For, and CloudflareCF-Connecting-IPschemes. - Configurable forward limit and trusted proxy CIDR ranges.
- Proto and Host processing.
- Diagnostics with request recording and step traces.
- Must-use plugin support.
- WordPress hooks:
vcip_resolved_ip,vcip_trusted_proxies,vcip_ip_resolved.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Gryphon Verified Client IP alternatives
All Client IP plugins →| Rank | Plugin | Active installs |
|---|---|---|
| 1 |
|
10+ |
FAQ
Gryphon Verified Client IP: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 16, 2026
Is Gryphon Verified Client IP free?
Yes. Gryphon Verified Client IP is free to download and use from the official WordPress.org plugin directory.
Is Gryphon Verified Client IP safe to use in 2026?
Gryphon Verified Client IP shows warning signs in 2026 — compare the alternatives below before installing. Was last updated 6 months ago, and scores 36/100 on our health check.
How many websites use Gryphon Verified Client IP?
Gryphon Verified Client IP is active on <10 WordPress websites and has been downloaded 361 times since it launched in April 2026. It was downloaded 66 times in the last 30 days.
Does Gryphon Verified Client IP work with WordPress 7.1?
Gryphon Verified Client IP is officially tested up to WordPress 6.9.10, while the latest release is 7.1.3. It may still work, but try it on a staging site first.
What PHP version does Gryphon Verified Client IP need?
Gryphon Verified Client IP requires PHP 8.1 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Gryphon Verified Client IP last updated?
The latest version, 1.2.1, was released on April 13, 2026 (6 months ago).
Who makes Gryphon Verified Client IP?
Gryphon Verified Client IP is developed and maintained by Sly Gryphon.
What are the best alternatives to Gryphon Verified Client IP?
The most popular alternatives to Gryphon Verified Client IP are Client IP Detector Plugin (10+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card