↑↓ to move · Enter to open · Esc to close

Redirect Checker

Follow the redirects for one URL and see each hop's status, next address, and time.

This check runs on our server. The address you enter is used only for this check and is not stored.
Updated

This check runs on our server. The address you enter is used only for this check and is not stored.

How to use the Redirect Checker

  1. Enter a web address.
  2. Tick the robot check and press Check.
  3. Read the hops from top to bottom. The last row is where the chain stopped.

How it works

This check runs on our server. The address is not stored.

The first request uses GET. Each 301, 302, 303, 307, or 308 is another row, and the next request goes to the Location after it is resolved against the current URL. A relative location is resolved before the request. If that next URL was already in the chain, the page stops and says the chain looped. After 10 redirects it stops and says the chain was cut off.

Hops that leave http and https, or that point at an address that is not public, stop the chain with that reason. They are not fetched.

Examples

  • http://example.com returning 301 to https://example.com/ is two rows when the second response is 200: the 301 with its Location, then the final 200.
  • A chain that returns to a URL already seen stops on that repeat and names it.
  • An 11th redirect is not requested. The last row says the chain was longer than 10 hops.

Limitations

  • The chain is what our server receives. A redirect that depends on a cookie or a country can differ in your browser.
  • Only http and https on ports 80 and 443.
  • Ten hops is the maximum followed.

Frequently asked questions

Does 301 mean the host is down?

No. 301 means the next address is in Location. The last row that is not a 3xx is the page the chain reached.

Why did you stop at a private address?

The Location pointed at an address we do not fetch. The hop is listed, and the request is not made.

Do you store the URL?

No.

Often used together with the Redirect Checker.

  • HTTP Headers

    Status, final URL, and response headers from one GET.

  • HTTP Check

    HTTP status and response time from each available location, without downloading the page.

  • SSL Certificate

    Subject, alternative names, issuer, validity, and key type for the certificate on port 443.