CC protection

About 6 min

A CC attack drains a site's resources with large numbers of seemingly normal requests. CC protection is on by default.

RequestCustom rulesAllow · Ban · Human checkCC levelOff … StrictOrigin
GET / · normal visitor
Allowed
POST /login · high rateRate limit
Blocked
GET /list · pageSilent check
Verify
GET / · trusted egress IPSkips CC protection
Allowed
GET /search · flood of requestsLevel rules
Verify
Human checksRate limit · Silent check · 5-second shield · Click · Slider
IPs that skip protection/8 /16 /24 masks supported
DefaultOn
Custom rules go first; what they don't match goes through the chosen CC level; trusted IPs skip it

Levels

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.

Tip API paths (login, SMS, search) suit a dedicated rate-limit rule; page paths suit the silent check, which barely bothers normal visitors.

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.

Caution If an allowlisted IP is abused by an attacker, protection is bypassed. Where lists and access control can narrow the scope, don't allow too widely.

View blocked requests in the attack log.

Get started

Try the live demo

Open the live demo, or contact us for a quote and the install command