This redirect checker follows every hop a URL takes, with the status code, destination and time for each. It then gives a verdict on chains, loops and temporary redirects. On 3 October 2026, https://sqmagazine.co.uk answered 301 with a Location of https://sqmagazine.co.uk/, which answered 200. It’s free, and our own edge service makes the requests.
Final URL
https://sqmagazine.co.uk/
- Final URL
- https://sqmagazine.co.uk/
- Final status
- 200 OK
- Redirects
- 1
- Total time (ms)
- 160
- Verdict
- One permanent redirect, which is the ideal setup for a moved page.
- Checked as
- The checker's own agent
Every hop
| Hop | Status | URL | Location header | Time |
|---|
How this works
- How it works
- Requests are made from the network edge with redirects followed manually, up to ten hops and five seconds per hop. Only status lines and Location headers are read; page content is never downloaded or shown. Private and local addresses are refused.
- Privacy
- Nothing from this check is stored. The address you enter is fetched from the network edge, hop by hop, and the chain is sent straight back.
- Corrections
- Report a wrong result to media@sqmagazine.co.uk; every report is reviewed and confirmed errors are corrected. Include the inputs and the answer you expected. With your permission, we thank you by name on this page.
- Updates
- Published.
- Feedback
- How useful was this tool?
Table of Contents
How to Use the Redirect Checker
The redirect checker takes one address and returns 5 results plus a table of every hop, a quick way to check redirects on a single URL.
Google Search Central describes redirecting as the practice of resolving an existing URL to a different one. A live check runs once you change the address, pick an example or open a shared link; until then, the panel shows a stored example.
- Type or paste an address into “URL to check”. Include the scheme: the field’s own help says http:// and https:// often redirect differently. An address typed without one gets https:// added before the check. Browsers that remember a site’s Strict Transport Security policy skip the http:// hop entirely, as covered below.
- Or pick one of the “Examples” chips: “http:// to https://”, “google.com” or “github.com”. “Reset” puts the default address back.
- Read “Final URL”, “Final status”, “Redirects”, “Total time (ms)” and “Verdict”.
- Scan the “Every hop” table. Each row gives the hop number, its status, the URL requested, the “Location header” it sent back and the time it took.
- Press “Copy” for the final URL or “Copy all details” for the whole panel. “Share result” copies a link that reruns the check, and “Download CSV” saves the hop table.
Behind those five results sits a short set of rules.
How the Redirect Checker Traces Each Hop
Each check requests the address, reads the status line, and follows any 3xx answer to the address in its Location header, hop by hop.
The IETF’s HTTP Semantics standard says the 3xx class indicates that further action needs to be taken by the user agent in order to fulfill the request. The Location field is used in some responses to refer to a specific resource in relation to the response.
Our edge service reads those two things and nothing else. Page content is never downloaded or shown. It follows each hop by hand, up to ten hops and five seconds per hop, refuses private and local addresses, and stops at the earliest answer that isn’t a redirect.
Following by hand matters for a service that fetches other people’s URLs. OWASP’s server-side request forgery guidance tells developers to Disable the support for the following of the redirection in your web client, so a redirect can’t slip past the address checks.
RFC 1918 sets aside three blocks of the IP address space for private internets, and the edge won’t follow a hop into one. Ten hops is also Google’s ceiling: Google’s crawlers follow up to 10 redirect hops by default, according to Google’s crawler documentation.
From the hop list, the page builds its results. With H as the list of hops in order:
- “Final URL” = the URL of the last hop in H.
- “Final status” = that hop’s status code and reason phrase, such as 200 OK.
- “Redirects” = the number of hops in H whose status falls from 300 to 399.
- “Total time (ms)” = the edge’s total time for the whole chain.
- Permanent = the number of hops whose status is 301 or 308, a count the page uses for the verdict and doesn’t display.
“Verdict” checks these rules in order and stops at the one that fits:
- No answer at the end gives “The address did not answer”, or “The chain stopped at hop” after earlier hops.
- A repeat visit gives “Redirect loop detected: the chain returns to an address it already visited”.
- Running out of hops gives a verdict opening “Stopped after”.
- One permanent redirect gives “One permanent redirect, which is the ideal setup for a moved page”.
- One redirect of another kind gives “One temporary redirect. Use 301 or 308 if the move is permanent”.
- Two or more give the count and “redirects in a chain”.
- None gives “No redirect: the address answers directly”.
The loop rule follows the standard, which says A client SHOULD detect and intervene in cyclical redirections.
Run against the default address, those rules give a clean result.
Redirect Checker Example: https://sqmagazine.co.uk
SQ Magazine’s default address takes one permanent redirect to reach the home page. We traced it by hand with curl from our editorial server, one request per hop, the way the edge does:
- Hop 1, on 3 October 2026: https://sqmagazine.co.uk answered 301 with Location https://sqmagazine.co.uk/.
- Hop 2: https://sqmagazine.co.uk/ answered 200, a page rather than a redirect, so the chain ends.
- “Redirects”: 1 of the two hops sits in the 3xx range.
- “Verdict”: that hop is a 301, so the panel reads “One permanent redirect, which is the ideal setup for a moved page”.
- “Final URL” is https://sqmagazine.co.uk/ and “Final status” is 200 OK, matching the stored example the page shows on load.
- “Total time (ms)”: our two hops took 32 ms and 114 ms, 146 ms in all. The edge starts from a different place, so its own figure differs.
Our www address shows the chain verdict a URL redirect checker exists to catch. The same morning, http://www.sqmagazine.co.uk answered 301 with Location https://www.sqmagazine.co.uk/, which answered 301 again with Location https://sqmagazine.co.uk/ before the page answered. That is 2 redirects, so the tool reports “2 redirects in a chain” and suggests pointing the opening address straight at the final one.
Google’s site-move guidance agrees: we advise redirecting to the final destination directly. One rule sending every variant straight to https://sqmagazine.co.uk/ would leave a single hop.
What Your Redirect Check Means
A clean result ends on 200 OK after no more than one permanent hop. Any other verdict names something to look at.
A temporary hop is worth a closer look. Google says temporary redirects Show the source page in search results, so a 302 or 307 on a move you meant to keep holds the old URL there. The chain verdict counts hops but doesn’t single out a temporary one, so read the Status column of “Every hop” for any 302, 303 or 307.
A loop or a stop means the edge gave up before a final answer. The page waits up to eight seconds for the edge, so a long, slow chain can end in “The check service did not answer” instead of a verdict. “Total time (ms)” is measured from the edge, not from your connection.
The edge reads HTTP headers only, so a redirect built into the page itself reads as “No redirect: the address answers directly”. Google’s redirects guide covers both kinds the tool can’t see: meta refresh tags and JavaScript that changes the location. Google notes that it interprets and executes JavaScript using the Web Rendering Service once crawling of the URL has completed.
Many sites also answer from an edge network in front of their server, which is one reason timings vary; our Cloudflare statistics put one of those networks in numbers.
Behind each verdict sits what a status code means.
Redirect Status Codes Compared
RFC 9110 lists 301 (Moved Permanently), 302 (Found), 307 (Temporary Redirect), and 308 (Permanent Redirect) as redirects to a different URI. It treats 303 (See Other) as a pointer to a different resource.
| Code | RFC 9110 meaning | Google treats it as | The tool counts it as |
|---|---|---|---|
| 301 Moved Permanently | New permanent URI | Strong signal for the target | Permanent |
| 308 Permanent Redirect | New permanent URI | Equivalent to 301 | Permanent |
| 302 Found | Resides temporarily under a different URI | Weak signal for the target | Temporary |
| 303 See Other | Indirect response, mainly after a POST | Temporary redirect | Temporary |
| 307 Temporary Redirect | Resides temporarily; method must not change | Equivalent to 302 | Temporary |
Source: RFC 9110 (HTTP Semantics); Google Search Central; the tool’s verdict rules
A single 303 draws the temporary verdict even where it fits the job, since the code is primarily used to allow the output of a POST action to redirect the user agent to a different resource. How much traffic rides on search visibility is tracked in our Google SEO statistics.
Status codes aside, the checker also sees a hop your browser hides.
Why the Checker Shows a Hop Your Browser Skips
SQ Magazine’s home page sends a Strict-Transport-Security (HSTS) header, and that changes what your browser does with http://. The header reads max-age=63072000; includeSubDomains, a lifetime of 730 days. RFC 6797 says that for a host it knows, The UA MUST replace the URI scheme with “https” before loading.
So a browser that has visited before turns https://sqmagazine.co.uk into https:// on its own and never sends the request that earns the 301. The edge keeps no such memory. It shows the hop that every new visitor and crawler still makes.
Scheme defaults cut the other way. Type sqmagazine.co.uk with no scheme and the tool checks https://sqmagazine.co.uk/, which answered 200 directly, so the verdict reads “No redirect: the address answers directly”. To see the http:// hop, type http:// yourself.
That real request also reaches the link’s owner.
Checking Where a Link Goes Before You Click
Paste a shortened or unfamiliar link into “URL to check” and “Final URL” shows where it lands, without your browser opening it. That is the simplest way to get the real URL behind a redirect. CISA’s phishing guidance lists Untrusted shortened URLs among the common signs, on a page it now marks as archived.
Read the hops, not only the start. OWASP warns that with an open redirect, the server name in the modified link is identical to the original site, so a link can open on a trusted domain and end somewhere else. More patterns are in our guide to how phishing works.
The check is a real request. The link’s owner sees a visit from our edge, and a one-time link, such as a password reset or a sign-in link, may count as used. A clean “Final URL” also says nothing about whether the page behind it is safe.
What is the difference between 301 and 302 redirects?
A 301 says the target resource has been assigned a new permanent URI. A 302 says it resides temporarily under a different URI. For a 301, Google systems use the redirect as a strong signal that the redirect target should be processed; a 302 is only a weak one.
Google’s advice follows from that. If you just want to send users to a different page temporarily, use a temporary redirect; for a page that has moved for good, use a 301 or 308.
How many redirects are too many?
Google’s site-move guide asks for ideally no more than 3 and fewer than 5 hops when a chain can’t be avoided, because Chaining redirects adds latency for users. Its crawlers follow up to 10 redirect hops, the same ceiling as this tool.
Once a redirect exists, leave it in place: Google suggests keeping it generally at least 1 year. MDN puts the cost of each hop as the small performance hit of an additional round-trip.
Good to Know Before You Use It
The redirect checker sends the address you enter to our own edge service, which makes the requests, reads only status lines and Location headers, and never downloads page content. It assumes the address answers the edge as it would answer you, which a site that varies by location or device may not.
Per the tool’s method note, the edge follows redirects manually, up to ten hops and five seconds per hop, and refuses private and local addresses. Meta refresh and JavaScript redirects sit outside that method, as do certificates and whether a destination is safe.
SQ Magazine publishes this page for information. A redirect check helps reduce the risk of following a link blind; it promises no security outcome and can’t tell you whether the final page is safe.
Conclusion
On 3 October 2026, the redirect checker’s default address took 1 permanent redirect, a 301 to https://sqmagazine.co.uk/ that answered 200. That’s the clean result for an http-to-https move. Check every variant of your own address, with and without www and on both schemes, since each can take a different path. If you’re weighing where a site should live, our web hosting statistics compare the providers.
























































