Shield · GDPR
Telling a bot from a person means looking at every request. Shield does it on your server, and visitors' data stays there.
Community is free on one server, with every protection.
Under the GDPR an IP address can be personal data. So it matters where requests are analysed.
If protection is an external service, the data goes through a third party, which has to be named in your privacy notice. With Shield the analysis happens on your server.
Shield runs next to the site, on your Linux server. No DNS change, no external proxy.
No IP address, no visited page, no header. Only data about the server (name, version), aggregate counts, also by country and network operator, and the type and path of attack attempts, masked, leave it.
A signed pass spares visitors already in from a second check. It is used only for protection.
On the free Community plan, connecting to the panel is the condition of use; on Pro and Business it is optional. Shield downloads shared rules from luviner.com and its updates from Docker Hub.
To verify requests claiming to be a search engine, Shield asks your server's DNS. This happens only for those requests, not for visitors.
No. No IP address, no visited page, no header. Only data about the server (name, version), aggregate counts, also by country and network operator, and the type and path of attack attempts, masked, leave it.
On Pro and Business, yes. On the free Community plan, connecting to the panel is the condition of use.
One: the pass that spares a second check. It is used only for protection.
No, not on its own. It reduces the visitor data leaving the server; your privacy notice is still up to you.
Shield installs in minutes on your Linux server and starts in observe mode: you see what it would stop before it stops anything.
Install Shield → See the plans →