The WordPress plugin and PHP SDK apply rules on your server. If NexIP is unavailable, observation remains non-blocking; previously enabled enforcement uses basic local limits.
Rate limits for login requests and failed sign-ins.
Protection for standard comments and registration.
Threshold rules with clear reasons.
An additional browser interaction check.
Manage protection in NexIP
Verify your domain with a DNS TXT record and connect the WordPress plugin or PHP SDK with a dedicated key. Start in observation mode, review events, then enable enforcement.
Passwords, authentication cookies and form contents are not sent to NexIP. Events contain technical metadata only.
Connect in four steps
Add your domain in the Shield dashboard.
Create the provided DNS TXT record and verify ownership.
Install the WordPress plugin or follow the PHP SDK guide inside its ZIP, then save your connection credentials.
Synchronize the integration, check the connection and start with observation. Review events before enforcing rules.
Available on the basic plan
The basic model includes one website, up to five rules and a short event history. Your current NexIP plan determines the actual limits and paid features.
Shield V1 protects application actions. It is not a CDN or protection against large L3/L4 DDoS attacks. JavaScript and the built-in browser check do not prove a visitor is human.
Third-party forms need a separate adapter. History contains received events; quotas and delivery failures can reduce coverage.
Protection and monitoring work together
NexIP Monitor checks availability. Shield records decisions on the connected website. Blocking a suspicious action does not by itself mean the website is unavailable.