We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Paste a short link to quickly reveal the original long URL. Expand shortened URLs safely and check where they redirect before clicking.
This tool supports popular short URL services (like t.cn, bit.ly, dwz.cn, etc.) and automatically follows redirects to uncover the original destination.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A shortened URL often responds by directing a browser to another address. HTTP uses 3xx status codes for redirection; a response can include a Location field naming the next target. This tool accepts one HTTP or HTTPS URL, follows HTTP redirect responses, and reports the original address, final address, redirect count, and hop details with status codes.
Read the chain from start to finish. Each redirect hop is a move from one address to another; the final response also appears in the hop list, so listed rows and redirect count differ. A result with zero redirects means the request reached a response without following a redirect. It does not establish that the address is trustworthy or intended.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Enter a full HTTP or HTTPS URL. If you omit the scheme, the input is treated as HTTPS. The form checks one address per run.
Choose the expand action or press Enter. A malformed address or unreachable destination produces a failure message.
Check the destination hostname and path, then inspect intermediate hosts and status codes when several hops appear. The reported count excludes the final response row.
Copy the destination if you need to inspect it elsewhere. Check the domain spelling and path yourself before opening it.
Use cases
See how the tool fits into real work and everyday tasks.
If a text message or post contains a shortened URL, inspect its destination before deciding whether to open it. Notice unexpected domain changes along the route.
An editor can verify that a shared URL resolves to the expected page and identify extra redirect steps added to an announcement or campaign link.
Q&A
Find concise answers to common questions and confusing cases.
No. It means this request did not follow an HTTP redirect. A direct-response page may still be deceptive, unsafe, or unintended.
No. It displays the resolved address and redirect path. You decide whether to open it after reviewing the result.
The site may be unreachable, return an error or interstitial, or use page-level or script-based navigation instead of an HTTP redirect. The chain covers the HTTP redirect responses the lookup can follow.
The list includes the final response address. The count measures transitions to another address, so the final row is not an additional redirect.
Notes
Review scope, result limitations, and important precautions before use.
Showing a final address does not scan it for phishing, malware, or harmful content. Page scripts and in-page refreshes are not represented as HTTP redirect hops. The lookup follows at most 10 redirects, so a longer chain may be incomplete. Treat unknown domains cautiously and verify the address through a trusted source before visiting.
Related
Discover related tools, collections, and available API capabilities.