FindIP Shield for WordPress
The official plugin on WordPress.org adds visitor risk intelligence to any WordPress site — VPN, proxy, Tor, relay, hosting, datacenter, malicious-IP, and network-service flags plus a risk score per session — without reading form values, passwords, or payment fields.
Installation
- In WordPress admin, open Plugins → Add New Plugin, search for FindIP Shield, install and activate.
- Create a Shield site at findip.net → Shield → Sites → New site whose domain matches your WordPress hostname.
- Open Settings → FindIP Shield, paste the site's public key (starts with
pub_), and save. - Load a public page, then confirm the first event on your Shield site's Install page.
The plugin loads an exact, immutable Shield SDK build from cdn.findip.net with subresource integrity — the browser refuses to run a script that does not match the recorded hash. Login pages are covered as well as public pages.
Settings
- Privacy mode — strict (default), balanced, or advanced, identical to the Shield SDK modes. Strict collects only user agent, language, and timezone and sets no visitor cookie.
- Automatic tracking — page views, one
session_startper browser session, and form-activity events derived from form attributes only; field values are never read. - Consent — with require consent enabled, the plugin starts in the configured pre-consent behavior (
strictordisabled) until your consent tool dispatches afindip:consentevent:
document.dispatchEvent(new CustomEvent('findip:consent', {
detail: { granted: true }
}));WooCommerce
If WooCommerce is active, this plugin can additionally emit cart, checkout, payment-failure, and order-completion context (toggleable in settings). For richer storefront signals with per-event controls, use the dedicated FindIP Shield for WooCommerce plugin instead — the two plugins are mutually exclusive and must not run together.
Attribution
Events report integration: wordpress in the dashboard, so WordPress traffic is distinguishable from plain JavaScript or Google Tag Manager installations.
Server-side verification
Browser risk responses are informational. For decisions that matter (sign-ups, checkouts), verify the session server-side with your secret key — see Server Verification.