HTTP Status Checker

Check the real, live HTTP status code for a URL, including the full redirect chain and response time.

Input

Results

Status Code
—
Status Message
—
Response Time
—
Final URL
—

Redirect Chain

#URLStatus

Overview

The HTTP Status Checker requests a URL and reports what the server actually answers: the status code and message, the total response time, the final URL after any redirects, and every hop of the redirect chain.

Use it to confirm that a page is up, to find out where a short or old link really ends up, to debug redirect loops and redirect chains that are too long, and to see whether a server is returning errors such as 403, 404, or 503.

How It Works

This site's server sends an HTTP GET request to your URL and reads the response status line and headers; it does not download the page and never executes it. Redirect responses (status 3xx with a Location header) are followed one hop at a time, up to ten, and each destination is re-checked so that a redirect cannot lead the tool to an internal address. Every hop is recorded in the redirect chain table.

Status codes are grouped by their first digit as defined in RFC 9110: 2xx means success, 3xx means the client should look elsewhere, 4xx means the request was a problem from the server's point of view, and 5xx means the server failed. Response time is the total time for all requests in the chain, measured from this site's server, not from your own connection.

How to Use the HTTP Status Checker

  1. Enter a URL such as https://example.com/page. A bare domain is treated as HTTPS.
  2. Press Calculate.
  3. Read the final status, the final URL, and the redirect table to see each hop and its status.
  4. If the result is an error status, continue with the HTTP Headers Checker and the SSL/TLS Checker.

Worked Example

Following a redirect chain from an old http:// link

An old link, http://example.com/old-page, is reported as "slow". The sample below is illustrative.

Input

URL: http://example.com/old-page

Illustrative output

Status Code:    200
Status Message: OK
Response Time:  310 ms
Final URL:      https://www.example.com/old-page

Redirect Chain
#  URL                                 Status
1  http://example.com/old-page         301
2  https://example.com/old-page        301
3  https://www.example.com/old-page    200

This output is an illustrative sample to show the layout and meaning of each field. Real results depend on the target and on when you run the check.

Two 301 Moved Permanently responses sit in front of the real page. The first upgrades HTTP to HTTPS; the second adds www. Each hop costs a full round trip, which explains the extra delay. The fix is to link directly to the final URL, and, on the server, to make the first redirect go straight to the final address.

A 302 Found or 307 Temporary Redirect would mean the move is not permanent, so clients and search engines should keep using the original URL.

Interpreting Results

200 OK
The request succeeded and the server returned the resource.
301 / 308 (permanent) and 302 / 307 (temporary)
Redirects. Permanent redirects may be cached by browsers; temporary ones should not be. 307 and 308 additionally preserve the request method.
401 vs 403
401 Unauthorized means authentication is required or failed; 403 Forbidden means the server understood the request and refuses it, which can be a permission rule, a block of automated or data-center clients, or a web application firewall.
404 / 410
The resource is not found (404) or is intentionally and permanently gone (410).
429
You, or this tool's server, are sending too many requests to that site.
500 / 502 / 503 / 504
Server-side failures: a generic error (500), a bad answer from an upstream server (502), an overloaded or maintenance state (503), or an upstream timeout (504).

Troubleshooting

"Too many redirects" or a chain that never ends.
A redirect loop. Look at the chain for repeating URLs: typical causes are HTTP→HTTPS and HTTPS→HTTP rules fighting each other, a proxy/CDN that always redirects while the origin does too, or www/non-www rules pointing at each other. See the redirect-loop guide.
403 here, but the page opens fine in my browser.
Sites often block unfamiliar user agents or data-center IP ranges. This is the server's decision about this tool; it does not show what a normal visitor sees.
"Unable to reach that URL."
The host did not answer: it may be offline, blocked, or the DNS name may not resolve. Verify with the DNS Lookup.
"This target cannot be checked."
Private, loopback, and internal addresses are refused, as are hostnames that resolve to them, and any redirect that leads to one.

Limitations and Accuracy

  • The request comes from this site's server in the cloud, not from your location or network, so geo-restricted, VPN-only, or intranet pages will not behave as they do for you.
  • Only http:// and https:// are supported. The page body is never read or rendered.
  • Each request has an 8-second timeout, redirects stop after 10 hops, and requests are rate limited.
  • A server may respond differently depending on the client, language, or cookies, none of which this tool sends.

Data Handling

Uses server-side requests. The URL you enter is sent to this site's server function, which requests it from the target server (and looks up its DNS name to confirm it is a public address).
Sent to: The web server you named, plus Cloudflare's DNS-over-HTTPS resolver for the safety check. That server sees a request from this site's infrastructure, not from you.

Inputs travel as URL query parameters, so avoid entering confidential internal hostnames or personal data. See the Privacy Policy for how requests are handled.

Frequently Asked Questions

What is the difference between a 301 and a 302?

301 means the resource has moved permanently; 302 means it is temporarily elsewhere. The distinction affects caching and how search engines treat the URLs.

Why is the response time higher than I expect?

It includes every redirect hop plus DNS, TCP and TLS setup for each new host, measured from this site's server.

Can it test pages behind a login?

No. It sends no credentials or cookies, so you will see the login redirect or a 401/403.