Why does the browser ignore what comes before the `@` in a URL?
Because RFC 3986 reserves that segment for HTTP authentication credentials embedded in the URL (`user:password@host`), an old feature rarely used legitimately today; the browser follows the spec exactly and treats everything before the `@` as a login, not part of the domain, which opens the door for the trick.
What is Punycode and why do phishing domains use it?
Punycode (RFC 3492) is the scheme that encodes non-ASCII letters in a domain into the `xn--` format DNS understands; it exists to allow legitimate internationalized domains, but it also allows registering a domain with letters from another alphabet that look visually identical to Latin ones, the basis of the homograph attack.
Does a link flagged as safe by the check guarantee the site is trustworthy?
No, the analysis is passive: it examines only the URL structure (host, encoding, confusable characters, brand pattern) without fetching the content or querying a third party, so a newly registered domain, technically clean but malicious, can pass through with no signal at all.
Why does a link shortener like bit.ly count as a risk signal?
Because the shortener hides the real destination domain behind a generic host, removing precisely the information that would let someone judge the link before clicking; that does not make the link malicious by itself, but it raises the risk by hiding exactly the data the other signals analyze.