Open Terminal

Redirect Checker

Available

Follow every redirect of a URL and see each hop with its HTTP status code, Location header and timing, up to the final destination.

Check a URL

Without a scheme, https:// is assumed. Add http:// to test the HTTP → HTTPS redirect.

Some sites redirect phones or bots differently.

Try:

Redirect chain

Enter a URL to see every redirect up to the final destination.

How it works

The NetTools server requests the URL without following redirects automatically, reads the status code and Location header, then requests the next URL itself, up to 10 hops. That makes every step visible, including loops, downgrades from HTTPS to HTTP and temporary redirects used for permanent moves.

Redirect status codes

  • 301 Moved Permanently / 308 Permanent Redirect: the page has moved for good. 308 also keeps the request method (POST stays POST).
  • 302 Found / 307 Temporary Redirect: temporary; the original URL stays the canonical one. 307 keeps the method.
  • 303 See Other: usually after a form submission, always followed with GET.

Safeguards & responsible use

  • Every hop is checked again: redirects to private, local or non-http(s) addresses are not followed (SSRF protection).
  • At most 10 redirects and short per-request timeouts; response bodies are not downloaded.
  • Per-client rate limits; URLs are not stored.

Frequently asked questions

301 or 302 — which should I use?

301 (or 308) for permanent moves: search engines transfer the old URL’s signals to the new one. 302 (or 307) for temporary redirects, where the original URL should stay indexed.

Why are long redirect chains a problem?

Each hop adds a round trip, and crawlers stop following after a number of hops. Redirect old URLs straight to the final destination.

Are JavaScript and meta-refresh redirects detected?

Only HTTP redirects (3xx with a Location header) are followed. Redirects done by JavaScript or <meta http-equiv="refresh"> happen in the browser and are not part of the chain.