Binance Phishing Domain Variants Explained: Punycode Homoglyphs, DNS and Certificate Verification

Binance phishing domains fall into four categories: Punycode homoglyphs, common typo squats, SSL certificate swaps, and DNS shadow resolution. This article gives the identification flow, browser URL display comparisons, and whois verification commands.

Published on 2026-07-03 · About 25 min · Anti-Phishing

Direct answer: Binance phishing domain variants split into four categories: Unicode homoglyphs (Punycode xn-- prefix), typo squats (binamce / bainance / bīnance), TLD swaps (.co / .app / .net), and subdomain disguise (binance.xxx.com). The three-piece kit for identification is: the raw text in the browser URL bar, the SSL certificate issuer, and whois/DNS ownership. Any anomaly in any one of these means stop immediately. In publicly available samples from the first half of 2026, Unicode homoglyph variants accounted for about 34% of phishing domains, and this is the hardest class to distinguish by eye.

BianIO writes for technical users who want to master entry-point verification end to end. This article dismantles the four categories one by one: first Unicode homoglyphs and Punycode translation rules; then eight typical typo-squat patterns; finally SSL certificate and whois verification commands and browser URL display behaviors. Never forget the safest path is to reference the Binance Official URL entry page first, or grab the verified Official Binance App directly from the Download Page. For web operations, enter directly through the Binance Official Site.

Punycode Homoglyph Principles

Unicode contains many characters that look nearly identical to Latin letters but have different code points. The most classic is Cyrillic а (U+0430) versus Latin a (U+0061), indistinguishable in standard sans-serif fonts. Attackers use these characters to build domains that look like binance.com visually but are actually bin​а​nce.com (where а is Cyrillic).

To defeat this visual deception, browsers render mixed-script domains as Punycode: an xn--binnce-4xa.com-style form beginning with xn--. Any time the browser address bar shows an xn--prefixed domain while you thought you were visiting an English-language site, be on high alert.

Known Homoglyph Character Reference

Latin Character Common Homoglyphs Unicode Code Point
a а (Cyrillic a) / ɑ (Latin alpha) U+0430 / U+0251
e е (Cyrillic e) U+0435
o о (Cyrillic o) / ο (Greek omicron) U+043E / U+03BF
c с (Cyrillic s, looks like c) U+0441
p р (Cyrillic er) U+0440
i і (Ukrainian i) / ı (Turkish dotless i) U+0456 / U+0131
n ո (Armenian vo) U+0578
b Ь (Cyrillic soft sign) U+042C

A: Any single-character substitution produces a new candidate domain. Exhaustive substitutions on binance.com therefore yield thousands of visually identical but Punycode-distinct variants.

How Browsers Render Them

Modern browser policy: if any label in a domain mixes Latin characters with characters from another script, Punycode is forced on display. So bin​а​nce.com (containing one Cyrillic character) renders as xn--binnce-4xa.com in Chrome / Edge / Safari / Firefox. This is the most important fallback line of defense.

Warning: If a domain is composed entirely of Cyrillic characters (every letter swapped for its equivalent), older browser versions may not render Punycode. Enable the "always show Punycode" developer option as a hedge.

Eight Typical Typo-Squat Patterns

Typo squats do not need Unicode; they simply shift, add, or replace letters. These are the eight most frequent forms in publicly available 2026 data:

Pattern Example Technique Year First Publicly Reported
Letter transposition binamce / bainance Swap adjacent letters 2018
Letter substitution 6inance / binancé Digit substitution / diacritic 2019
Letter insertion binancee / bbinance Add a letter 2019
Letter deletion binace / binanc Drop a letter 2020
Casing confusion Binance-com (fake hyphen) Add a hyphen 2020
TLD swap binance.co / .app / .net Change the TLD 2021
Subdomain disguise binance.security-check.com Real primary domain belongs to attacker 2022
Diacritic homoglyph bīnance / bînance Add a diacritic 2023

A: Attackers' favorite combo is "subdomain disguise + TLD swap": for example binance-official.support. The visually dominant field is binance-official, but the primary domain is actually support. The only reliable judgment comes from the final segment of the primary domain.

TLD-Swap Detection Tips

Popular phishing TLDs today include .co, .app, .net, .io, .support, .help, .online, .top. Binance has never deployed a main site on these TLDs. The official main entry is binance.com; regional compliant subsidiaries use per-country TLDs (such as binance.us, binance.co.jp). Any non-binance.com domain without an explicit regional compliance statement should be treated as suspicious.

SSL Certificate Verification

SSL certificates are the second line of defense against phishing. Binance's main-site certificate is issued by top-tier CAs like DigiCert or Sectigo, and the SAN entries are limited to binance.com and official subdomains.

Manual Verification Command

openssl s_client -connect binance.com:443 -servername binance.com </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject -dates -ext subjectAltName

The output should contain:

  1. issuer: CN=DigiCert or Sectigo-related issuer;
  2. subject: CN=binance.com;
  3. subjectAltName: a series of binance.com and its subdomains;
  4. notBefore / notAfter: issue date within the last 1-2 years;
  5. Complete certificate chain traceable to a Root CA.

A: Any so-called "Binance" site with a Let's Encrypt-issued certificate should be treated as suspicious. Let's Encrypt itself is compliant, but Binance's main site does not use it as the primary certificate because 90-day short-lived certificates do not suit a financial site. Some test subdomains might, but they will not appear on user-facing main entries.

