HTTP Status Code & Redirect Checker

5 of 1 ratings

Enter a URL to see its status code, the full redirect chain and the response headers of every step. Without a protocol http:// is used.

URL

User-Agent

Request method

GET

HEAD

IP version

Auto

IPv4

IPv6

Auto uses IPv4 when the host has it. IPv4 or IPv6 forces that protocol for every step of the chain.

Advanced options

Custom User-Agent (used when "Custom" is selected)

Referer (optional)

Accept-Language (optional)

HTTP status codes

The status codes you will meet most often and what they mean.

1xx Informational

Code	Name	Meaning
100	Continue	The server received the request headers and the client can send the body.
101	Switching Protocols	The server agrees to switch the protocol, for example to WebSocket.
102	Processing	The server is still processing the request (WebDAV).
103	Early Hints	Preliminary headers that let the browser start loading resources early.

2xx Success

Code	Name	Meaning
200	OK	The request succeeded and the page or resource is returned.
201	Created	The request succeeded and a new resource was created.
202	Accepted	The request was accepted but the processing is not finished yet.
203	Non-Authoritative Information	The response was modified by a proxy.
204	No Content	The request succeeded and there is nothing to return.
205	Reset Content	The request succeeded and the client should reset the form or view.
206	Partial Content	Only a part of the resource is returned, as requested with a Range header.
207	Multi-Status	Several results in one response (WebDAV).

3xx Redirection

Code	Name	Meaning
300	Multiple Choices	There are several possible versions of the resource.
301	Moved Permanently	The page moved to a new address for good. Search engines transfer the signals to the new URL.
302	Found	The page is temporarily at another address. The old URL stays in the index.
303	See Other	The result is at another address and has to be requested with GET (typical after a form POST).
304	Not Modified	The cached copy is still valid, no body is sent.
307	Temporary Redirect	Temporary redirect that keeps the request method and body.
308	Permanent Redirect	Permanent redirect that keeps the request method and body.

4xx Client errors

Code	Name	Meaning
400	Bad Request	The server cannot understand the request because of a client error.
401	Unauthorized	Authentication is required.
402	Payment Required	Reserved, sometimes used for paid APIs.
403	Forbidden	The server understood the request and refuses to serve it.
404	Not Found	The page does not exist at this address.
405	Method Not Allowed	The HTTP method is not allowed for this resource.
406	Not Acceptable	The server cannot produce a response matching the Accept headers.
407	Proxy Authentication Required	Authentication with the proxy is required.
408	Request Timeout	The server timed out waiting for the request.
409	Conflict	The request conflicts with the current state of the resource.
410	Gone	The page was removed and will not come back. Search engines drop it faster than a 404.
411	Length Required	The request needs a Content-Length header.
412	Precondition Failed	A condition in the request headers was not met.
413	Content Too Large	The request body is larger than the server accepts.
414	URI Too Long	The URL is longer than the server accepts.
415	Unsupported Media Type	The format of the request body is not supported.
416	Range Not Satisfiable	The requested byte range is outside of the resource.
418	I'm a teapot	An April Fools joke from RFC 2324, sometimes used to block bots.
421	Misdirected Request	The request was sent to a server that cannot answer it.
422	Unprocessable Content	The request is well formed but its content is invalid.
425	Too Early	The server is not willing to process a request that may be replayed.
426	Upgrade Required	The client must switch to another protocol.
428	Precondition Required	The request has to be conditional.
429	Too Many Requests	Rate limit exceeded, slow down.
431	Request Header Fields Too Large	The request headers are too big.
451	Unavailable For Legal Reasons	The content is blocked for legal reasons.

5xx Server errors

