Toolsky

Free Online Tools & Utilities for Every Task.

Redirect Checker

Checker whether a URL has a Redirect.

A shortened link, an old bookmark, a URL from a migration checklist — click any of them and your browser may quietly bounce through two or three addresses before landing. A redirect checker makes that invisible journey visible. Enter a URL and it follows the trail hop by hop, reporting each address visited, the HTTP status code that sent you onward, and where the chain finally ends. What looks like one click is often a small relay race, and this tool shows you every handoff.

What This Redirect Checker Shows You

Instead of reporting only the destination — which your browser already shows you — the checker lists the entire path: the URL you entered, each intermediate address, the status code responsible for each move, and the final response. That detail separates healthy behaviour from trouble. A single 301 hop from http to https is a site doing its job. A chain of four redirects mixing temporary and permanent codes, crossing between www and bare domain twice, is a site wasting its visitors' time and muddying its own search signals. The checker turns suspicions like "this link feels slow and weird" into a concrete list you can hand to a developer. For the official semantics of each code, MDN's guide to HTTP redirections is the reference worth bookmarking.

The Redirect Types You Will Meet

  • 301 Moved Permanently — the address has changed for good; browsers cache it and search engines transfer ranking signals to the new URL.
  • 308 Permanent Redirect — the modern permanent redirect that also preserves the request method and body.
  • 302 Found — a temporary move; the original address remains the canonical one.
  • 307 Temporary Redirect — the temporary equivalent of 308, method preserved.
  • Meta refresh and script redirects — moves performed by the page itself rather than an HTTP response; slower, and easy to overlook because they happen after the page loads.

How to Check a URL's Redirects

  1. Paste the complete URL you want to investigate, including its http or https scheme.
  2. Start the check.
  3. Read the chain from the top: each row is one hop, with its status code.
  4. Note the final destination and its status — a healthy chain ends in a 200.
  5. Count the hops. One or two is routine; long chains deserve a cleanup.
  6. If the chain never ends, you have found a redirect loop — a configuration bug to fix, not a curiosity.

A Worked Example: Three Hops to a Homepage

A shop owner tests the address printed on her packaging, http://shop.example.com. The checker reports: hop one, a 301 to https://shop.example.com — the HTTP-to-HTTPS upgrade, entirely proper. Hop two, a 301 to https://www.shop.example.com — the site's preferred www host, also fine on its own. Hop three arrives with a 200. Nothing is broken, yet every customer who types the printed address pays two extra round trips before the page even begins loading, and on a slow mobile connection that is a visible pause. The fix is a single server rule sending the printed address directly to the final URL — one hop instead of two. This pattern, harmless-looking hops compounding across a whole site's old links and ads, is the single most common finding, and it pairs naturally with a status audit through an HTTP status code checker when you are surveying many pages at once.

Problems a Redirect Check Uncovers

Beyond long chains, watch for these: redirect loops, where A sends to B and B sends back to A until the browser gives up; downgrade hops that land a visitor back on insecure http mid-chain; temporary 302s used for permanent moves, which tell search engines to keep crediting the old address; and chains that begin with a URL shortener, stacking an outside service's hop on top of your own — an URL unshortener specialises in peeling exactly that first layer. Also check parameters: marketing links tagged with UTM codes sometimes lose their tracking through a careless redirect, which shows up later as mysteriously unattributed campaigns. When you find rules to rewrite on an Apache server, an htaccess redirect generator helps produce the replacement rules cleanly.

Frequently Asked Questions About Redirect Checking

How many redirects are too many?

Two is unremarkable, three is worth a look, and beyond that you are spending your visitors' patience and slowing every arrival. Search engines will follow longer chains, but each hop is another chance for something to break.

What is the difference between 301 and 302 redirects?

A 301 declares the move permanent, so browsers cache it and search engines transfer the old page's standing to the new address. A 302 declares it temporary, keeping the original address as the one that counts. Using 302 for a permanent migration is a common and costly mistake.

Why does my link end at a different page than I expected?

Because a chain is only as honest as its weakest rule: migrations, trailing-slash normalisation, language detection and shortener services can each add hops. The checker's hop list shows exactly which step diverted the journey.

Can a redirect chain hurt my search rankings?

Indirectly, yes. Long chains slow pages down — a ranking factor in itself — and any hop that errors or loops loses the visitor and the crawler alike. Clean, short, permanent chains for genuine moves are the safe standard.

What is a redirect loop and how do I fix it?

A loop is two or more rules sending a request back and forth forever; browsers report "too many redirects". The checker reveals the repeating pair, and the fix is correcting the conflicting rule, usually in your server configuration or a plugin.

Do redirects preserve my link's tracking parameters?

They should, but sloppy rules can strip query strings. Test the exact tagged URL you plan to share and confirm the parameters survive to the final destination before a campaign launches.

Why check redirects before sharing a shortened link?

Because a short URL hides its destination from everyone, including you. One check confirms it resolves to the page you intend — and not through a chain of strangers' domains on the way.

Know the Journey Before the Visitor Takes It

Every link you publish is a promise about where it leads. A thirty-second redirect check keeps that promise honest: short chain, permanent codes where the move is permanent, and a fast, clean arrival at the page you meant.