Paste a TinyURL, t.co, or other shortened URL below, then confirm the scan. See the observed redirect path and final destination when reachable, with warning signals and incomplete checks explained.
CheckLink provides risk signals and review context, not a guarantee. Verify sensitive links through official channels before acting.
The visible tinyurl.com address names the shortening service, not the final website. Copy the complete short URL and review where the public redirects lead. Compare the destination domain with the sender's claim before signing in or paying.
A TinyURL alias is not an encoding you can decode by reading its letters. The shortener stores a redirect to another URL. CheckLink requests that public redirect and shows the destination it can observe, without intentionally loading the final page in your browser.
Shorteners, campaign trackers, and affiliate links can add several redirects. Those hops can be legitimate. Inspect the observed chain and decide whether the final destination fits the message; a domain change alone is not proof of phishing.
A t.co link from X can hide the full destination until it redirects. The same workflow works for other public HTTP and HTTPS short URLs. The result depends on the redirects the server can observe, not on the shortener's brand.
Expired links, bot blocking, timeouts, redirect limits, and pages that require JavaScript or a login can prevent a complete preview. CheckLink does not run the destination's page scripts. An incomplete result cannot confirm the final destination or its legitimacy.
Bitly is also a shortener. The dedicated Bitly link checker linked below provides bit.ly-specific guidance; this page covers TinyURL, t.co, and shortened URLs more broadly. Both use CheckLink's existing scanner.
Next step: use the related tool that matches your situation, or request manual review when the link affects money, credentials, accounts, work, or customers.
Copy the complete TinyURL, paste it into CheckLink, and confirm the scan. Review the observed redirect path and final domain if the destination can be reached.
Yes. CheckLink requests the public URL on its server and shows the available redirect information. It does not open the destination in your browser; the remote service can still receive the check request.
The scanner accepts public bit.ly URLs too. Use the linked Bitly Link Checker for Bitly-specific guidance.
A link may expire, block automated requests, require JavaScript or a login, or exceed redirect and timeout limits. Read the incomplete checks instead of assuming the destination is safe.
No. It reveals an observed destination. The page may change or contain risks that URL and redirect checks cannot detect.