Redirect Checker

About Redirect Checking

An HTTP redirect instructs a client to request a different URL. This tool follows the complete redirect chain for a URL — from the initial request through any intermediate redirects — and shows each hop with its status code, destination, and timing. This is essential for debugging redirect loops, verifying that HTTP-to-HTTPS redirects are working, or understanding complex redirect chains.

HTTP redirect status codes

• 301 Moved Permanently — The resource has permanently moved to a new URL. Browsers and search engines cache this redirect. Use for permanent URL changes.
• 302 Found — Temporary redirect. The resource is temporarily at a different URL. Browsers do not cache this. Search engines keep the original URL indexed.
• 303 See Other — Used after a form POST to redirect to a GET request (the Post/Redirect/Get pattern).
• 307 Temporary Redirect — Like 302 but guarantees the method is preserved (a POST stays a POST).
• 308 Permanent Redirect — Like 301 but preserves the HTTP method.

Common redirect patterns to check

• HTTP → HTTPS — Every HTTP request should redirect to HTTPS. Verify this is a 301, not a 302.
• www → non-www (or vice versa) — Canonicalisation should be a single 301 redirect.
• Trailing slash — Inconsistent trailing slash handling can cause redirect loops or duplicate content.
• Redirect chains — More than one redirect in a chain slows page loads and dilutes link equity in SEO. Aim for direct single-hop redirects.
• Redirect loops — A → B → A loops will cause a browser error. This tool shows where the loop occurs.