HomeDevHTTP Status Checker
Web tools

HTTP Status Checker

Check HTTP status codes for any URL. Trace redirect chains, response timing, and key headers—like 200, 301, 302, 404, and 500. Works offline-ready.

Loading tool…

Loading Preparing tool…

How to use

Follow these steps for a clear answer.

1

Enter one or more URLs

Paste absolute URLs (one per line). Schemeless hosts get https:// automatically.

2

Check status

Optionally pick a crawler User-Agent, then run the check to fetch live server responses.

3

Read codes and redirect chains

Review each hop’s status, timing, Location, and final URL—useful after setting up 301s.

HTTP status checker specification

Version 1.1.0 · Last reviewed 2026-07-28

Definition
An HTTP status code is a three-digit server response that indicates whether a request succeeded, redirected, or failed.
What it calculates
Live HTTP status codes, optional redirect chains (up to 10 hops), per-hop timing, and selected response headers for public http(s) URLs.
Inputs
  • One or more absolute URLs (max 10; schemeless hosts normalized to https://)
  • User-Agent preset (checker, Googlebot, or Bingbot)
  • Follow redirects (on/off)
Outputs
  • Final status code and reason phrase
  • Redirect chain with status, Location, and latency per hop
  • Key response headers (Content-Type, Cache-Control, Location, security/CDN fields, …)
Formula
GET url (redirect=manual) → status + headers; if 3xx and Location → resolve next URL → repeat

Enter one or more public URLs to retrieve live HTTP status codes, redirect chains, and key response headers—useful for verifying 301 redirects, finding broken links, and debugging server responses.

Common HTTP status codes

Success (2xx)

Code Status Meaning
200 OK Request succeeded
201 Created Resource created
204 No Content Success, empty body

Redirection (3xx)

Code Status Meaning
301 Moved Permanently Permanent redirect
302 Found Temporary redirect
304 Not Modified Cached version still valid
307 Temporary Redirect Temporary, method preserved
308 Permanent Redirect Permanent, method preserved

Client error (4xx)

Code Status Meaning
400 Bad Request Invalid syntax
401 Unauthorized Authentication required
403 Forbidden Access denied
404 Not Found Page does not exist
410 Gone Permanently removed
429 Too Many Requests Rate limited

Server error (5xx)

Code Status Meaning
500 Internal Server Error Server malfunction
502 Bad Gateway Upstream server error
503 Service Unavailable Server temporarily down
504 Gateway Timeout Upstream timed out

Verifying redirects

After setting up a 301 redirect:

  1. Check the old URL — expect 301 (or 308) with a Location header
  2. Confirm the chain ends at the canonical URL with 200
  3. Prefer one hop; fix loops and long chains
  4. Re-check with Googlebot User-Agent if crawlers must see the same redirect

Tips

  • Use https:// (or omit the scheme—the tool adds https)
  • Compare www vs non-www and http vs https for canonical consistency
  • Pair with the HTTP Header Checker when you need the full header list
  • Large site audits: crawl with a dedicated SEO tool, then spot-check URLs here
Assumptions
  • Checks run on CalculatorX edge/servers, not in the visitor’s browser fetch sandbox.
  • Private, loopback, and link-local hosts are blocked (SSRF protection).
  • Bodies are not retained; only status, timing, and headers are returned.
  • Reason phrases follow common RFC 9110 / IANA names when the server provides them.
Units
  • Status code: integer (100–599)
  • Timing: milliseconds
  • URL: absolute http:// or https:// string
Boundary conditions
  • Maximum 10 URLs and 10 redirect hops per request.
  • Requests time out after about 12 seconds per hop.
  • Invalid URLs or blocked hosts return an error without a status.
  • Some hosts block datacenter IPs or specific User-Agents (403/429).
Example
https://example.com → 200 OK; http://example.com may 301 → https://example.com/ → 200
Validation cases
  • 200 response → Final status 200 with empty or short chain
  • 301 with Location → Chain shows 301 then destination status when follow is on
  • 404 URL → Final status 404
  • Follow redirects off → Single hop even when Location is present
Sources
  • RFC 9110 HTTP Semantics
  • IANA HTTP Status Code Registry
Last reviewed
2026-07-28
Calculation version
1.1.0
→ HTTP Header Checker › → 301 Redirect Code Generator › → URL Decoder & Encoder ›

Frequently asked questions

Key distinctions behind the tool.

What status code means a page is working?

200 OK means the request succeeded and the resource was returned. Other 2xx codes (201, 204) are also successful outcomes.

301 vs 302 — what’s the difference?

301 Moved Permanently tells clients and search engines to use the new URL going forward (SEO value typically transfers). 302 Found is temporary—the original URL may return later.

Why does my page show 404?

The server could not find the resource. Check typos, deleted pages, wrong paths, or a broken redirect that points at a missing URL.

Can I check multiple URLs at once?

Yes. Paste up to 10 URLs, one per line, then click Check status. For larger audits, use a crawler or scripting with curl.

Why can’t the browser check URLs by itself?

Cross-origin requests are limited by CORS. This tool proxies checks through CalculatorX so you can read status codes and headers for public sites.

Do redirects affect SEO?

Yes. Prefer a single 301 hop to the canonical URL. Long redirect chains slow crawlers and can dilute signals—keep chains short and consistent (http/https, www/non-www).

What User-Agent should I use?

Use the default checker for normal browser-like requests. Switch to Googlebot or Bingbot when you need to see how crawlers are treated (some sites vary by UA).