Skip to main content

Website protection log mode

When you turn Website protection on for a domain, it starts in log mode. The WAF (when it's on for the cluster) and some Website protection rules record what they would block, but let those requests through, so you can see what would be blocked before you switch the domain to blocking.

What log mode covers​

Log mode covers:

  • the WAF, which checks requests for common attacks such as SQL injection and cross-site scripting, once you've turned it on for the cluster
  • the path traversal rule
  • the rule for requests for secrets and backup files (sensitive-path)
  • the automatic Captcha Protection checks: Suspicious traffic, Chosen pages, When the site is under load, and country-rule checks (see Country blocking)

These record what they would block and let the requests through.

These still block in log mode, just as they do when the domain is blocking:

  • the WordPress hardening rules on WordPress domains
  • rate limits, including the cluster's Website protection requests per second and Website protection burst (answered with HTTP 429)
  • the admin login lock on WordPress domains, if you turn it on
  • Under Attack, which still checks visitors
  • all Network protection
  • enforced country blocks, including network-wide blocks (HTTPS at the sentry firewall, HTTP on port 80 at the sentry's web server) and a domain's own or owner country blocks

How a domain starts in log mode​

Every way you turn Website protection on starts the domain in log mode:

  • the Website protection toggle on Domains
  • assigning a Website protection licence
  • adding a domain from Not protected yet with protection set to Website protection (starts in log mode)
  • turning Website protection back on after it was turned off automatically, for example when the account went over its Website protection allowance

Domains that already had Website protection on before this release stay in blocking. Turning Website protection off and on again starts the domain in log mode.

There is no time limit and no reminder. A domain stays in log mode until an account owner switches it, or the domain owner does, if you allow it on Owner access.

Switching between log mode and blocking​

On Edit domain, under Website protection rules, you'll see Log mode or Blocking. Open the domain from Domains, click Edit domain, then Website protection rules in Settings on this page. The domain header shows a Log mode badge when it's on, and the Protection tab shows Log mode or Blocking. That tab is read-only: What's protecting this domain right now. To change a setting, use Edit.

  • In log mode: The WAF and the path traversal and private file rules record what they would block, but let those requests through. The WordPress hardening rules, rate limits and the admin login lock, if it's on, still block.
  • In blocking: Website protection rules block the requests they match.

Use Switch to blocking or Switch to log mode. Before switching to blocking, the portal asks you to confirm: Switch to blocking? Website protection rules will block the requests they match on {domain}. Check what log mode would have blocked first, so you don't block real visitors. Before switching back to log mode: Switch to log mode? The WAF and the path traversal and private file rules will only record what they would block on {domain}, and let those requests through. The WordPress hardening rules, rate limits and the admin login lock, if it's on, keep blocking.

You can also select domains on Domains and use the same two actions, up to 500 at a time. Only an account owner can switch. Everyone else sees: Only an account owner can change this.

If Website protection is off, Website protection rules on Edit domain reads: Turn on Website protection to use Website protection rules. New domains with Website protection start in log mode.

What log mode would have blocked​

The domain's Blocks tab shows Would have blocked, last 24 hours, with a count, a breakdown by rule, and Recent requests recorded but let through (time, IP address, rule and path). Paths are shown without their query string. If nothing matches, it says Nothing would have been blocked in the last 24 hours. That view is read-only. If a WAF rule would block real visitors, open Edit domain, go to Website protection rules, and click Ignore on this domain next to it (see WAF rules). The panel shows the last 24 hours. The records themselves are kept for 30 days.

These are samples, at most one per IP address and rule every 30 seconds, so they show the pattern rather than exact totals. Requests recorded but let through count as allowed, not blocked. They do not appear under Logs, and there is no Logs filter for them.

After you switch to blocking​

Once a domain is set to blocking, the same section is headed Recorded but let through, last 24 hours, and it only appears when something was recorded in the last 24 hours. Two kinds of rows can still show:

  • Country rule in log mode: {country}: a country rule still in log mode records visitors from that country and lets them through, whatever mode the domain is in. Click Enforce on the country to start blocking or checking them.
  • Before you switched to blocking: rules recorded while the domain was still in log mode. The note above the table reads You switched to blocking at {time}. These rows drop off within 24 hours of the switch.

If nothing is left to show, the section is hidden.

On Domains, a domain in log mode shows a Log mode icon, explained by the Key under the table. Hover it for: The WAF and some Website protection rules on this domain record what they would block, but let those requests through. Filter the list with Website protection rules: All, Log mode or Blocking.

Check Would have blocked, last 24 hours on the Blocks tab, then switch the domain to blocking on Edit domain, under Website protection rules, when you are ready.