← back home · # use cases
For people who already lived this pain.
recurl is one tool, but the 403 shows up in different jobs. Here is where it earns its place — each with the concrete problem, how recurl resolves it, and the commands to run. Same ethical scope as curl: authorised targets only.
Debugging anti-bot 403s in DevOps
→On-call DevOps and SRE engineers
When a monitoring curl or health check returns 403, recurl tells you whether it is TLS fingerprinting or a real outage — and keeps the check green.
ScrapingResilient scraping pipelines
→Scraper developers and data engineers
Scraper scripts that work in dev and 403 in prod are a fingerprint problem. recurl keeps the same curl command line and escalates only on a block.
SecuritySecurity-testing your own properties
→Security researchers and appsec engineers
Test your own sites against browser-grade TLS fingerprints, then flip --recurl-strict to see exactly what plain curl saw. Same ethical scope as curl.
CIStabilising flaky curl checks in CI
→Automation and platform engineers
External curl checks that flake on bot walls stop being flaky when you alias curl to recurl — same flags, same exit codes, escalation only on a block.