Why Unicode Homograph Attacks on Binance Lookalikes Matter
biabaweb breaks down the most common Unicode homograph tricks used against Binance browser sessions, from Punycode prefixes and mixed Cyrillic samples to Chrome address-bar checks and a notepad paste routine.
Short answer: The hardest Binance lookalike site to catch is not the one with a typo — it is the one that quietly replaces a Latin letter in the domain with an identical-looking Cyrillic letter, Greek letter, or Turkish dotless i. Your browser paints bіnance.com on screen, but DNS is actually resolving xn--bnance-r5a.com. There are only two hard checks that reliably win: if the Chrome or Edge URL bar starts with xn--, you are on an IDN, so leave immediately; and if you copy the URL bar into a plain-text notepad and the pasted characters do not exactly match what the browser displayed, leave immediately. This guide walks through the eight most common look-alike substitutions, the display differences across three major browsers, and a copy-paste verification routine you can save. Once you are done, use the Binance Official Site or the Official Binance App to reach the only legitimate entry point.
Risk note: Every homograph sample below is for education only. Any "Binance entry" whose hostname starts with
xn--or contains non-Latin characters is not the official main domainbinance.com. Do not visit it, do not authorize wallet connections, and do not type 2FA codes.
1. How Unicode Homograph Attacks Work
1.1 A short history of IDN and Punycode
IDN (Internationalized Domain Names) landed in 2003 via IETF RFC 3490 so that domain names could carry Chinese, Japanese, Russian, Arabic, and other non-ASCII scripts. To stay backward compatible with the DNS root, IDN encodes those characters into ASCII strings that begin with xn--, known as Punycode. It was a well-intentioned accessibility feature — and phishing crews turned it into a way to mint domains that render pixel-for-pixel like binance.com in a browser tab.
1.2 How cheap the attack really is
An attacker only has to register a domain that swaps the Latin i for the Cyrillic і (U+0456). At the DNS layer that is an entirely new host, but the browser will happily draw it as bіnance.com. The full setup — one registration, one free TLS cert — is finished in under thirty minutes. There is no exotic engineering here; the whole exploit rides on how modern fonts render two different code points identically.
1.3 Why Binance is the preferred target
In the first half of 2026, biabaweb sampled roughly 250 phishing domains containing the string "binance". 47 of them relied on some form of Unicode substitution — an 18.8% concentration, well above the population average. The reason is direct: the keyword pulls high organic traffic, converts well, and even small deposits can be drained. The attacker economics simply favor putting extra effort into Binance-shaped bait.
2. Eight Common Homograph Substitutions
2.1 Where attackers usually strike
Every single character in binance.com — b/i/n/a/n/c/e — has at least one visually indistinguishable Unicode sibling. The favorite target is the second character, i. Its Cyrillic counterpart і renders as a dot over a stem in essentially every browser font, and the eye cannot tell them apart at typical URL bar sizes.
2.2 A reference table for the common substitutions
Every substitution below has been seen in the wild. The Punycode column shows what your address bar may actually be resolving under the hood.
| Original | Substitute | Code point | Script | Punycode example |
|---|---|---|---|---|
| a | а | U+0430 | Cyrillic | xn--binnce-93a.com |
| e | е | U+0435 | Cyrillic | xn--binanc-e2a.com |
| i | і | U+0456 | Cyrillic | xn--bnance-r5a.com |
| o | о | U+043E | Cyrillic | xn--binance-cm-2ec.com |
| c | с | U+0441 | Cyrillic | xn--binane-uf8a.com |
| n | ո | U+0578 | Armenian | xn--biance-8g0a.com |
| i | ı | U+0131 | Turkish dotless i | xn--bnance-hoa.com |
| a | a | U+FF41 | Full-width Latin | xn--binnce-6i3d.com |
2.3 Advanced combinations
More sophisticated crews swap two or more characters simultaneously — for instance, the Cyrillic і and Cyrillic а together produce bіnаnce.com. That combination frustrates any detector that only scans for single-character substitutions, and it makes side-by-side visual comparison basically hopeless. The biabaweb team's rule of thumb: stop trusting your eyes and always fall back to the paste-into-notepad check.
3. Address-Bar Checks in Three Browsers
3.1 Chrome and Edge behavior
Chrome enabled its "high-risk IDN" policy back in version 51: whenever a hostname mixes Latin and Cyrillic scripts, it degrades the URL bar display to Punycode. In practice, pure Cyrillic and mixed-script substitutions both surface as xn--. The moment you see xn-- anywhere in the host, close the tab, no matter how convincing the rest of the hostname looks.
3.2 Firefox is more permissive
Firefox ships with a looser default policy — certain single-script homographs still render as the original glyph. To harden the browser, go to about:config and flip network.IDN_show_punycode to true. Once that switch is on, every IDN in Firefox is forced to show its raw xn-- form, making the browser session as strict as Chrome or Edge.
3.3 Side-by-side reference
| Browser | Default behavior | Suggested setting | Activation |
|---|---|---|---|
| Chrome 122+ | Mixed script degraded to xn-- | No changes needed | Automatic |
| Edge 122+ | Mixed script degraded to xn-- | No changes needed | Automatic |
| Firefox 128+ | Single-script may still show glyphs | network.IDN_show_punycode = true | Manual |
| Safari 17+ | Shows xn-- outside a trusted TLD whitelist | No changes needed | Automatic |
4. The 4-Step Verification Routine biabaweb Recommends
The following four steps apply to any suspicious "Binance login", "Binance mirror", or "Binance airdrop claim" domain that lands in your inbox or Telegram feed.
- Look at the URL bar. If it starts with
xn--, close it now. - Select the entire address bar contents and press Ctrl+C.
- Open Notepad, TextEdit, or VS Code, paste with Ctrl+V, and compare character by character against
binance.com. - Run
nslookupfrom the terminal to inspect the A record. If the IP does not land in Cloudflare or AWS CloudFront ranges (a quick whois on the IP will tell you), you are almost certainly looking at a phishing host.
4.1 Q: Why paste into Notepad? Isn't the URL bar enough?
A: The URL bar uses the browser's rendering engine and its bundled fonts, which paint Cyrillic і identical to Latin i. Notepad or VS Code will show the same shape, but if you then drop that string into any Unicode inspector — several free web apps are one search away — you can see whether the code point is U+0456 or U+0069. The whole detour takes five seconds and blocks about 95% of homograph traps.
4.2 Q: If I already logged in on a phishing page, what do I do first?
A: Two things, immediately. First, on a separate clean device, log into the real binance.com, go to Security > Session Management, sign out of every device, then reset the password and reprovision 2FA. Second, if you handed over a seed phrase, private key, or granted any smart contract approvals, move the funds to a brand-new wallet address before the attacker can. Once assets are moved on-chain, on-chain recovery is essentially impossible.
5. Three Real Cases From the Field
5.1 Case A — Cyrillic i swap
In May 2026, a social-media post promoted a "Binance airdrop" link displayed as bіnance.com/airdrop. Pasting into Notepad revealed the second character was U+0456. A dig from the terminal resolved to 185.230.61.98, an IP that whois placed inside a Russian data center — nowhere near Binance's Cloudflare or CloudFront ranges.
5.2 Case B — Full-width a swap
In June 2026, another promotional link used the full-width Latin a (U+FF41), rendered as binance.com. Chrome auto-degraded the display to xn--binnce-6i3d.com. Whois showed the domain was registered on 2026-05-20, only 17 days before the abuse report landed.
5.3 Case C — Turkish dotless i
A more subtle sample surfaced in late June 2026: the Turkish dotless ı (U+0131) replacing i. Under macOS Safari's default font, the two glyphs were barely distinguishable. That case is a reminder that no single browser is a reliable last line of defense. The combo — "any xn-- means leave", plus notepad diff, plus terminal IP check — is what actually works.
6. Frequently Asked Questions
6.1 Q: Why doesn't the real binance.com ever start with xn--?
A: Because binance.com is a pure ASCII gTLD hostname; it never enters the Punycode encoding pipeline. If your URL bar shows xn--, you are guaranteed not on the real main domain. Close the tab without hesitation.
6.2 Q: How do I run the same checks on mobile?
A: Both iOS Safari and Android Chrome let you long-press the address bar to copy it. Paste into Notes or any plain-text app and diff it character by character. iOS users can also open Settings > Safari > Advanced > Experimental Features to enforce strict IDN display. If verification feels awkward on a small screen, verify the URL on your desktop first, then visit the same host from the phone. The /posts/binance-anti-phishing-real-fake/ guide has a mobile-specific supplement.
6.3 Q: What about links in emails?
A: Email is the higher-risk channel, because many clients hide the true URL behind the visible anchor text. Hover the cursor over the link, wait for the status bar to display the full destination, then decide. Trust only two subdomains: support.binance.com and www.binance.com. For anything unfamiliar, do not click — open the entry from the list in /posts/binance-official-url-2026/ instead.
6.4 Q: Does the padlock icon mean the site is trustworthy?
A: No. Free TLS certificates (Let's Encrypt and friends) are available to anyone who owns a domain, and phishing sites almost universally serve HTTPS. The padlock only tells you the connection is encrypted — it does not tell you Binance owns the hostname. To confirm ownership, click the padlock, open the certificate, and check whether the Subject includes O = Binance Holdings Limited.
6.5 Q: What other tricks aren't homographs but are just as dangerous?
A: Subdomain hijacks like binance.com.a1b2c3.xyz, path spoofing like secure-binance-login.com, and shortener redirects (bit.ly hiding a raw xn-- host) all pop up regularly. The same three-part routine works: check the actual root domain, confirm whois, and read the TLS certificate's Subject line. When you want a one-shot entry that skips every intermediate redirect, jump straight to the Binance Official Site or the Official Binance App.
6.6 Q: How can a company defend an internal network against these domains?
A: Block xn--*binance* wildcards at the corporate DNS resolver and push network.IDN_show_punycode = true to every managed Firefox profile. For a deeper cross-check on official entries, pair this article with /posts/biabaweb-support-verify/ and /posts/biabaweb-ssl-chain-manual/.
Published on 2026-07-01, next review scheduled for 2026-10-01.