Firewall and the Lawwwing scanner
Lawwwing periodically scans your website to detect cookies, scripts, tracking technologies and other relevant elements. We use this data to keep your banner, cookie declaration and legal documents up to date.
If your website is protected by a firewall, a WAF (Web Application Firewall), a CDN with bot protection or a security plugin, it may block our scanner. When that happens, the scan can fail or return incomplete results.
How do I know if the scanner is being blocked?​
The most common symptoms are:
- The scan fails or never finishes.
- The scan finishes, but does not detect cookies or scripts that you know are on your website.
- The results show a block page, a captcha or a JavaScript challenge (for example, "Checking your browser…" or "Access denied") instead of your website.
- Your firewall logs show blocked requests with the
LawwwingAuditorUser-Agent.
To prevent this, add the Lawwwing scanner to the allowlist (or whitelist) of your security system. You can do it in two ways:
- By User-Agent (recommended)
- By IP address
Option 1: By User-Agent​
Every request from our scanner is identified with the following User-Agent:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36 LawwwingAuditor/1.0 (+https://lawwwing.com/)
The first part of the User-Agent (the browser version, for example Chrome/142.0.0.0) will change over time as we update the browser used by the scanner.
The LawwwingAuditor identifier will always stay the same. That's why we recommend that your rule checks whether the User-Agent contains LawwwingAuditor, instead of matching the full string.
Example: Cloudflare​
-
In the Cloudflare dashboard, go to Security → WAF → Custom rules and click Create rule.
-
Give it a name, for example "Allow Lawwwing scanner".
-
Click Edit expression and enter:
(http.user_agent contains "LawwwingAuditor") -
Under Choose action, select Skip and tick the components you want to skip (for example, All remaining custom rules, Rate limiting rules, Managed rules and Super Bot Fight Mode).
-
Save the rule and make sure it is in the first position of the list.
If you use Bot Fight Mode (Cloudflare free plan), note that it cannot be skipped with custom rules. In that case, turn it off temporarily while the scan runs or use the IP option.
Example: Nginx​
If you block bots or User-Agents in your Nginx configuration, add an exception for the scanner before your blocking rules:
map $http_user_agent $is_lawwwing_scanner {
default 0;
~*LawwwingAuditor 1;
}
Then use the $is_lawwwing_scanner variable to skip your blocking rules when its value is 1.
Example: Apache (.htaccess)​
SetEnvIfNoCase User-Agent "LawwwingAuditor" lawwwing_scanner
Then use the lawwwing_scanner environment variable to exclude the scanner from your blocking rules (for example, with Require env lawwwing_scanner).
Other providers​
Most firewalls and security plugins (Sucuri, Wordfence, Imperva, Akamai, AWS WAF, etc.) let you create User-Agent exceptions. Look for an option such as "Allowlist", "Whitelist", "Allowed User Agents" or "Custom rules" and create a rule with the condition User-Agent contains LawwwingAuditor.
The User-Agent is sent by the client itself, so anyone could imitate it. If you need stricter control, combine the User-Agent rule with the IP address list.
Option 2: By IP address​
If your security system only allows exceptions by IP address, or you want stricter control, you can allowlist the IP addresses our scanner operates from:
188.165.71.52
91.134.19.115
51.210.167.202
This list may change in the future as we expand or modify our infrastructure, and we may not always be able to notify you in advance. If an IP changes and your firewall only allows the old ones, the scan will start failing again.
That's why, whenever your system supports it, we recommend using the User-Agent rule, which does not depend on IP addresses. If you use the IP list, check this page periodically to keep it up to date.
Check that it works​
Once the exception is in place:
- Go to your Lawwwing dashboard and run a new scan of your website.
- Check that the scan finishes successfully and detects your website's cookies and scripts.
- If your firewall keeps logs, verify that requests with the
LawwwingAuditorUser-Agent no longer appear as blocked.
If the scan still fails after following these steps, contact us and we'll help you with whatever you need.