Skip to content
Sign in

How-to

Let Zof's test traffic through

Updated

On this page

Load, endurance, stress and scalability tests send every request from Zof's one source, so your site's rate limiting or firewall can refuse them. Letting that traffic through on a staging or performance address takes about 10 minutes, with access to the firewall or CDN in front of the site.

Why a site refuses it

Real visitors reach your site from many addresses. Zof's test traffic comes from one, so rate limiting or a firewall, such as Cloudflare or AWS WAF, treats it as one very busy client. It answers 429 Too Many Requests or 403 Forbidden, which your real users wouldn't get.

What Zof shows

When nearly every failed request was a 429 or a 403, the run measured how your site's protection treats one source, not how your site handles its users. Zof shows the test as Couldn't check, never as a pass, with the reason and a link to this page.

Add a rule on a staging or performance address

Every request from these tests names Zof in its User-Agent header:

Mozilla/5.0 (compatible; ZofTestingAgent/<version>; +https://zof.ai/bot) <agent>/<version>

  1. In your firewall, CDN or rate-limiting settings, open the rules for your staging or performance address.

  2. Add a rule for requests whose User-Agent contains:

    ZofTestingAgent

  3. Have the rule skip rate limiting and firewall challenges for those requests. Providers call this a skip, bypass or allow rule.

  4. Save the rule.

Match on the User-Agent, not an IP address: Zof doesn't publish addresses for its test traffic.

Warning. Anyone can copy a User-Agent. Add this rule only on a staging or performance address, never on production, and remove it when you finish testing.

Check that it worked

Run the test again. It no longer says the site refused Zof's test traffic, and it shows a result: Passed, or Issues found when a limit is crossed. If it still says the site refused it, check that the rule covers the address you tested.

Next steps