# When bot protection blocks your tests, and how to allow them

> Cloudflare-style challenges and firewalls stop automated browsers, including the tester. Why a blocked run is not counted, and how to allow Testsy's static addresses.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/when-bot-protection-blocks-your-tests/

## Your site is working as designed

Many client sites sit behind bot protection: a CDN's challenge page, a firewall rule, a security plugin that blocks unfamiliar traffic. It is doing its job when it stops an automated browser. The tester is an automated browser.

When that happens, Testsy reports the run as **Blocked**: the site stopped the tester, so some checks could not be done. A blocked run is **not counted** against your plan, and it is not reported as a pass or a fail of the site.

## Allow our addresses

Testsy's browsers reach websites from static addresses. From [network and allow-listing](https://testsy.dev/docs/network/): **Settings → Workspace → How our browsers reach your site** lists them, each with **Copy**. Add them to the allow list of the client's firewall, CDN or bot protection. When runs were blocked this month, the same page says so.

![Workspace settings: the addresses to allow and the country tests browse from.](https://testsy.dev/docs/img/workspace-settings-light.webp)

On the home page, blocked runs come with an **Allow our browsers** shortcut to the same list.

## Where to allow them

- **CDN bot protection or WAF:** an IP allow rule that skips challenges for those addresses.
- **WordPress security plugins:** their allow-list or trusted IP setting.
- **Rate limiting:** exclude the addresses, or keep tests from running all at once.

Allow them only where the client agrees, and for the sites you test.

## When you cannot allow them

Hosted platforms do not always let you change bot rules. Options:

- Test a staging copy without the protection.
- Test a page before the protected part (the challenge is often only on checkout or login).
- Accept the blocked result as an answer: the site is protected, and the test cannot get past it either.

## Sites that are not public

A site that is only reachable on a private network or a developer's machine cannot be tested yet. A site behind a sign-in is fine: the tester signs in with a [stored account](https://testsy.dev/docs/sign-in-accounts/).

This post is part of [Find the bug before your client does](https://testsy.dev/blog/find-the-bug-before-your-client-does/).
