HTTP Status Checker
Check HTTP status codes and redirect chain for a URL with headers, server info and timing
This tool sends network requests to the target URL.
Overview
HTTP status codes are three-digit numbers that indicate the response status from a web server.
200 - Success
301 - Moved Permanently
302 - Found
404 - Not Found
500 - Server Error
503 - Service Unavailable
Documentation
What is this tool?
The HTTP status checker inspects a target URL's status code, redirect chain, and response headers to help troubleshoot access issues and cache behavior.
Key Features
- Show status codes and reason phrases for each request
- Display the full redirect chain and target URLs
- Provide headers, server IP/port, and elapsed time
- Extract page titles to quickly identify destinations
How to use
1
Enter an http/https URL to check
2
Click Check and wait for results
3
Review status codes, redirects, and headers
4
Use the details to diagnose or optimize caching
About HTTP response status codes
HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Status codes are grouped into ranges:
- Informational responses: 100–199 The server received the request and the client should continue.
- Successful responses: 200–299 The request was received, understood, and accepted.
- Redirection responses: 300–399 Further action is needed to complete the request.
- Client error responses: 400–499 The request contains bad syntax or cannot be fulfilled.
- Server error responses: 500–599 The server failed to fulfill a valid request.
Detailed HTTP status codes:
| Code | Description |
|---|---|
| 100 | The client should continue the request; ignore it if already completed. |
| 101 | The server is switching protocols. |
| 102 | The server has received and is processing the request, but no response is available yet. |
| 103 | The server sends early hints about likely resources while processing the main request. |
| 200 | The request succeeded. |
| 201 | The request succeeded and a new resource was created. |
| 202 | The request has been accepted but not yet processed. |
| 203 | The request succeeded, but the returned metadata is from a different source. |
| 204 | The request succeeded but there is no content to return. |
| 205 | The request succeeded and the client should reset the document view. |
| 206 | The response contains partial content for range requests. |
| 207 | Multiple status codes for multiple resources. |
| 226 | The server fulfilled the request and the response represents instance manipulations. |
| 300 | Multiple choices are available; the user agent should choose one. |
| 301 | The resource has been moved permanently and a new URL is provided. |
| 302 | The resource is temporarily located at another URL. |
| 303 | See other; retrieve the resource with GET at another URI. |
| 304 | Not modified; the cached version can be used. |
| 307 | Temporary redirect; repeat the request with the same method. |
| 308 | Permanent redirect; the resource is at another URI. |
| 400 | Bad request due to invalid syntax or other client error. |
| 401 | Authentication is required to access the resource. |
| 403 | Forbidden; the server refuses to authorize the request. |
| 404 | The requested resource was not found. |
| 405 | The method is not allowed for the target resource. |
| 406 | No acceptable representation was found after content negotiation. |
| 407 | Proxy authentication is required. |
| 408 | The request timed out. |
| 409 | The request conflicts with the current state of the server. |
| 410 | The resource is gone and no forwarding address is known. |
| 411 | Content-Length is required. |
| 412 | A precondition in the request failed. |
| 413 | The request entity is larger than the server is willing to process. |
| 414 | The requested URI is longer than the server can handle. |
| 415 | The media type of the request is not supported. |
| 416 | The requested range cannot be satisfied. |
| 417 | The server cannot meet the expectations indicated by the Expect header. |
| 418 | I'm a teapot. A humorous status code; not to be taken seriously. |
| 421 | The request was directed to a server that cannot produce a response. |
| 422 | The request was well-formed but had semantic errors. |
| 423 | The resource is locked. |
| 424 | The request failed due to failure of a previous request. |
| 425 | The server is unwilling to risk processing a request that might be replayed. |
| 426 | The server refuses to perform the request using the current protocol. |
| 428 | The origin server requires the request to be conditional. |
| 429 | Too many requests were sent in a given amount of time. |
| 431 | Request header fields are too large. |
| 451 | The user agent requested a resource that cannot be legally provided. |
| 500 | The server encountered an unexpected condition. |
| 501 | The server does not support the functionality required to fulfill the request. |
| 502 | The server received an invalid response from an upstream server. |
| 503 | The server is not ready to handle the request. |
| 504 | The server, acting as a gateway, did not get a response in time. |
| 505 | The server does not support the HTTP version used in the request. |
| 506 | The server has an internal configuration error. |
| 507 | The server is unable to store the representation needed to complete the request. |
| 508 | The server detected an infinite loop while processing the request. |
| 510 | Further extensions to the request are required for the server to fulfill it. |
| 511 | Network authentication is required to gain access. |
These status codes are defined in section 10 of RFC 2616. You can find the latest definitions in RFC 2616 and RFC 7231.
If you see status codes not listed here, they may be non-standard responses defined by specific software systems.
FAQ
Why are there multiple requests?
The target URL may redirect; the tool lists each hop and its status.
Why does it differ from my browser?
Servers may respond differently based on headers or network conditions, and caches can also affect results.
What if the check fails?
Confirm the URL is reachable and try again later. Restricted or private addresses may be inaccessible.
Notes
- Only HTTP/HTTPS URLs are supported.
- Requests are made from the server, so results may differ from your local network.
- Some sites may rate-limit or block automated requests.