- Home
- Redirect Checker
Redirect Checker
Enter a URL and see every redirect between it and the page that finally loads, with the status code and timing of each hop. Spot chains that are too long, temporary redirects that should be permanent, loops and broken destinations.
Why redirects matter
Every site has redirects, whether you set them up or not: plain http:// goes to https://, one of www and the bare domain goes to the other, and old pages point to new ones after a redesign. Done well, visitors never notice. Done badly, they slow pages down, waste crawl budget, and make links that point to your old addresses count for less than they should.
This checker requests the address you enter exactly once per hop, reads the Location header instead of letting the browser follow it silently, and lists each step. The final line shows the page that actually loads and its status.
Status codes you will see
| Code | Meaning | Use it for |
|---|---|---|
| 301 | Moved permanently | Domain moves, http → https, old URLs after a redesign |
| 308 | Permanent, keeps the request method | The same as 301 for APIs and forms |
| 302 | Found, temporary | Short-lived moves; often used by mistake for permanent ones |
| 307 | Temporary, keeps the method | Temporary moves; also what HSTS shows inside browsers |
| 200 | OK | The destination page loaded |
| 404 / 410 | Not found / gone | The redirect points at a page that no longer exists |
| 5xx | Server error | The destination is down or misconfigured |
Checks we run on every chain
- Chain length: more than one redirect is flagged, with a suggestion to point the first hop straight at the final address.
- Temporary redirects: a 302 or 307 in a chain that looks permanent is flagged, because search engines may keep the old address indexed.
- HTTPS downgrade: a chain that starts on https:// and ends on http:// is a security and SEO problem.
- Broken destination: a chain that ends on a 4xx or 5xx sends visitors and link value to an error page.
- Loops: a chain that returns to an address it already visited is stopped and reported.
Redirects and links
If you build links, redirects affect you twice. Links to an address that redirects still work, but each extra hop is a chance for something to break later, so ask for links to your final address. And when you place a link on someone else's site, for example in a blog comment, check that it does not get rewritten through a redirect script: some sites wrap outbound links in /go/ or /out/ URLs that pass little or no value. The RipeLinks extension rechecks the links you place and records their rel attribute, so you can see which ones were rewritten or removed.
Related tools
Look up a domain
WHOIS Lookup
Registrar, creation and expiry dates, status and name servers from the registry.
Domain Age Checker
How old a domain is, when it was first archived and whether it changed hands.
DNS Lookup
A, AAAA, MX, NS, TXT, CNAME, SOA and CAA records in one view.
SSL Checkercoming soon
Certificate issuer and expiry date.
Check a live site
Robots.txt & AI Crawler Checker
Whether Googlebot, GPTBot, ClaudeBot and others may crawl a page.
Open Graph Checkercoming soon
Preview how a link looks when shared.
Build links with the RipeLinks extension
Found a blog worth a comment? The free RipeLinks extension checks the page, drafts a comment from the article with your own AI key, fills the form for you to review, and rechecks the link a week later.
Frequently asked questions
301 or 302: which redirect should I use?
Use 301 (or 308) when the move is permanent, such as http to https, www to the bare domain or an old URL to its new home. Search engines then index the destination and pass signals to it. Use 302 (or 307) only when the original address will come back, such as a temporary maintenance page.
How many redirects are too many?
Google follows up to ten hops, but each hop adds a round trip, and link signals are safest with one. Aim for a single redirect from any old address to the final one. Two in a row, like http → https → www, is common and harmless, but easy to fix.
Why does the checker see something different from my browser?
Some sites redirect by country, language, device or cookie, and some block automated requests. The checker sends a plain request from a data centre without cookies, which is close to what a search-engine crawler sees. JavaScript and meta-refresh redirects are not followed because they need a browser.
Does it follow redirects to other domains?
Yes, as long as the destination is a public web address. We stop at private network addresses, non-standard ports and loops, and after ten hops.
What does a redirect loop look like?
The chain comes back to an address it already visited, for example https://example.com → https://www.example.com → https://example.com. Browsers show “too many redirects”. It is usually two settings fighting each other, such as a host forcing www while a plugin forces the bare domain.