Skip to main content

Captcha Protection

Captcha Protection asks visitors to your clients' domains with Website protection to complete a quick, automatic browser check before the page opens. People get through in a few seconds without solving a puzzle: their browser does a small piece of work in the background, then the page they asked for opens by itself. Bots and scripts that can't run the check are stopped. A visitor who passes can keep browsing, and isn't checked again unless they go 30 minutes without opening a page.

Captcha Protection works on domains with Website protection only and is included in your Website protection licence. See Network protection vs Website protection.

You'll find it in Settings › Captcha Protection: open Settings and click Manage Captcha Protection on the Captcha Protection card. For one domain, open it from Domains, then use Under Attack for this domain in the header, or click Edit domain and go to Captcha Protection. The Protection tab is read-only: What's protecting this domain right now. To change a setting, use Edit. Your clients can use it in the owner area. Only an account owner can change these settings. Sentries pick up a change within a minute. This needs the latest sentry release: older sentries keep letting visitors through without a check.

Under Attack​

Under Attack is the emergency switch. While it's on, every visitor is checked before the page opens, except trusted traffic. Turn it on with one click when a site is being flooded, and turn it off once the attack is over.

You can turn Under Attack on:

  • For one domain: on the domain's page, click Turn on Under Attack. The switch is labelled Under Attack for this domain, and only shows when Website protection is on. You can also turn it on under Captcha Protection on Edit domain. When you turn it off, the portal asks you to confirm: {domain} will stop checking every visitor before the page opens. Other Captcha Protection checks still apply.
  • For every domain with Website protection on a cluster: in Settings › Captcha Protection, open the cluster's tab and click Turn on Under Attack.
  • For every domain with Website protection on every cluster: in Settings › Captcha Protection, on the All clusters tab, click Turn on Under Attack.

While it's on, a red banner says so on the page where you turned it on, and the domain's page shows it too. On Domains, a red shield icon marks each domain with Under Attack on; the key under the table reads Under Attack is on. The Domains table has no switch of its own: turn Under Attack on or off from Settings › Captcha Protection or the domain's page.

Domain owners can turn Under Attack on and off for their own site in the owner area header, if you've allowed Captcha Protection. They can't turn off Under Attack that you turned on.

Every time Under Attack is turned on or off, by you or a domain owner, it's recorded in your audit log.

When to check visitors​

Besides Under Attack, you can choose when visitors are checked. Each one is on or off:

