Request Checker (Why am I getting 403?)
Free request checker for web scrapers. It echoes the headers the server actually received and scores how bot-like your request looks, so you can see what triggers 403s before TLS fingerprinting.
About This Tool
Getting 403 Forbidden while scraping is almost always a fingerprinting problem, not a code problem. This free tool echoes the exact headers the server received from your request and scores how bot-like it looks: missing User-Agent, a python-requests or curl signature, no Accept-Language, missing Sec-Fetch and client-hint headers. Run it from your browser to see a clean baseline, then point your scraper at the endpoint and compare. If every header passes but you still get blocked, the cause is your TLS/JA3 fingerprint and your IP reputation.
How It Works
- 1Open the tool to see your browser baseline score
- 2Read which headers pass and which give you away
- 3Point your scraper at the endpoint with the curl or Python snippet
- 4Fix the flagged headers, then add rotating residential proxies if still blocked
Features
- Echoes the real headers the server received
- Scores bot-likeness 0 to 100 with a clear verdict
- Flags each problem header and how to fix it
- Call it from curl, Python, Node or any scraper
- CORS-open endpoint for direct scraper testing
- Explains when the block is TLS fingerprint vs headers
Common Use Cases
- Debug 403 Forbidden errors when scraping
- Verify your scraper sends browser-accurate headers
- Decide whether your block is headers, TLS fingerprint or IP reputation
- Compare requests library vs curl_cffi vs a real browser
Frequently Asked Questions
Anti-bot systems compare your request to a real browser. The usual giveaways are a missing or library User-Agent (python-requests, curl), no Accept-Language, and missing Sec-Fetch and sec-ch-ua client-hint headers. This tool shows exactly which of those you are missing.
Then the block is no longer your headers. Cloudflare, DataDome and Akamai also compare your TLS/JA3 fingerprint to known browsers and check IP reputation. Use curl_cffi or curl-impersonate to match a real browser TLS handshake, and route through rotating residential or mobile proxies.
Point your scraper at the checker endpoint instead of your target, then read the JSON it returns. It lists the headers it received and a verdict, so you see your scraper exactly as a server sees it.
No. The endpoint reads the request headers, returns the verdict, and stores nothing.
Related Tools
Proxy Tester
Free online proxy tester tool. Test up to 10 proxies at once - check latency, exit IP, geolocation, and VPN/proxy detection. Real-time results.
User Agent Generator
Free user agent generator tool. Create realistic user agent strings for Chrome, Firefox, Safari, Edge across Windows, macOS, Linux, Android, and iOS.
Proxy Calculator
Free proxy calculator. Tell it your web scraping volume or how many social accounts you run, and it tells you how many proxies you need, which type, and roughly how much bandwidth.
Let's start our journey with a personal gift for you ❤️
WELCOME12