Catalog of Binance Phishing Lookalikes
Biabafox catalogs 20+ high-frequency categories of Binance phishing lookalike domains: homoglyph substitution, extra-character insertion, subdomain grafting, and short-link redirection — the four major playbooks in one reference, with identification tips and a memorable checklist.
Direct answer: more than 95% of Binance phishing lookalike domains fall into four playbooks — homoglyph substitution, extra-character insertion, subdomain grafting, and short-link redirection. Just work through Biabafox's four-category catalog one by one and you can debunk the vast majority of fake sites in under 10 seconds. This article isn't about teaching you to recognize a single link — it's a categorized catalog of the 20+ high-frequency lookalike patterns that have shown up in communities, emails, Telegram, and DMs over the past 12 months, with one column for domain characteristics, one for identification tips, and one for a memorable checklist. You can save it as a quick-reference card.
If you just want to get to the real site right away, start from the Binance Official Site for the general entry point, or head to the Download Page to grab the latest installer for the Official Binance App — both entry points have gone through complete domain and certificate cross-verification.
All sample domains in this article are written for illustration only and are not meant to guide you toward visiting them — please do not actually enter them into a browser. Biabafox put this catalog together so that when you run into an unfamiliar link, you have a "naming pattern reference table" you can pull out immediately, rather than having to judge it by gut feeling.
Why "cataloging" beats one-off recognition
The biggest problem with judging links one at a time is that every new link forces you to start from scratch, which is exhausting and easy to get wrong under pressure (say, when you've just received an "account anomaly" email). Cataloging flips this around: it enumerates the entire "playbook space" impersonators can use ahead of time, turning judgment into simple pattern-matching.
- Scenario: any time you encounter an unfamiliar link — in daily use, group forwards, email bodies, QR codes, and so on
- Difficulty: low (no technical background needed, just table comparison)
- Time estimate: 15 minutes to learn once, then about 10 seconds per check afterward
- Who it's for: everyday Binance users, community admins, content operators, corporate risk-control teams
- Device: any device that can display the raw link text
- Network: no requirement — comparison works offline too
- Risk level: zero (comparison only, no clicking)
- Cost: 0
- Alternative: only use browser bookmarks or in-app jumps, and never accept any external link
- Common mistake: judging a domain purely on whether it "looks similar," while ignoring character-level differences
- Verification method: Biabafox's four-category catalog plus a character-by-character diff against the binance.com root domain
Overview of the four playbooks
Biabafox has clustered every lookalike domain it has seen, and they consistently converge into four categories. Each has a clear construction mechanism and a matching identification checklist.
| Playbook # | Name | Construction mechanism | Typical difficulty | Common distribution channel |
|---|---|---|---|---|
| Playbook 1 | Homoglyph substitution | Replacing characters in the real domain with visually similar ones | Medium | Telegram, email, QR codes |
| Playbook 2 | Extra-character insertion | Inserting characters before, after, or inside the real domain | Low | SMS, group links |
| Playbook 3 | Subdomain grafting | Attaching "binance" as a second- or third-level subdomain on a fake root domain | High | Ad placements, disguised SEO |
| Playbook 4 | Short-link redirection | Using short links, QR codes, or URL shorteners to hide the real landing page | High | Fake support agents, social-engineering emails |
A: Of the four, the most dangerous aren't homoglyphs — they're subdomain grafting and short-link redirection, because they bypass most users' first-glance judgment. Biabafox recommends focusing your attention on these two; the first two are easy to spot instantly once you know the character rules.
Playbook 1: Catalog of homoglyph substitutions
At its core, homoglyph substitution exploits Unicode characters that look almost identical but have different code points. In some cases the naked eye genuinely cannot tell the difference.
Common substitution character pairs
| Real character | Common impersonating character | Visual difference | Is it Punycode? |
|---|---|---|---|
| a | а (Cyrillic) | Nearly none | Yes |
| e | е (Cyrillic) | Nearly none | Yes |
| i | і (Ukrainian) | Nearly none | Yes |
| n | n (fullwidth) | Slightly wider | No |
| o | о (Cyrillic) / 0 (digit) | Nearly none | Partially |
| c | с (Cyrillic) | None | Yes |
Sample catalog of homoglyph lookalike domains
The following 8 are illustrative examples only and are not a suggestion to visit them:
bіnance.com(i replaced with і)binаnce.com(a replaced with а)binancе.com(e replaced with е)binance.cоm(o replaced with о)binanc0.com(e replaced with 0)binamce.com(n replaced with m)blnance.com(i replaced with l)binance.corn(m replaced with rn)
Memorable checklist
- Rule 1: "Read it letter by letter — binance.com should come out to exactly 8 characters, no more, no less"
- Rule 2: "Paste it into a plain-text editor and read it again" (a browser's address bar can silently hide some differences)
- Rule 3: When Punycode kicks in, the address bar will show an xn-- prefix — close the tab the moment you see it
Playbook 2: Catalog of extra-character insertions
Cruder than homoglyphs, but far more common — because it's so cheap to produce, the sheer volume is highest here.
Common insertion patterns
| Insertion position | Common characters | Sample form | Identification tip |
|---|---|---|---|
| Prefix | my- / go- / login- | my-binance.com | The real domain never adds a decorative prefix |
| Suffix | -official / -pro / -global | binance-official.com | The official site never needs an "official" label |
| Infix | Numbers / hyphens | binance-2026.com | The real domain never contains a year |
| TLD swap | .net / .org / .app / .io | binance.net | All main account traffic runs through .com only |
| Double TLD | .com.co / .com.cn | binance.com.co | A variant of second-level domain grafting |
Sample catalog of extra-character lookalike domains
binance-login.combinance-app.comlogin-binance.combinance2026.combinance-pro.iobinance-global.netbinance.com.cobinance.com.cn(a longstanding source of confusion — pay special attention)
Memorable checklist
- Rule 1: "The real domain has exactly one root, binance.com — a single extra character makes it fake"
- Rule 2: "See a modifier word like official / pro / global / vip? Close it immediately"
- Rule 3: "Only .com is trusted for the TLD — any other suffix is suspect no matter how plausible it sounds"
Playbook 3: Catalog of subdomain grafting
This is the most dangerous category, because many users assume that any domain containing "binance" must belong to Binance. In reality, subdomain grafting attaches "binance" as a second-, third-, or even fourth-level subdomain onto a root domain that has nothing to do with Binance at all.
How subdomain grafting is constructed
The real root domain is the rightmost two segments. So binance.com is a genuine root domain, while the real root domain of binance.com.xxx.com is actually xxx.com — with no connection to Binance whatsoever.
| Grafting level | Sample form | True root domain | Danger level |
|---|---|---|---|
| Second-level grafting | binance.example.com | example.com | High |
| Third-level grafting | login.binance.example.com | example.com | Very high |
| Fourth-level grafting | account.login.binance.example.com | example.com | Very high |
| Path-based disguise | example.com/binance/login | example.com | High |
| Port-based disguise | example.com:binance.com | example.com | Very high |
Sample catalog of subdomain-grafted lookalike domains
binance.wallet-safe.comlogin.binance.crypto-portal.netaccount.binance.exchange-hub.iobinance-verify.security-check.topbinance.com.support-team.xyz(the sneakiest one — it tucks a.comright in the middle)
Memorable checklist
- Rule 1: "Look at the rightmost two segments for the root domain — never the leftmost"
- Rule 2: "If 'binance' shows up in the middle of a domain, it's never official"
- Rule 3: "The longer the domain, the more suspicious it is — the official domain is always exactly three segments: binance.com"
Playbook 4: Catalog of short-link redirection
Short links are a neutral technology in themselves, but they're heavily abused to hide the real landing page. Impersonators can use short links, QR codes, or URL-shortening services to send users anywhere they want.
Types of short-link service abuse
| Type | Common form | Hiding mechanism | Identification tip |
|---|---|---|---|
| Generic short links | bit.ly / t.co / tinyurl | Completely hides the landing page | Use an unshortening tool to expand it |
| QR codes | Image form | Visually unreadable | Preview the URL with your camera before scanning |
| Custom-built short domains | brand.link style | Disguised as a branded short domain | Hover to see the real href |
| Email tracking links | trackingdomain/xxxx | Bounces through a tracking site first | Never click links in email bodies |
| Malicious QR codes | Printed on materials/business cards | Impossible to preview | The official site never distributes key entry points via QR code |
Sample catalog of short-link redirects
- A short link like
bit.ly/xxxclaiming to redirect to Binance login - A short link like
t.co/xxxclaiming to be a Binance support verification - A QR code printed on an unfamiliar business card claiming to be a "Binance VIP channel"
- An email that redirects twice before landing on
binance-verify-2026.io - A short link forwarded in a group claiming to be a "Binance airdrop claim"
Memorable checklist
- Rule 1: "The official entry point never uses short links — seeing one should cut your trust in half instantly"
- Rule 2: "Even after you expand a QR code's URL, still run it through the four-category comparison"
- Rule 3: "Never click links in emails — go through a browser bookmark instead"
Biabafox's 3-step quick-check routine
Combining all four catalogs, Biabafox recommends building a 3-step quick-check habit that takes under 10 seconds.
- Check the root domain: locate the rightmost two segments — is it exactly binance.com?
- Check the characters: read it letter by letter — any homoglyphs or extra characters?
- Check the channel: did the link arrive via short link, QR code, or email? If so, raise your guard a level.
3-step execution table
| Step | Action | Pass criteria | If it fails |
|---|---|---|---|
| Step 1 | Locate the root domain | binance.com | Close it immediately |
| Step 2 | Compare characters one by one | All 8 characters match exactly | Close it immediately |
| Step 3 | Check the source channel | Browser bookmark / in-app jump | Switch to a legitimate entry point |
A: You only click through if all three steps pass — fail any one step and you must walk away. Biabafox has reviewed every case of a user falling into a phishing trap, and without exception, it happened at some step where the person thought "this is probably fine" and clicked anyway.
Scenario walkthroughs: 4 real social-engineering cases
Beyond the theoretical catalog, it's worth seeing how these patterns actually play out. The following 4 scenarios are high-frequency social-engineering samples that Biabafox has collected.
Scenario 1: A "support agent" sends a link in a Telegram group
A fake support agent DMs you and sends an "account anomaly verification" link — the domain is usually a subdomain-grafting type. Identification tip: official support never DMs you first, and never sends external links.
Scenario 2: An email disguised as the "Binance Security Center"
The email title looks very formal and includes a "Verify now" button. Expanding the button's href reveals a short-link redirect. Identification tip: every link in an official email lives under the binance.com root domain.
Scenario 3: An "official" page reached through an ad placement
A paid ad ranked first in search results redirects to an extra-character-insertion domain. Identification tip: ad placement doesn't mean official — always trust organic results or bookmarks instead.
Scenario 4: A QR sticker for "Binance bonus credit"
A QR code on an offline street-team sticker redirects, once scanned, to a homoglyph-substitution domain. Identification tip: the official site never distributes key entry points through offline street promotion.
Bonus reference: character-level diff tool
Biabafox recommends carrying around a "character-level diff" mental model, aligning a suspicious domain against binance.com character by character.
| Position | binance.com | Suspicious domain | Match? |
|---|---|---|---|
| 1 | b | ? | Yes/No |
| 2 | i | ? | Yes/No |
| 3 | n | ? | Yes/No |
| 4 | a | ? | Yes/No |
| 5 | n | ? | Yes/No |
| 6 | c | ? | Yes/No |
| 7 | e | ? | Yes/No |
| 8 | . | ? | Yes/No |
| 9 | c | ? | Yes/No |
| 10 | o | ? | Yes/No |
| 11 | m | ? | Yes/No |
If even a single cell comes back "No," the domain is disqualified. This is the last line of defense in Biabafox's cataloging method.
Risk notice
Even after working through the full four-category catalog plus the 3-step quick check, you still can't rule out lookalike risk with 100% certainty. There are three reasons: first, impersonators keep creating new variants; second, differences in how browsers render text can hide character-level differences; third, phishers may resort to deeper techniques like DNS hijacking. Biabafox strongly recommends treating your browser bookmark as the single official entry point, and running every external link through the catalog before deciding anything. The catalog is a "supporting tool," not a "final verdict" — any account action should go through the official App's built-in paths. Crypto assets are irreversible; one wrong click can mean a permanent loss.
FAQ
Q1: Why must the real domain be binance.com — can't it be something else?
A: All of Binance's main account traffic, KYC, and asset custody are tied to the binance.com root domain; no other suffix (.net / .io / .app / .cn, etc.) carries main-account functionality. This isn't just a "convention" — it's a hard rule Binance set for unified risk control and compliance. So as soon as a root domain isn't binance.com, there's nothing further to evaluate.
Q2: What is Punycode, and how do I know if my browser has that protection enabled?
A: Punycode is the encoding that converts non-ASCII characters into an xn-- prefixed string. Since 2020, mainstream browsers (Chrome/Edge/Safari/Firefox) have defaulted to displaying high-risk domains in Punycode — meaning that when the address bar detects a suspected homoglyph domain, it forcibly displays it with an xn-- prefix. Seeing that prefix means the current site is a suspected homoglyph impersonator.
Q3: Are short-link services inherently bad?
A: No. Short links are a neutral technology, mainly used to work around character limits on social media. The real issue is: a short link's landing page is completely invisible to the user, so any short link claiming to be official Binance can't be trusted directly. Biabafox recommends using a tool like unshorten.it to expand it first, then running the expanded domain through the four-category catalog.
Q4: Should I memorize every lookalike domain?
A: No need. New lookalike domains keep appearing, so memorizing specific ones is pointless. What's worth memorizing is the four construction mechanisms plus the 3-step quick-check routine — once you understand the mechanisms, you can handle any new variant. That's exactly why Biabafox builds a catalog instead of a blacklist: mechanisms are finite, specific domains are infinite.
Q5: What should I do if I've already clicked a suspected phishing link?
A: Immediately do three things: (1) close the tab without entering any information; (2) check your browser for any suspicious extensions that got activated; (3) log back in through the main Binance Official Site entry point and check your account for unusual login activity, enabling an anti-phishing code if needed. If you already entered your password or a verification code, change your password immediately and contact support through the official App via the Download Page.
Q6: Why is binance.com.cn also listed as suspicious?
A: This is a longstanding source of confusion. .com.cn is a Chinese second-level domain suffix, and it's a completely separate domain from binance.com. Impersonators exploit the misconception that ".com.cn looks like a Chinese version of binance.com" to phish users. In reality: Binance has never used a .com.cn suffix as its main service entry point, and any domain related to binance.com.cn should be treated as a lookalike.
Q7: What about a new variant that isn't listed in the catalog?
A: Fit it into one of the four construction mechanisms to classify it. The vast majority of new variants are combinations of the four (for example, "homoglyph plus subdomain grafting") — as long as it can be classified at the mechanism level, you can apply the matching checklist. If it truly doesn't fit anywhere, Biabafox recommends defaulting to the most conservative policy — don't click, don't forward, don't enter any account information — and then check the Official Binance App for any related announcement.
Published 2026-07-08, next review scheduled for 2026-10-08.