What problem does it solve? Security testers need to verify whether API rate limiting controls actually prevent brute force attacks, credential stuffing, and resource exhaustion, but rate limits are often enforced inconsistently across IPs, methods, paths, and API versions. ## Core Features & Use Cases - Rate Limit Discovery: Probes endpoints to detect rate limit headers (X-RateLimit-Limit, Retry-After) and establishes baseline throttling thresholds. - Bypass Technique Testing: Tests X-Forwarded-For and other IP spoofing headers, URL path variations, HTTP method switching, content-type changes, parameter pollution, and concurrent race conditions. - Structured Findings Output: Produces severity-rated findings mapped to OWASP API4:2023 Unrestricted Resource Consumption with remediation guidance. - Use Case: Before a compliance audit, a security team tests a login endpoint and discovers that rotating X-Forwarded-For headers bypasses the 10-requests-per-minute limit, enabling unlimited credential stuffing attempts. ## Quick Start Run the rate limiting bypass test against my authorized staging API endpoint at https://staging.example.com/api/v1/auth/login with header, method, and path bypass checks enabled.