How to Spot a Phishing Link

By cryptoke, developer and editor at SafeLinkWrite. Reviewed for technical accuracy.

A phishing link is a URL designed to look like one destination but deliver the visitor to another. The purpose varies — credential capture, malware delivery, payment theft — but the mechanics are consistent. If you know what to look for, most phishing links become obvious once you slow down. The problem is not that readers are careless; it is that phishing URLs are engineered so the correct part of the URL looks wrong and the wrong part looks correct.

This guide covers how to read a URL correctly, the substitution patterns attackers rely on, the role of HTTPS, redirect parameters, delivery context, and a five-step check you can run in ten seconds.

What Makes a Link "Phishing"

A phishing link has three design goals:

  1. Look plausible at a glance. A quick skim should not raise suspicion.
  2. Break under careful reading. The URL only fails when the reader stops and inspects the domain — which most readers do not do.
  3. Survive casual warnings. The padlock icon, the HTTPS prefix, and the presence of a brand name in the URL all reassure the reader without any real verification.

Understanding those three goals is the operating principle. Every technique below is a variation on one of them.

Technical Breakdown: Common Phishing URL Patterns

Pattern Example What is actually happening
Brand-subdomain trick paypal.verify-user.com The domain is verify-user.com. "paypal" is only a subdomain label chosen to trigger recognition.
Brand-in-path trick attacker.com/bankofamerica/login The domain is attacker.com. Everything after the first slash is path data, meaningless to ownership.
Typosquatting g00gle.com, paypaI.com Character substitution — zero for O, capital I for lowercase l, rn for m.
Homograph attack аpple.com (Cyrillic 'а') Non-Latin characters replace Latin ones. Looks identical on screen.
Hyphen stuffing secure-login-paypal.com The lookalike string is the whole domain, not a subdomain. The real domain is that whole thing.
Open redirect abuse trusted.com/redirect?url=attacker.com The visible URL is a trusted domain, but the query parameter forwards the visitor elsewhere.

Six patterns cover the majority of what arrives in an inbox. Each fails the moment the reader applies the right check — but the right check is different for each pattern.

Reading the URL Correctly: Domain vs Path vs Query

The domain is the part between the scheme and the first single slash. It is the only segment of a URL that reliably indicates who owns the page. Everything after the first slash can be crafted to look like anything.

Segment Example Who controls it
Scheme https:// Protocol — says nothing about ownership.
Subdomain login. Chosen by whoever owns the domain. Can be anything.
Domain bankofamerica.com The owner. This is the only segment that matters for trust.
Path /personal/accounts The domain owner. Can be crafted to look like any brand.
Query string ?session=abc The domain owner. Frequently used for redirect abuse.

Read a URL right to left when in doubt. The first thing you should identify is the domain — then decide whether the rest is even worth reading.

Example: Ten-Second Inspection of a Realistic Phishing Link

A message arrives claiming to be from a bank. The link says:

https://bofa.secure-login-verify.com/session?next=bofa.com%2Faccount

Reading it in order:

  1. Scheme: https://. Encrypted, but encryption does not mean legitimate.
  2. Subdomain: bofa. Chosen to trigger recognition, not owned by Bank of America.
  3. Domain: secure-login-verify.com. This is the actual owner. It is not Bank of America. Stop here.
  4. Path: /session. Irrelevant now — the domain already disqualified the link.
  5. Query: next=bofa.com%2Faccount. A redirect parameter. Even if the reader landed on the site, this would forward them elsewhere.

The correct action after step 3 is to stop. Do not visit the page, even to "see what it looks like." Reach the bank through the app or by typing the domain manually.

Myths vs Facts

Myth Fact
"The padlock means the site is safe." The padlock means the connection is encrypted. Phishing sites obtain HTTPS certificates as easily as legitimate ones.
"If the brand name is in the URL, it's the brand's site." The brand name can appear as a subdomain or a path. Only the domain segment indicates ownership.
"Phishing links always look obviously fake." Modern phishing uses clean design, valid certificates, and domains that pass a casual scan. The failure only shows under careful reading.
"Clicking is what causes the damage." Most phishing pages only cause damage when credentials are entered. The click alone is usually harmless — the mistake is what happens next.
"Antivirus blocks phishing links automatically." Antivirus catches known-bad URLs. Newly registered phishing domains often pass through before they are blacklisted.
"Redirect links from trusted sites are safe." Open redirect parameters on trusted domains are a standard attack vector. The visible domain is legitimate; the destination is not.

Five-Step Check Before Any Suspicious Link

  1. Read the domain, not the path. Identify the segment before the first single slash. Ignore everything after it until the domain passes.
  2. Hover before clicking. In email clients and browsers, hovering shows the real destination. Compare it to the visible text — a mismatch is a phishing signal.
  3. Scan for character substitution. Look for zeros in place of O, capital I in place of lowercase l, and unexpected non-ASCII characters.
  4. Decode redirect parameters. If the URL contains url=, link=, goto=, or next=, decode the value and check the destination.
  5. Reach the destination by a channel you control. Type the domain manually, open the official app, or use a bookmark. Never enter credentials on a page you reached through a link you did not expect.

Consider the Delivery Context

Phishing relies on plausible context. The suspicious link usually arrives somewhere unexpected: an email pretending to be from a supplier, a chat message from an unrecognized account, a text message with a partial claim that forces a click. If the link arrives through a channel that would not normally carry that kind of message, the link deserves extra scrutiny even when it looks fine. The channel is part of the attack.

Conclusion

Phishing links are not sophisticated. They are engineered so the domain does not match the visible brand, the path looks convincing, and the reader is in a hurry. That is the entire design. The countermeasure is equally simple: read right to left, stop at the domain, and refuse to click anything that arrived through a channel you did not expect. Ten seconds of inspection beats an hour of account recovery. The next time a link shows up somewhere unexpected, run the check — the domain will tell you what the rest of the URL is trying to hide.