Redirect Checker

See where a public URL redirects and the path it takes.

Redirect checker

Final Status

Enter a public URL and check its redirects.

How it works

IngoHub requests the public URL, follows a small bounded number of redirects, and reports each hop plus the final status.

Example
STARTING URL
http://example.com
REDIRECT
301 Moved Permanently
FINAL URL
https://example.com/
FINAL STATUS
200 OK

Questions

What is a redirect?

A redirect is an HTTP response that tells the client to continue at a different URL. The checker reports each hop and the final status that URL returns.

What is the difference between 301 and 302?

301 Moved Permanently means the resource has a new lasting URL. 302 Found means the move is treated as temporary. Both can send a client to another address.

What are 307 and 308 redirects?

307 Temporary Redirect and 308 Permanent Redirect also send the client to another URL while keeping the original request method. This checker follows them when a Location header is present.

How many redirects are too many?

This checker follows at most five redirects. A longer chain is reported as too many redirects rather than a complete result.

Why should I check redirect chains?

A chain shows whether a URL moves, how many times, and where it ends. That helps confirm a canonical address and catch unexpected hops.

What is a redirect loop?

A redirect loop sends the client back to a URL already in the chain, such as A to B to A. The checker stops and reports that instead of repeating hops.

Does this tool follow redirects?

Yes. It follows a small bounded number of standard redirects with a Location header and lists every hop, including the final response.

Can I check localhost or private network URLs?

No. Only public HTTP and HTTPS URLs can be checked. Localhost and private network addresses are rejected, including when a public URL redirects to one.

Why can the result differ from my browser?

Browsers can send cookies, extra headers, or cached responses. This checker sends a simple server-side GET from IngoHub infrastructure, so the chain can differ.