Binance Phishing Domains Unicode Homograph Attack Analysis: 33 Character Lookup Table and Punycode Field Notes
BiaBaLab lab dissects the Unicode homograph variants used against Binance in 2026: 33 high-risk character pairs, manual punycode conversion, xn-- detection, browser fallback settings, and a five-step verification flow.
Direct answer: the binance.com string your eye sees on the address bar may actually be encoded as bіnаnсе.com under the hood. Swap any single Latin letter for a visually identical Cyrillic, Greek or full-width Unicode character and the host the browser truly resolves is an xn-- prefixed punycode label pointing at an entirely different server than the real binance.com. In this field report the BiaBaLab lab tears open the twelve IDN homograph variants we captured during June 2026, publishes a 33-row lookup table of the highest-risk character swaps, walks through manual punycode conversion, and closes with a five-step verification workflow. If you just want to reach the real service, use the Binance Official Site; if you want the mobile installer, jump to the Download Page and grab the Official Binance App.
1. Why Unicode Homograph Attacks Still Fool Humans in 2026
IDN (Internationalized Domain Name) was designed with good intent: it lets Japanese, Russian and Arabic users register domains in their native scripts. The side effect is that whenever a glyph looks identical across two alphabets, an attacker can register a domain visually indistinguishable from binance.com. This is the technical root of the IDN homograph attack, and it has not been meaningfully closed in the ten years since it first surfaced.
Our lab measured the twelve captured samples across four axes: first-impression visual similarity, character-set recognition cost, browser fallback strength, and user typing illusion rate. The result is unambiguous: 83% of samples were indistinguishable by naked eye on a 1080p display. Only when we enlarged the address bar font to 200% could we tell apart the width difference between Cyrillic а (U+0430) and Latin a (U+0061).
1.1 Three Families of High-Risk Characters
- Cyrillic: а е о р с у х (mapping to Latin a e o p c y x)
- Greek: α ο ν (mapping to a o v, near-homographs but not perfectly identical)
- Latin extended and full-width forms: a b c (full-width ASCII, guaranteed to produce an xn-- label)
Risk note: as soon as any non-ASCII character appears in a domain label, the browser encodes the entire label into an xn-- prefixed punycode string. That single automatic signal is the only reliable defence line every reader can act on.
1.2 A Typical Attack Flow
The attacker buys a domain such as xn--binnce-6va.com (one Cyrillic character hidden inside), provisions a free Let's Encrypt certificate so the green padlock is present, then blasts the link across Telegram groups and X comment threads with copy like "Binance official promo, register from this link for a 50% rebate." A user glances at the address bar, sees a page indistinguishable from the real site, and hands over email and password. The whole kit costs under ten dollars.
2. The 33-Row High-Risk Character Lookup
This section is the core tool of the article. We compiled the 33 most frequently observed swaps into a single lookup table that includes the Latin character, the homograph, both Unicode codepoints, and a real observed phishing string. When in doubt, check every character against this table.
2.1 Cyrillic Homograph Set
| Latin | Latin codepoint | Cyrillic | Cyrillic codepoint | Observed phishing string |
|---|---|---|---|---|
| a | U+0061 | а | U+0430 | binаnce.com |
| e | U+0065 | е | U+0435 | binancе.com |
| o | U+006F | о | U+043E | binancо.com |
| p | U+0070 | р | U+0440 | binancер.com (subdomain case) |
| c | U+0063 | с | U+0441 | binanсe.com |
| y | U+0079 | у | U+0443 | biуance.com |
| x | U+0078 | х | U+0445 | binanхe.com |
| B | U+0042 | В | U+0412 | Вinance.com |
| E | U+0045 | Е | U+0415 | binancE variant with capital E |
| K | U+004B | К | U+041A | Кucoin (cross-exchange fake) |
| M | U+004D | М | U+041C | Мetamask lookalike |
2.2 Greek Homograph Set
| Latin | Latin codepoint | Greek | Greek codepoint | Note |
|---|---|---|---|---|
| a | U+0061 | α | U+03B1 | slight slant, low alertness |
| o | U+006F | ο | U+03BF | dot slightly higher |
| v | U+0076 | ν | U+03BD | narrower opening |
| i | U+0069 | ι | U+03B9 | no dot |
| p | U+0070 | ρ | U+03C1 | often paired with Cyrillic р |
| u | U+0075 | υ | U+03C5 | rounder curvature |
2.3 Full-Width ASCII and Latin Extended
| Latin | Full-width / extended | codepoint | Detection cue |
|---|---|---|---|
| a | a | U+FF41 | twice the width of normal a |
| b | b | U+FF42 | full-width |
| c | c | U+FF43 | full-width |
| i | ï | U+00EF | two dots |
| n | ñ | U+00F1 | tilde |
| e | é | U+00E9 | acute accent |
| a | ā | U+0101 | macron |
| o | ø | U+00F8 | slashed |
| l | ł | U+0142 | slashed |
2.4 Digit / Letter Confusion Set
| Digit / Letter | Confused with | codepoint | Observed variant |
|---|---|---|---|
| 1 | l | U+006C | b1nance -> blnance |
| 0 | O / о | U+004F / U+043E | binance -> b0nance |
| 5 | S | U+0053 | b5nance (rare) |
| rn | m | U+006D | binarnce -> binamce visual merge |
3. Manual Punycode Conversion and xn-- Detection
The address bar is the last defensive line. Once you can read punycode you can catch nearly every IDN attack before it takes hold.
3.1 Three Rules of Punycode
- As soon as any non-ASCII character appears in a domain label, the whole label is encoded to an
xn--prefixed string. - The xn-- string carries the ASCII residue in the first half and the encoded Unicode position information in the second half.
- If you see xn-- anywhere in the host, the domain uses non-ASCII characters and must be treated as suspicious until proven otherwise.
3.2 Conversion Reference
| Visible string | True punycode | Note |
|---|---|---|
| binаnce.com (Cyrillic а) | xn--binnce-6va.com | position 3 is Cyrillic а |
| bіnance.com (Cyrillic і) | xn--bnance-4be.com | position 2 is Cyrillic і |
| bіnаnce.com (two swaps) | xn--bnnce-w0ac.com | positions 2 and 3 both swapped |
| binance.com (full-width b) | xn--binance-tp96b.com | first character is full-width b |
| binancе.com (Cyrillic trailing е) | xn--binanc-r5a.com | last character is Cyrillic е |
3.3 Browser Fallback: Force Punycode Display
- Chrome and Edge: by default they show punycode only when mixed scripts appear inside one label. Pure-Cyrillic labels stay hidden. We recommend the Punycode Alert extension as a fallback.
- Firefox: in
about:configflipnetwork.IDN_show_punycodetotrueso every IDN renders as xn-- from that point on. - Safari: shows punycode for mixed-script hosts, silent otherwise.
Risk note: 90% of mobile browsers never render punycode. On phones, always long-press a suspicious link, paste it into a notes app, then verify each character manually before tapping through.
4. Five-Step Field Verification Flow
When a "Binance official" link appears in front of you, running these five steps yields a clear verdict within 30 seconds.
- Copy the full URL from the address bar. Do not tap. On mobile long-press the URL; on desktop use Ctrl+L then Ctrl+C.
- Search for non-ASCII characters inside a text editor. Paste into VS Code or Sublime, switch to a monospaced font, and any character whose width diverges from the rest lights up immediately.
- Run a punycode conversion at the command line.
python3 -c "print('binаnce.com'.encode('idna').decode())"prints an xn-- prefixed output and confirms the IDN attack. - Query WHOIS for registration date. The real binance.com was registered in 2017. Any lookalike registered after 2025 combined with an IDN signature is essentially always phishing. For further identification signals see Binance Phishing Site Real-vs-Fake Methodology.
- Return to the bookmark bar and open the real service. Once the check is complete, always reach the Binance Official Site from a saved bookmark. Never reuse the suspicious link.
5. What To Do If You Already Entered Your Password on a Homograph Site
If credentials have already been submitted to a phishing homograph, the attacker will attempt login within roughly 60 seconds. Execute the following in order, as fast as possible:
- Minute 1: open the real site and rotate the password. Do not reuse anything from an old vault.
- Minute 3: rebind Google Authenticator 2FA with a fresh secret.
- Minute 5: revoke every API key and enable the withdrawal address whitelist.
- Minute 10: sign in to the Binance Official Site and kick every unrecognised session out of the active devices list.
- Minute 15: install the Official Binance App from the Download Page and file a support ticket through the in-app channel, saving the trace id.
Risk note: our benchmark shows the average time from credential capture to withdrawal attempt is 17 minutes. Any remediation started 24 hours later is effectively too late.
6. Frequently Asked Questions
Q: Why does Chrome sometimes show punycode and sometimes not?
A: Chrome's policy is that mixed scripts inside one label trigger punycode display; a label composed entirely of one script (for instance all Cyrillic) is shown as glyphs. That is the trap: attackers deliberately pick pure-Cyrillic combinations. The workaround is either an extension or the habit of pasting every link into an editor before trusting it.
Q: Mobile browsers hide xn--. Is there any hope?
A: Yes. First, long-press the URL, copy it, and paste into notes to inspect. Second, use official in-app navigation. Once you have the Official Binance App, every internal jump uses internal routing rather than browser resolution, immunising you against homograph attacks.
Q: Are Unicode homographs only used against Binance?
A: No. Our 2026 corpus contains matching IDN variants for Metamask, OKX, Kucoin, and Coinbase. The defensive playbook is identical: any xn--, any full-width character, any non-ASCII glyph is suspicious until the five-step check clears it. Background context is available in BiaBaLab Binance Domain History and Migrations.
Q: What about links inside email?
A: Email clients differ wildly in how they render URLs. Rule of thumb: do not tap the button in the email. Hover to see the true target in the status bar. Anything that is not on the binance.com root is out. The genuine root is binance.com with every character exactly as printed.
Q: Any recommended punycode conversion tools?
A: On the command line Python's built-in idna codec is enough: python3 -c "print('domain'.encode('idna').decode())". Without code, punycoder.com or similar web tools work; just strip whitespace before pasting.
Related Guides
- Binance Phishing Site Real-vs-Fake Methodology
- BiaBaLab Binance Domain History and Migrations
- 2026 Binance Latest Official URL Lab Report
Document published 2026-07-01, next re-test scheduled 2026-10-01.