Redirect Checker

Follow a URL’s redirect chain and check HTTPS upgrades and redirect types.

Website security Live check from this server, against public hosts only.

About the Redirect Checker

Redirects send visitors and crawlers from one address to another. Long chains slow down page loads, temporary (302) redirects for permanent moves can confuse search engines, and a redirect from HTTPS back to HTTP exposes visitors.

The checker follows up to five redirects, shows every hop with its status code, and checks that plain HTTP is upgraded to HTTPS, that the chain is short, and that permanent moves use 301 or 308.

How to use it

  1. Enter the starting address (http:// shows the HTTPS upgrade).
  2. Run the check.
  3. Review each hop and the warnings.

Frequently asked questions

What is the difference between 301, 302, 307 and 308?

301 and 308 are permanent; 302 and 307 are temporary. 307 and 308 keep the request method (a POST stays a POST), while 301 and 302 may change it to GET. Use 301 or 308 for moved pages, 302 or 307 for temporary detours.

How many redirects are too many?

Aim for one hop. Google follows up to 10, but every extra hop adds latency, especially on mobile networks. Point old URLs straight to the final address.

Is an HTTP to HTTPS redirect enough?

It is necessary but not sufficient: the first plain-HTTP request can still be intercepted. Add HSTS so browsers go straight to HTTPS next time, and consider HSTS preloading.

All free tools