Docs / Getting started
Protection modes
How much protection to turn on: from watching only to a browser check for everyone.
The protection mode sets what a node does with a suspicious request: only log it, block it, or ask the browser to pass a check first. The mode is chosen per site and changes in one click.
Three modes
| Mode | What happens | When |
|---|---|---|
| Passive | WAF rules and your rules only write to the log; requests reach the server. Address lists, countries and limits work as usual. | The first days after connecting, to see that rules do not hit real visitors |
| Standard | The WAF (OWASP CRS) and your rules block. The browser check appears only where your rule asks for it and during an attack. | Normal operation |
| Challenge | Every new visitor passes a browser check first, then reaches the site. | The site is under attack, or only real people should get in |
Switch it in the panel: domain → Protection → Protection mode. Which modes are available depends on the plan: Passive is always there, Standard and Challenge come with plans that include the WAF.
How the browser check works
The visitor sees a short page while the browser solves a small computing task in the background. It usually takes under a second and nothing has to be typed. After the check the browser gets a mark for 30 minutes, renewed on its own while the person uses the site.
- Bots without a real browser do not solve the task and get no further.
- During an attack and for suspicious visitors the task gets a bit harder.
- Background requests (XHR, fetch, JSON, static files) without the mark get a short
429instead of the check page: the check is needed once, when the page opens.
Turn on “Show the challenge”
The check page appears only when “Show the challenge” is on in Protection → Browser challenge. Without it the Challenge mode and checks asked by your rules do not fire.
The same page adds an optional slider captcha on top of the check: never, during an attack, for suspicious visitors, or always.
Who passes without a check
- Verified search and service bots: Googlebot, Bingbot, Yandex, Telegram and others. See Known bots.
- API requests with an
Authorizationheader. - Requests let through by your Skip rules.
- VPN apps on subscription paths, if enabled in Protection → VPN apps.
APIs and apps
In Challenge mode, requests that cannot show a page — /api/, files, framework service requests — get no check page but still go through the limits and the WAF. Mobile apps and integrations should send a token in the Authorization header.
Automatically during an attack
When requests to a site suddenly grow far above normal, the nodes treat the site as attacked:
- The browser check turns on for new visitors, even in Passive mode. Visitors already on the site keep working without it.
- Your chosen mode does not change. The check turns off on its own once the attack is over, but not earlier than 15 minutes after it started.
- You get a notice when the attack starts and ends.
Next
Set up custom rules and country and address lists, then watch the request log: every decision has a reason and a Ray ID.