Skip to content

Cloudflare

Cloudflare is the most common reason a check fails on a site that is perfectly healthy. It can mistake monitoring traffic for data scraping, and the frequency Testomato checks at — every minute, sometimes several URLs at once — looks like exactly the pattern its bot and rate-limiting rules exist to stop.

A blocked check usually comes back as an Access denied (Error 1020) response:

Cloudflare Error 1020 access denied screen

Error 1020 means Testomatobot was blocked by a WAF custom rule. The rule is one of yours, so the fix is to find it and add an exception. Other blocks show up as a challenge page, a 429, or one of the other 1xxx error codes — the way to identify them is the same.

  1. Log in to the Cloudflare dashboard and select your domain.
  2. Go to Security → Events (Security Events).
  3. Filter by the Ray ID from the error page, or by one of the Testomato IP addresses, to find the blocked request.
  4. The event names the service and the rule that blocked it — a custom rule, a managed rule, rate limiting or IP reputation.

There are two ways to do it. Pick one.

  1. In the Cloudflare dashboard, select your domain.
  2. Go to Security → WAF → Tools.
  3. Under IP Access Rules, add each Testomato address with the action Allow and scope it to the site or your whole account.

This exempts the addresses from the WAF, rate limiting and the IP reputation checks, but not from a custom rule that blocks them explicitly.

A skip rule in Security → WAF → Custom rules overrides everything below it, including your own block rules:

  1. Create a custom rule and place it above the rules that are blocking Testomato.

  2. Use this expression, with the full list of addresses in the set:

    (ip.src in {217.31.53.147 217.31.54.206 167.235.18.92})
  3. Choose the action Skip and tick the components to bypass — at minimum All remaining custom rules, Rate limiting rules and Managed rules.