Code	Name	Meaning
500	Internal Server Error	A generic server error, usually a bug or a misconfiguration.
501	Not Implemented	The server does not support the requested function.
502	Bad Gateway	A gateway or proxy got an invalid response from the upstream server.
503	Service Unavailable	The server is overloaded or down for maintenance. Search engines retry later.
504	Gateway Timeout	A gateway or proxy did not get a response from the upstream server in time.
505	HTTP Version Not Supported	The HTTP version of the request is not supported.
507	Insufficient Storage	The server cannot store the data needed to finish the request (WebDAV).
508	Loop Detected	The server detected an infinite loop (WebDAV).
511	Network Authentication Required	The client must authenticate to get network access, typical for public Wi-Fi.

HTTP Status Code Checker and Redirect Chain Tracer

Enter any URL to see the HTTP status code the server returns, every redirect on the way (301, 302, 303, 307 and 308) and the response headers of each step, together with the server IP address and timings. It is the quickest way to find out why a page does not open, where an old address really leads, or how many hops stand between a link and the final page.

What the checker shows

The whole redirect chain, step by step, with the status code and the address every step points to (relative addresses in the Location header are resolved for you)
Response headers of every step: Server, Content-Type, Cache-Control, Set-Cookie, X-Robots-Tag and the rest
Timings of each request: DNS lookup, connection, TLS handshake, time to first byte and total time
Server IP address, the A and AAAA records of the host and the HTTP version (HTTP/1.1 or HTTP/2), with a choice between IPv4 and IPv6
Hints about common problems: redirect loops, long chains, temporary redirects that should be permanent, http to https hops, noindex in the headers, slow responses

HTTP status code classes

1xx: informational, the request is being processed
2xx: success, 200 OK means the page was returned
3xx: redirection, the browser has to request another address
4xx: client errors, for example 404 Not Found or 403 Forbidden
5xx: server errors, for example 500 Internal Server Error or 503 Service Unavailable

The table under the checker lists the most common status codes and what they mean.

301, 302, 307 and 308: which redirect to use

301 Moved Permanently: the page moved for good. Search engines pass the ranking signals to the new address and replace the old one in the index. Use it for a changed domain, URL structure or the switch to https.
302 Found and 307 Temporary Redirect: the move is temporary and the old address stays in the index. Use them for short-term cases such as maintenance or an A/B test.
308 Permanent Redirect: like 301, but the browser must repeat the request with the same method and body (POST stays POST).
303 See Other: the result is at another address and is fetched with GET, typical after submitting a form.

Redirect chains and SEO

Every extra hop is one more request that slows the page down and wastes crawl budget, and long chains may be abandoned by crawlers. Aim for a single redirect from the old address to the final one: http to https and www to non-www (or the other way round) should happen in one step, not three. Redirect loops make the page unreachable. If the checker finds a chain, update internal links and sitemaps to point straight to the final URL.

Checking as a browser or as a search engine bot

Choose a User-Agent to see how the site answers different clients: Chrome on desktop or Android, Googlebot, Googlebot Smartphone, YandexBot, Bingbot or curl. You can also send your own User-Agent, a Referer and an Accept-Language. Keep in mind that only the User-Agent text is changed. Servers that verify real search engine bots by their IP address will still treat this request as a normal visitor, so the result can differ from what the real bot sees.

Checking over IPv4 or IPv6

Many sites are reachable over both IPv4 and IPv6, and a problem can exist in only one of them: a missing AAAA record, a server that does not listen on IPv6 or an IPv6 address that points to the wrong machine. Pick IPv4 or IPv6 to force that protocol for every step of the redirect chain, or leave Auto to use IPv4 when the host has it. For each step the checker also lists the A and AAAA records of the host and shows which address was used.

How to use the checker

Enter the address. If you leave out the protocol, http:// is used, so you can see whether the site redirects to https.
Pick a User-Agent and, if needed, the request method (GET or HEAD) and the extra headers under "Advanced options".
Press Check and read the chain from the first step to the final response.

For safety the checker only requests public web addresses (http and https on the standard web ports). Addresses of private networks and of the server itself are refused, and the checked addresses are not stored.