A CC attack drains a site's resources with large numbers of seemingly normal requests. CC protection is on by default.
GET / · normal visitorPOST /login · high rateRate limitGET /list · pageSilent checkGET / · trusted egress IPSkips CC protectionGET /search · flood of requestsLevel rulesLevels
Go to Security Center › Protection settings › CC Protection. Requests not matched by a custom rule go through the selected CC rule set; the built-in levels range from "Off" to "Strict". The parameters of preset levels are read-only; choose "Custom" to change them.
- The default level is enough for everyday sites.
- Raise the level under attack; if you see "CC level too low", switch to "JS challenge" or higher as suggested.
- A site can change its own level in its settings, and administrators can set the default level by scope (global / region / node).
Custom rules
Create custom rules for a site to target a certain path or condition. Requests that match a rule can be:
- allowed;
- banned;
- given a human check: rate limit, silent check, 5-second shield, click check, slider and so on.
Regexes in conditions use RE2 syntax. A regex that matches anything (including empty content, such as .* or a?) makes the condition always true, and some patterns can make edge nodes backtrack out of control; both kinds are rejected on save with the reason shown. To match an empty value, write ^$. A rule can have at most 256 conditions.
IPs that skip protection
A list of IPs skips CC protection and challenges, one per line, with /8, /16 and /24 masks supported. Listed IPs are no longer affected by CC protection, so list only egress IPs you trust.
View blocked requests in the attack log.