Short URL Check: See Where a bit.ly Link Goes Before You Click

Contents
Why you can't tell from the address alone
A regular address leaves hints in the domain and path, like news.example.com/2026/07/…. A shortened address keeps only the shortener's domain and a random string, like bit.ly/xyzabc.
In other words, bit.ly isn't the destination. It's an information desk. Nothing happens until you knock, and then the desk tells you "go here" — so hovering over the link only shows you the short URL again.
To check, you need a way to ask the desk without actually going there. That's what the header check below does.
How to check without any tools
1) Request just the headers. Mac and Windows 10 or later ship with curl. Type this into a terminal (Command Prompt or PowerShell on Windows).
curl -I http://bit.ly/xyzabc
-I tells curl to skip the body and return only the response headers. Run it, and you get something like this.
HTTP/1.1 301 Moved Permanently
Location: http://www.pandora.com
The 301 on the first line is the "this moves" signal, and the Location line is the next address. You never opened the page, and you already have the destination.
2) See every stop along the way. Sometimes the destination forwards you somewhere else, so one look isn't enough to get the final landing page. Add -L and curl follows each hop, showing the headers at every step.
curl -sIL http://bit.ly/xyzabc
If all you want is the final URL on a single line, use this.
curl -sL -o /dev/null -w "%{url_effective}\n" http://bit.ly/xyzabc
3) The preview built into the shortener. On bit.ly, adding + to the end of the address (bit.ly/xyzabc+) opens that link's info page instead of redirecting, and shows you the destination. The catch is that this rule varies by service, so it may not work with other shorteners.
4) Already opened the link? Use your browser's dev tools. Open the Network tab in your browser's developer tools (usually F12), turn on the preserve log option, and load the link. Each step shows up as a 301 or 302 in the log. But this is a look-after-you-visit method, not check-before-you-click.
The problem is that you have to open a terminal, remember the flags, and pick the lines you need out of the output when there are several hops.
Checking with our tool. Paste the address and press 'Trace', and it walks the same steps one hop at a time and gives you a clean result.
Free, with no install or signup. A server follows each hop for you instead of your browser, and shows you the waypoints and the final destination.

At the top the screen shows the redirect count, below that each hop's hop number, status code, and address, and at the bottom the final destination. Status codes are color-coded: yellow for a redirect (3xx), green for a clean landing, red for a failure or error.
The input box needs the full address, including http:// or https://. If you paste only the domain part, you'll get a prompt asking you to check the format again.
What status codes tell you
Redirect responses are in the 300s. Each number has a fixed meaning.
Code
Meaning
301
Permanent move. Signals that this address will keep working going forward
302
Temporary move. Signals that you're being sent elsewhere just for now
303
Tells the client to request a different address instead
307
Temporary move. Preserves the original request method
308
Permanent move. Preserves the original request method
200
End of the redirects. This is the actual page
Two cautions. A 3xx without a Location header means no destination was specified. And 304 sits in the 300s but isn't a redirect — it's a cache response telling the client "nothing changed, use your saved copy."
307 and 308 exist because of the request method. With 301 and 302, implementations have long been inconsistent about whether to keep the original method, so 307 and 308 were nailed down to remove that ambiguity. When you're just clicking a link (a plain lookup), you won't notice much difference.
Where reading the chain gets tricky
Multiple hops don't make a link suspicious. Trace Wikipedia's short URL http://w.wiki/4Jx and you'll see 301 twice. The first hop upgrades http to https, and the second goes to the actual article.
It's also common to see an extra hop for a separate mobile page, for merging an old domain into a new one, or for appending campaign parameters to the end of the URL.
Some redirects don't show up in status codes. Moves done with a meta refresh inside the page or with JavaScript don't happen in the HTTP response — they happen after the page opens. In that case header tracing looks like it ended at 200, so it's still possible for the final page to hand you off somewhere else.
A final 200 is not a safety verdict. 200 only means "there's a page at that address." The judgment comes from a human reading the destination domain.
Read domains from the right. In an address, the domain runs from after // up to the first /, and what actually decides the site is the rightmost part of it. For example, the real domain in https://example.com.abc-login.top/pay is abc-login.top, not example.com.
The check never opens in your browser. Our tool sends the request from our server instead of your browser, so your IP and cookies never reach the destination. The shortener itself does see one request come in, though, so it may be counted as a click.
Some links loop forever. If two addresses point at each other, the redirects never end. That's why this tool stops at 10 hops and tells you "Stopped after 10 redirects (possible infinite loop)."
The short version
- A shortened address only reveals its destination once you click, but reading the
Locationheader lets you check without opening anything. curl -I URLshows the headers, andcurl -sIL URLshows every hop. Both are built into Mac and Windows 10 or later.- 301 is a permanent move and 302 is a temporary one. 304 is not a redirect — it's a cache response.
- Two or three hops is normal (https upgrade, domain consolidation, campaign parameters).
- A final 200 means "it opens." Read the destination domain from the right end and check it with your own eyes.
Free, with no install or signup. A server follows each hop for you instead of your browser, and shows you the waypoints and the final destination.
Frequently asked questions
Can you really find out where a link goes without clicking it?
Yes. When the shortener gets the request, it doesn't take you to the destination — it returns a redirect response (301 or 302) with a Location header saying "go to this address." Read that header and don't follow it, and the destination page never opens. That's exactly what curl -I does, and it's what this tool does too: instead of following redirects automatically, it stops at each hop and reads the response.
What's the difference between 301 and 302?
301 is a permanent move — "this is where it goes from now on." 302 is a temporary one — "I'm sending you there just this once." Browsers and search engines treat a 301 as an address change, and a 302 as the original address staying in place. From the checking side, both mean the same thing: there's a next address.
Is a link with 3 or 4 redirects suspicious?
Not on its own. An http-to-https upgrade, an old domain folding into a new one, a redirect to a mobile page, and a campaign parameter being added can easily stack up to three or four hops. What matters isn't the count — it's the domain you finally land on.
Does a final 200 mean it's safe?
No. 200 only means "there's a page at that address and it responded normally." It says nothing about the content. You still need to check whether the destination domain is really the site you know (especially the rightmost part) and whether the page asks for login or payment details. If you're unsure, don't follow the link — go to the service's app or type in its address yourself.
This article was adapted from our Korean original. Read the Korean original