Redirect Checker
This free redirect checker follows a URL hop by hop to its final page, showing each status code, where it points and how long it took, and flags loops and long chains.
Free, no signup. Try it with wikipedia.org.
What a redirect checker shows
It follows a URL the way a browser or search engine would: each redirect, its status code (301, 302, 307 or 308), where it sends you, and how long it took, until it reaches the final page.
Then it checks the chain for common problems: loops, more than two hops in a row, plain HTTP that never moves to HTTPS, bouncing between www and non-www, and a final page that returns an error.
301, 302, 307 and 308: which one to use
301 and 308 are permanent: search engines move the old address's ranking to the new one. 302 and 307 are temporary: search engines keep the old address in their index.
For a permanent move, like HTTP to HTTPS or an old page to a new one, use 301 (or 308, which also keeps the request method). Use 302 or 307 only for genuinely temporary changes.
Why long redirect chains hurt
Every hop is another round trip before the page starts loading, which mobile visitors feel most. Search engines also follow only a limited number of hops.
Point every old address straight at its final destination, so there's one redirect at most.
Do it on your hosting
Step-by-step guides from our knowledge base.
- How to Redirect Your Website to Any Page or External DomainKnowledge base
- How to Redirect a Page or Website Using htaccessKnowledge base
- How to Force HTTPS Using .htaccessKnowledge base
Frequently asked questions
What is a redirect loop?
A loop is when page A redirects to B and B redirects back to A (sometimes through more steps). Browsers give up with a "too many redirects" error. It's often caused by an HTTPS or www rule fighting a CDN or plugin setting.
Do you check meta refresh redirects too?
Yes. If the final page uses an HTML meta refresh, we flag it. Search engines and screen readers handle a server-side 301 much better.
Do you follow JavaScript redirects?
No. We don't run the page's JavaScript, so redirects done in JavaScript won't show. Search engines may not follow them reliably either, so a server-side redirect is the safer choice.
Why can't I check an IP address or a local server?
For safety, we only check public websites by domain name, on the standard ports. Internal addresses and IP addresses are refused, at the start and at every hop.
Dig deeper
HTTP Header Checker
Every response header a site sends, after its redirects, with the common ones explained in plain English.
See headersSecurity Headers Checker
Grades a site's HTTP security headers from A+ to F, with ready-to-paste fixes for Apache and nginx.
Grade a siteWho Is Hosting This Website?
Finds the company behind a website's server, and tells you honestly when a CDN is hiding the real host.
Find the host