← All checks
Rate limit test: will your server block a crawler burst?
Group A3 pointsrubric r1
We fetch your homepage five times in a row and record the status codes. Any 403, or two or more 429 responses, fails the check.
Why it matters
An agent answering a question often loads several pages within a few seconds. A strict rate limit turns the second or third request into a 429 or 403, and the agent finishes its answer from the pages it did get, which is incomplete. A single 429 in the burst earns partial credit.
How to fix it
- Raise the per-IP limit for cacheable GET requests to at least 10 per second.
- Return
429with aRetry-Afterheader rather than403, so a client can back off. - Serve public pages from a CDN cache, which does not count against origin limits.
- Check WAF rules that block an IP after a few identical requests.
How to verify
Run for i in 1 2 3 4 5; do curl -s -o /dev/null -w "%{http_code} " https://example.com/; done and expect five 200s.