How to Check a Short Link Before You Click It
Created on 16 November, 2026 • Link safety • 4 views • 4 minutes read
A short link hides its destination by design. Here are the practical ways to see where one goes, what the signals mean, and the look-alike tricks that defeat a quick glance.
Short links are useful precisely because they hide a long, ugly URL. That same property makes them the standard delivery vehicle for phishing, because the recipient cannot see the destination before committing.
You can almost always see it anyway. Here is how, in rough order of effort.
1. Expand it without visiting it
A redirect checker fetches the link and reports the chain of redirects and the final destination without rendering the page. This is the single most useful step: paste the short link into a redirect checker and read where it lands.
Read the whole chain, not just the end. A link that passes through four unrelated domains is a signal in itself, and one of those hops may be the actual attack while the final destination is innocuous.
Note the limits honestly. Some destinations behave differently for a checker than for a real browser - they look at the user agent, the IP address, the referrer or the country and serve a harmless page to anything that looks automated. This technique, often called cloaking, is common enough that a clean result is reassurance rather than proof.
Some shortening services also support a preview mode, typically by appending a character such as + to the short URL. It is worth knowing but it is service-specific and not something to rely on.
2. Check the destination's reputation
Once you have the final URL, check it against Google Safe Browsing, which maintains lists of pages known to host malware, unwanted software or social engineering. A safe URL checker queries exactly this.
Again, the limits matter. Safe Browsing is a blocklist, so it is reliable when it says yes and uninformative when it says no - phishing sites are frequently taken down within hours and are often newest exactly when they are most dangerous. "Not listed" means "not yet listed".
3. Look at the domain, carefully
Most of the signal is in the domain, and most of the deception is too.
Read right to left from the last dot. The registrable domain is the part immediately before the public suffix. In yourbank.com.secure-login.example, the actual domain is secure-login.example and yourbank.com is just a subdomain label chosen to be read first. This trick works on almost everyone in a hurry.
Watch for look-alike characters. Internationalised domain names allow non-ASCII characters, and many of them are visually identical to Latin letters - Cyrillic а, е, о and р render exactly like their Latin counterparts in most fonts. The resulting homograph domain is a different domain entirely. Browsers defend against the obvious cases by displaying the Punycode form (xn--...) when a domain mixes scripts suspiciously, but the defence is not complete. If a domain looks right but something feels off, run it through an IDN/Punycode converter and see what it really is.
Check the age. A WHOIS lookup shows the registration date. A domain registered three days ago that claims to be a long-established bank is not one. Registrant details are usually redacted for privacy, so the date and the registrar are the useful fields.
Note the credential-free path. Legitimate organisations rarely ask you to log in via a link you did not request. The strongest defence is not inspecting the link at all - it is opening the site yourself, by typing the address or using a bookmark.
4. Know what HTTPS does and does not tell you
A padlock means the connection is encrypted and the certificate matches the domain. It says nothing about whether the domain belongs to who you think. Certificates are free and issued automatically within minutes, and the overwhelming majority of phishing sites now use HTTPS.
What a certificate can tell you is the exact domain it was issued for and when it was issued - an SSL lookup shows both. A certificate issued yesterday for a domain claiming decades of history is a contradiction worth noticing.
5. Context beats inspection
Technical checks are the second line. The first is the situation.
- Was it expected? An unexpected link is the single strongest signal, regardless of who appears to have sent it.
- Does it create urgency? Account suspension, a delivery problem, an unpaid invoice, a security alert demanding action within hours. Urgency exists to stop you doing exactly what you are doing now.
- Does it ask for credentials, payment details or a code? Especially a one-time code. No legitimate organisation needs you to read one back.
- Does the channel match? A bank that normally writes by post, contacting you by SMS with a link, is anomalous.
- Could the sender be impersonated? Display names are trivially forged, and compromised accounts send links to their real contacts. "It came from a colleague" is weak evidence.
If you are not sure
Do not click to find out. Reach the organisation independently - type the domain you already know, open the app, call the number on your card - and ask. The cost of a two-minute detour is zero; the cost of being wrong once is not.
If you clicked and entered something: change that password immediately, change it anywhere you reused it, revoke active sessions, and tell whoever handles security where you work. Speed matters far more than embarrassment.
And if you run short links yourself, you are on the other side of this problem too - the measures that keep your links trustworthy are covered in shortened links and phishing.
Popular posts
-
-
Bio link pagesBio link pages • 5,372 views
-
Short URL best way to track your linksShort URL • 5,253 views
-
-