HTTP Status Code Checker
Check up to 10 URLs at once. Our server requests each one and follows redirects hop by hop, so you see the first status code, every redirect in the chain, the final URL and its status, and how long each response took.
Status code quick reference
How to use the HTTP Status Code Checker
Paste up to 10 URLs
One per line. URLs without http(s):// are treated as https://.
Run the check
Results fill in as each chain completes.
Open any chain
Expand a row to see every hop, its status, Location header and time.
Act on problems
Fix broken links, collapse chains, and replace temporary redirects that should be permanent.
What it checks
- First response
- The status code returned for the URL exactly as entered.
- Redirect chain
- Every hop, up to 10, with status, Location header and resolved next URL.
- Final result
- The URL that finally responded without redirecting, and its status.
- Timing
- Response time for each hop and the total, measured from our server.
- Loops and limits
- Redirect loops and chains longer than 10 hops are reported as such.
- Headers
- Content type and any X-Robots-Tag header on the final response.
Interpreting the results
Each row shows the requested URL, the first status, the number of redirects, the final URL and status, and total time. The reference below summarises the codes you'll meet most:
| Code | Meaning | SEO relevance |
|---|---|---|
| 200 | OK | The page loaded. Indexable pages should return this. |
| 301 / 308 | Permanent redirect | Signals generally consolidate to the new URL. |
| 302 / 307 | Temporary redirect | Fine for short-term moves; use 301 for permanent ones. |
| 304 | Not modified | Caching response; rare on a fresh request. |
| 403 | Forbidden | Access refused — sometimes only for automated requests. |
| 404 | Not found | Fix or redirect links pointing here. |
| 410 | Gone | Deliberately removed; a clearer signal than 404. |
| 429 | Too many requests | Rate limited — try again later. |
| 500 | Server error | Persistent errors can lead to pages dropping out of results. |
| 502 / 503 / 504 | Gateway / availability | Often temporary: overload, maintenance or upstream failure. |
Connection failures — DNS errors, timeouts, invalid certificates — are shown as errors, not status codes. If our server couldn't reach a URL, the tool says so; it never shows a guessed result.
Detected marks facts read directly from what you provided or what our server actually received. Guidance marks general recommendations based on those facts — rules of thumb, not guarantees or search engine requirements.
Practical guidance
Check the URLs that matter most: pages that receive backlinks, URLs in your sitemap, and old addresses after a migration. A realistic example: after a redesign, ten old URLs with backlinks are checked. Six return a single 301 to the right page, two return 404 and two go through a 302 and then a 301. The 404s get redirects to their closest new equivalents and the chains are collapsed into single 301s — so the value of those old backlinks isn't left pointing at dead ends.
Before building new links, confirm the target returns 200 directly — the first item in the target-page checklist on our PBN backlinks page. Generate clean redirect rules with the Redirect Rule Generator, and use the SEO Page Analyzer to review what the final page actually contains.
Limitations
- Only server-side (HTTP) redirects are followed. JavaScript and meta-refresh redirects happen in a browser and aren't seen.
- Some servers respond differently to automated requests, data-centre IPs or different countries. Results reflect what our server received.
- Private, local and reserved addresses are blocked, only ports 80 and 443 are allowed, and each request times out after 12 seconds.
- Up to 10 URLs per check, and a fair-use rate limit applies.
Frequently asked questions
Does the checker follow redirects?
Yes — up to 10 hops per URL, validating every hop, and shows the full chain.
Why do I see 403 when the page works in my browser?
Some servers and firewalls block automated requests or requests from data centres. The result is still real: it's what our server received.
How many redirects are too many?
Aim for one at most. Each hop adds delay and some crawlers stop following after a few.
Can it check pages on my local network?
No. For security, private, local and reserved addresses are blocked.
Related tools
- Redirect Rule Generator
Create 301/302 redirect rules for Apache .htaccess or Nginx from a list of URLs. - SEO Page Analyzer
Fetch a live URL and review status, tags, headings, links, images and schema in one report. - Canonical URL Checker
Find self-referencing, missing, relative, conflicting or misplaced canonical tags. - XML Sitemap Validator
Check sitemap XML for syntax, namespace, URL, lastmod, duplicate and size problems.
More in Technical SEO Tools · All 25 free SEO tools