Reveal where shortened links really go
Paste any short URL — bit.ly, t.co, tinyurl.com, youtu.be, buff.ly and dozens more — and we’ll trace the full redirect chain, show the final destination, and preview the page’s title, description and image. No browser extension required.
Recent analyses
Browse all →
Most-analyzed providers
All providers →
Why TechLinkss
Safe by default
Internal SSRF protection blocks private network probes and disallows non-HTTP(S) schemes. Pages are scanned, never executed in your browser.
Full redirect chain
From the first short URL to the very last destination — every hop with status code, host and rewritten location header.
Rich previews
We extract the page title, description and Open Graph image so you know what the link is before you ever click it.
Permanent pages
Every analysis gets its own canonical URL at /u/<id>, so you can share the result without exposing private data.
No public API
All requests are server-rendered HTML. The internal scanner is never exposed to the public internet.
No tracking cookies
We don’t set advertising or analytics cookies on first visit. Ads, where present, are clearly labeled.
Frequently asked questions
What kinds of links can TechLinkss expand?
Any HTTP(S) URL that uses a redirect — including Bitly, t.co, TinyURL, ow.ly, buff.ly, youtu.be, lnkd.in, fb.me, l.facebook.com, l.instagram.com, snapchat redirect URLs, Amazon amzn.to, Telegram t.me, WhatsApp wa.me, and many more.
Is it safe to paste any short URL here?
Yes. Our scanner only performs HEAD/GET requests against the link, follows redirects, reads the response headers and the public HTML metadata. We never execute scripts. We block requests that resolve to private network IPs or to non-HTTP protocols.
Do you store the full URL I paste?
We keep a small record of analyzed links (the submitted URL, the final URL, the redirect chain and basic page metadata) so the result has a permanent /u/<id> page and so we can show statistics by provider. We never store passwords, tokens or query parameters that look like authentication data. See our privacy policy.
Why don’t you provide a public API?
To prevent abuse, every analysis is performed via the website. The internal scanner is bound to localhost and is not reachable from the public internet.