Allowlist SecurePrivacy.ai Scanner in Your Firewall/CDN (Bot Protection Guide)
If your firewall, CDN, or WAF uses bot protection (rate limiting, CAPTCHA/challenge, or behavioral analytics), you must allowlist the SecurePrivacy.ai scanner so your compliance scans can run reliably. Request the current IP list on demand at mailto:support@secureprivacy.aisupport@secureprivacy.ai.
Overview
Modern bot protection can challenge or block automated traffic—including legitimate scanners used for compliance and privacy verification. The SecurePrivacy.ai scanner is a trusted service that needs predictable access to your site so we can detect consent banners, cookies, trackers, and related signals. The simplest, most secure way to permit our scanner is an IP-based allowlist (source IPs provided by us).
- What you configure: Allow our scanner’s IPs to bypass bot challenges and strict rate limits.
- What we provide: A current list of scanner IP addresses via support@secureprivacy.ai
Quick Start (3 Steps)
- Request IPs: Email support@secureprivacy.ai with subject “Scanner IP allowlist” and include your domains/environments (e.g., production, staging).
- Create an allow rule: In your firewall/CDN/WAF, create a rule that allows or bypasses bot protection for those source IPs.
- Verify: Run a scan from your SecurePrivacy.ai dashboard (or ask support to trigger one) and confirm no challenges/blocks occur.
Tip: Place the allowlist rule near the top of your rule set so it takes precedence over generic bot and rate-limit policies.
FAQ
Why do I need to allowlist the scanner?
Bot defenses often block legitimate automated crawlers. Allowlisting ensures accurate privacy and compliance scanning without human challenges or false blocks.
How do I get the current IPs?
Email support@secureprivacy.ai - we’ll provide the up-to-date list and notify you of any changes upon request.
Do the IPs change?
This can happen rarely, but yes - they can. Re-request the list in case the scans begin failing, and update your allowlist accordingly.
Will this weaken my security?
No—you’re only permitting a specific, known source IP set. Keep the rule narrowly scoped and prioritized, and maintain your existing protections for all other traffic.
Need Help?
We’re happy to assist via support@secureprivacy.ai