SettingWho is checked
Suspicious trafficVisitors that look like bots but aren't a known service, addresses on the stillorigin naughty list (when you aren't already dropping them with Use the stillorigin naughty list), and visitors over the rate limit (they get the check instead of an error)
Chosen pagesVisitors opening the pages you list, such as a login page. One path per line, starting with /. End a path with * to include everything under it, for example /admin/*. You can add up to 20 pages. Click WordPress, Joomla, Drupal or Other sites under Add common login pages: to add their usual login pages: /wp-login.php and /xmlrpc.php; /administrator/*; /user/login and /user/password; or /login and /admin/*
When the site is under loadEvery visitor, while the site is slow or failing to answer. It stops by itself once the site has recovered

Settings on the All clusters tab apply to every cluster in your account, now and in future. A cluster tab can only add settings for that cluster; settings for all clusters are shown ticked there and can only be changed on the All clusters tab. Click Save when you're done.

When the site is under load turns on when, over one minute with at least 20 requests, the average response is 2 seconds or more, or 25% or more of responses are 502, 503 or 504. It turns off after 5 healthy minutes, and never sooner than 10 minutes after it turned on. Each sentry decides for itself, from the traffic it sees.

Never checked​

These are never checked:

  • Identified traffic, such as search engines, monitoring services and payment providers (see Verified crawlers). Internet scanners, such as Censys, are labelled but not trusted, so they're checked like any other visitor.
  • Payment notifications sent to common online stores, so orders are confirmed when the customer pays (see Online stores and payments).
  • Certificate checks (ACME and pki-validation), so certificates keep renewing.
  • Your own sentries and origin servers.
  • The addresses you add under Never check these addresses, such as your office or a monitoring service. IP addresses or ranges, one per line, up to 100.

Online stores and payments​

Captcha Protection is built so shoppers can check out normally:

  • Payment providers' servers are never checked. When a payment provider tells the store that an order is paid, its request comes from the provider's own servers, not the shopper's browser. Braintree, Checkout.com, GoCardless, Mollie, Paddle, PayPal, Square and Stripe are in Identified traffic, by the addresses they publish, under Payment providers.

  • Payment notifications sent to the store's callback addresses are never checked, whoever sends them. This applies only to requests that send information to these addresses (POST requests). Opening one of these addresses as a page is checked as usual:

    • WooCommerce: /wc-api/… and any address with ?wc-api=, plus the WooCommerce PayPal Payments and WooPayments webhooks
    • Magento: PayPal IPN (/paypal/ipn/) and Adyen webhooks (/adyen/webhook)
    • PrestaShop: the PayPal, Mollie and Stripe module callbacks (/module/paypal/ipn, /module/paypal/webhookhandler, /module/mollie/webhook, /module/stripe_official/webhook), and /modules/paypal/ipn.php

    Only the check is skipped. Your Website protection rules, rate limits and blocks still apply to these addresses.

  • The pass lasts while the shopper is active. It renews as they open pages, so it doesn't run out halfway through a checkout.

  • The pass still works when the payment page sends the shopper back to the store. On HTTPS sites, the pass goes with the shopper when a payment provider returns them to the store, so they aren't checked again.

If a store uses another payment provider, such as Adyen, add the provider's published addresses under Never check these addresses. Some providers don't publish a list of addresses we can keep up to date for you. Their payment notifications to the addresses listed above are never checked anyway.

A shopper who changes network during checkout, for example from Wi-Fi to mobile data, is checked again, because a pass only works from the address that passed the check.

What visitors see​

A visitor who's checked sees a stillorigin-branded page headed Checking that you're a person. The check starts when the page opens and usually takes a few seconds. The I'm a person label ticks itself when the check finishes, then the page they asked for opens by itself, at the same address. Visitors never have to click to start the check. If the check doesn't work or times out, a Try again button is shown.

The check needs JavaScript; without it, the page asks the visitor to turn JavaScript on and reload.

Requests that aren't a page opened in a browser, such as an API call or a script, get a plain-text 403 reply instead: Captcha Protection: this request needs a browser check. Open this page in a web browser to continue. If an app or service needs to reach the site while Captcha Protection is on, add its address to Never check these addresses.

The check page is never stored by browsers or search engines.

When the check was shown because the visitor's address is on the naughty list (and you aren't already dropping those addresses on the deny list), the page also says Your address may be on stillorigin's naughty list. You can check it, and ask for it to be removed, at https://stillorigin.app/check. That line isn't shown for other checks, or on the block page.

Log mode​

While a domain's Website protection rules are in log mode, Suspicious traffic, Chosen pages, When the site is under load and country-rule checks don't check visitors. The check they would have got is only logged, and shows under Would have blocked, last 24 hours on the domain's Blocks tab. Switch the Website protection rules to blocking on Edit domain, under Website protection rules, to turn those checks on.

Under Attack still checks visitors in log mode, because you turn it on yourself in an emergency.

In your logs​

Each check shows in your logs as:

  • Browser check: chosen page, Browser check: country rule, Browser check: naughty list, Browser check: site under load, Browser check: suspected bot, Browser check: too many requests or Browser check: Under Attack: the visitor was shown the check, and why. Country-rule checks are set on Country blocking.
  • Browser check passed: the visitor completed the check and can keep browsing the site. The pass ends after 30 minutes without opening a page.
  • Browser check failed: the check wasn't completed correctly, so the visitor didn't get through.

The Protection tab, and Captcha Protection on Edit domain, show the last 24 hours, for example Last 24 hours: 120 checks shown, 95 passed, 3 failed. If there were none, it reads No checks in the last 24 hours. The Overview tab also shows Browser checks passed, 24h and Browser checks failed, 24h. Shown, passed and failed counts are kept for 30 days.

Domain owners​

This permission is on by default: Let domain owners change Captcha Protection on their domain, including Under Attack, on Owner access. A domain owner can then, in the owner area header, turn Under Attack on or off for their site, and on the Settings tab, under Captcha Protection, choose Use my host's settings or Choose my own checks. They click Save checks when they're done. They can't turn off Under Attack that you turned on; they see Your host turned on Under Attack for your site. Contact your host if you need it turned off. The Protection tab shows whether Under Attack is on, which checks apply, and the last 24 hours of checks. It's read-only: What's protecting your site right now. You can change some of these in Settings. Your host manages the rest.

If you take the permission away, the owner's choices stop applying but are kept, and come back if you allow it again. The owner still sees Captcha Protection on Protection and Settings, reading Your host manages Captcha Protection for your site. They also see Your Captcha Protection choices are paused because your host now manages Captcha Protection. They come back if your host allows changes again. under Settings your host has paused. Your own settings, and Under Attack you turned on, always apply.

Changes you or a domain owner make to Captcha Protection are recorded in your audit log, for example Under Attack turned on for all clusters, Under Attack turned off for domain shop.example.com, or Changed Captcha Protection for domain shop.example.com.