Redirect & HTTP header checker
Enter a URL to see each redirect step, its status code and how long it took, plus the response headers of the final page.
What to look for
- More than one hop before the final page: update links and canonical tags to point at the final URL.
- 302 or 307 where the move is permanent, such as HTTP → HTTPS: use 301 or 308.
- A redirect loop: two URLs redirecting to each other, often a CDN and the origin disagreeing about HTTPS or
www. - Missing security headers on the final page:
strict-transport-security,x-content-type-options,content-security-policy.
Every status code is explained in our HTTP status code reference.
Frequently asked questions
What is a redirect chain?
A chain is when one URL redirects to another that redirects again, for example http:// to https:// to www. Each hop adds a round trip, so link directly to the final URL and keep chains to one hop where you can.
Should I use a 301 or a 302 redirect?
Use 301 (or 308) when the move is permanent, such as HTTP to HTTPS or an old URL to a new one. Use 302 (or 307) only for temporary moves. Search engines treat permanent redirects as a signal to index the new URL.
Why does the checker show a different result than my browser?
Browsers cache redirects (especially 301s) and send cookies. This tool makes a fresh request without cookies from Cloudflare's network, so it shows what a new visitor or a search engine sees.