Choose the narrowest trust method
| Method | Best use |
|---|---|
| IP whitelist | A known office, administrator, integration server, or customer address. |
| Trusted Automated Services | A specific, stable product name found in its browser identification. |
| Trusted Service Groups | A maintained category such as uptime monitoring or CDN/security services. |
| Hosting and CDN Addresses | Infrastructure allowed to supply the original client address. This is a proxy-trust setting, not a general visitor whitelist. |
| Rate Limiting whitelist | An address that should bypass only the rate-limiting module. |
Add one IP address
- Enter a valid IPv4 or IPv6 address.
- Record why it is trusted.
- Choose Permanent, 1 hour, 24 hours, 1 week, 1 month, or 1 year.
- Select Add to Whitelist and confirm it appears under Current Whitelisted IPs.
Bulk import
Enter one address per line. The shared reason and duration apply to every accepted address. Use Export before a large import or cleanup. Invalid lines should be corrected rather than converted into broad ranges.
Trusted service patterns
Patterns match names in browser identification. Prefer a full product name such as Screaming Frog SEO Spider. Avoid broad fragments such as bot, crawl, monitor, or a common browser name.
Preset groups
The available categories cover monitoring, CDN/security, SEO tools, analytics/marketing automation, security scanners, and development tools. A preset is convenient but broader than one explicit service. Review its included patterns before enabling it.
Expiration and precedence
Temporary IP entries expire automatically. Cleanup actions remove expired entries from the active list. A trusted IP bypasses Bot Guard even if an active blocked strike record remains; when the trust entry is removed, that strike state applies again immediately if it has not expired.