Status Codes, Headers, Redirect Chains
Paste up to 100 URLs and see exactly what each one returns — status codes, response headers, and the full redirect chain hop by hop.
Free, no account. Pick from 30+ user agents (including AI crawlers). Filter results, copy URLs, and export to CSV.
Lower if you get 429 Too Many Requests errors
What the Status Codes Mean
Every HTTP response falls into one of these groups. The tool colours each badge by group so problems jump out.
Success. Request succeeded. 200 OK is the standard healthy response.
Redirect. Moved. 301 is permanent (passes link equity), 302/307 are temporary.
Client error. Request is invalid or the page doesn't exist. 404 is the most common.
Server error. Server failed to handle the request. 500, 502, 503 are typical.
Transport error. DNS failure, TLS error, timeout, or refused connection — no HTTP response at all.
Try It With These Examples
Click Load examples in the tool above to pre-fill the textarea with these three URLs.
https://serp.tools/
A healthy page. Single hop, status 200, no redirect.
https://www.serp.tools/
A canonical redirect. The www variant 301-redirects to the apex domain and resolves cleanly.
https://serp.tools/idonotexist
A missing page. The server responds, but the resource doesn't exist at that URL.
When This Tool Is Useful
After a site migration. Verify every old URL returns the right status code and lands at the right destination.
Crawl-budget audits. Find redirect chains (A→B→C) and collapse them to single-hop redirects.
Pre-launch QA. Confirm key URLs return 200 and redirects send the right status codes before going live.
Post-deploy regression checks. Run a known URL list after each deploy to catch routing breakages immediately.
AI-crawler debugging. Test how GPTBot, ClaudeBot, or PerplexityBot see your URL — useful for AI-search visibility. For a single URL across 20+ AI bots at once, use the AI Bot Access Tester.
About Redirect Chains
A redirect chain happens when one redirect leads to another before reaching the final URL — for example
http://example.com → https://example.com → https://www.example.com/page/.
Each hop adds 50–150ms of latency and wastes crawl budget. This tool reveals every hop so you can spot and collapse them.
Have an old→new redirect map to verify?
This tool tells you what a URL does. To confirm a URL does exactly what you planned — right destination, right status code — use the Bulk Redirect Checker. Upload your migration spreadsheet and get a row-by-row pass/fail verdict for every redirect.
Related tools in your workflow:
- → Bulk Redirect Checker — verify your old→new redirect map after a site migration
- → Bulk Indexability Checker — once a URL returns 200, check whether it's actually indexable
- → AI Bot Access Tester — check how 20+ AI crawlers see a single URL, including robots.txt rules
- → Robots.txt Validator — make sure key URLs aren't blocked from crawlers
- → XML Sitemap Checker — pull every URL out of a sitemap so you can run it through this tool
Frequently Asked Questions
Why does the tool show a different status code than my browser? ▾
The most common cause is user-agent detection — the server returns a different response to bots than to browsers. Try switching the user agent to "Your Browser" to simulate a real visitor. Cookies and session state can also matter; pages requiring login will return a different status without an authenticated session.
What does a status code of 0 mean? ▾
A code of 0 is a transport-level failure — the tool could not establish a connection at all. This happens when a domain doesn't exist (DNS failure), the SSL certificate is invalid, the connection times out, or the server actively refuses the connection. It is different from a 4xx or 5xx, which requires a successful connection.
Why do some URLs show 503 in the tool but work fine in my browser? ▾
503 Service Unavailable is often returned to bot user agents by CDN services (Cloudflare, Fastly, Akamai) with bot protection enabled. Try switching the user agent to "Your Browser" or "Googlebot" to determine whether the 503 is bot-blocking or a genuine server issue.
How does the parallel requests setting affect results? ▾
It controls how many URLs are fetched simultaneously. Higher values are faster but send more concurrent requests to the same server. If you see 429 Too Many Requests errors, drop it to 5–10 and retry.
What's the difference between this and the Bulk Redirect Checker? ▾
This tool is for discovery — paste a URL list and see what each one does. The Bulk Redirect Checker is for validation — you already have an old→new redirect map and want to confirm every redirect lands at the expected destination with the expected status code.
How many URLs can I check at once? ▾
Up to 100 URLs per check. For larger lists, run them in batches of 100, or use a desktop crawler like Screaming Frog for site-wide audits.
Free account unlocks more
Now (no account)
- –AI calls: 3 per session
- –Tool result history: Not saved
- –Referral bonus AI calls: —
- –Early access to new tools: —
Free account
- ✓AI calls: 10 per day
- ✓Tool result history: Last 30 days
- ✓Referral bonus AI calls: +50 on referral
- ✓Early access to new tools: Newsletter updates