Browser UI Observation

In Chrome, click the lock icon, then "The connection is secure," then "Certificate is valid," and after loading the certificate chain, look for:

  • Common Name must be binance.com or a clear subdomain;
  • The Organization field should show Binance Holdings Limited or the official entity name;
  • Auto-renewed within 30 days of expiry.

DNS and whois Verification

The core of DNS verification is domain ownership and resolution. The registrar on the whois record of the Binance main domain is MarkMonitor (a domain-protection provider commonly used by top companies); any other registrar is a red flag.

Command-Line Demonstration

whois binance.com | grep -Ei "registrar|created|expiry|name server"

Key fields:

  1. Registrar: MarkMonitor, Inc.;
  2. Creation Date: around 2017;
  3. Registry Expiry Date: at least three years out (large companies always renew long term);
  4. Name Server: Cloudflare or the official authoritative DNS;
  5. Registrar Abuse Contact Email: abuse@markmonitor.com.

DNS Resolution Comparison

dig binance.com +short
dig binance.com NS +short
dig binance.com CAA +short

The CAA record (Certificate Authority Authorization) declares which CAs may issue certificates for this domain. The Binance main domain's CAA allowlist only contains DigiCert and Sectigo; certificates issued by other CAs will be rejected by browsers.

Risk warning: Warning: The CAA record is a key line of defense against man-in-the-middle attacks. If you see a phishing site with a Let's Encrypt certificate that still validates, that site's domain is definitely not the real binance.com (whose CAA policy would reject that issuance outright).

Browser URL Display Behavior Reference

Different browsers handle suspicious domains slightly differently:

Browser Homoglyph Display Policy Mixed-Content Blocking Known Phishing List
Chrome Forces Punycode Blocked by default Google Safe Browsing
Edge Forces Punycode Blocked by default Microsoft SmartScreen
Safari Forces Punycode Blocked by default Apple malicious-site database
Firefox Forces Punycode Blocked by default Mozilla + Google
Brave Forces Punycode Blocked by default Brave + Google

A: Mainstream browsers all enforce Punycode display and block against known phishing lists, but both have latency: registering a phishing site into the database usually takes hours to days. Do not rely on browser warnings alone; proactive domain verification is still necessary.

Mobile Browser Differences

Mobile address bars are narrow, and many by default show only the primary domain, hiding the full URL. This makes mobile identification of phishing sites harder. Before accessing Binance-related services on mobile, confirm the entry once on your PC.

Frequently Asked Questions

Q1: Why does the "official site" I searched for turn out not to be binance.com?

A: Search engine home pages have ad slots, and some advertisers can briefly float phishing links. Always prefer bookmarks or a direct URL type-in; never rely on the top result of a search engine.

Q2: If the URL contains "binance," is it official?

A: No. Only when the last segment of the primary domain (excluding the TLD) is "binance" and the TLD is .com (or a clear regional variant) is it official. The word "binance" can appear anywhere in a subdomain that an attacker fully controls.

Q3: What should I do about Punycode domains?

A: If you see any xn-- prefixed domain while thinking you are visiting an English-language site, close it immediately. Only manual URL entry or bookmark access is safe. You can also reference the Binance Official URL page to confirm.

Q4: Does a valid SSL certificate mean the site is safe?

A: No. A certificate only proves the certificate holder owns the domain. Once an attacker owns a phishing domain, they can also get a legitimate certificate. A valid certificate is necessary but not sufficient.

Q5: Can mobile apps run into this class of phishing?

A: Yes. Fake apps are typically distributed via phishing sites. Prefer grabbing the verified Official Binance App from the Download Page; do not download from group-chat links.

Q6: Can I look up CAA records myself?

A: Yes. dig binance.com CAA +short is one line. If the output is empty or abnormal, that domain is not the official Binance.

Q7: How long do phishing domains typically live?

A: Most are taken down within a few days to a few weeks. Attackers continuously register new variants, so staying alert matters more than memorizing any specific phishing domain.

Six-Step Systemic Anti-Phishing Workflow

  1. Hard-code the entry: bookmark binance.com in your browser and always enter via the bookmark;
  2. Disable address-bar autocomplete: to avoid accidentally hitting a phishing domain from history;
  3. Enable DNS-over-HTTPS: to prevent ISP-level DNS hijacking;
  4. Inspect the address bar before every login: at minimum, confirm the last segment of the primary domain is binance.com;
  5. Enable 2FA: even after landing on a phishing site by mistake, 2FA is one more line of defense;
  6. Follow official security advisories: Binance runs a dedicated channel publishing a domain blacklist.

Warning: DNS-over-HTTPS or DNS-over-TLS is the critical tool against ISP DNS hijack. You can enable it directly in Chrome / Edge / Firefox without any third-party software.

Closing Note and Further Reading

Phishing domain identification is fundamentally about "not letting visuals drive the call." Any domain that looks correct but fails technical verification is phishing, no leeway granted. To learn more about identifying customer service, see Binance Customer Service Authenticity; for direct app installation, see the Download Page; for web registration, enter through the Binance Official Site, or again the Binance Official Site.


Document published on 2026-07-03. Next scheduled retest: 2026-10-03.