onchain-binance.com is an impersonation phishing site that uses the Binance name to target the exchange's customers and anyone looking for its on-chain or Web3 services. PhishDestroy first detected it on 2026-10-09. When last checked on 2026-10-19, the domain was still alive and its content was reachable through a redirect, so it remains a live risk.
How the scam works
Sites like this borrow a trusted exchange brand and add a plausible word like "onchain" to the domain, so a link in a search ad, social post or direct message looks like an official Binance page. The visitor is then pushed to sign in, verify an account or connect a wallet. Anything entered or approved goes to the operators. That can mean stolen exchange credentials and 2FA codes, or wallet permissions that let them move funds. The page currently carries the title "Google", while we classify the site as Binance impersonation phishing.
Evidence
Six of 92 VirusTotal engines flagged the domain as of 2026-10-17: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That count is modest, so many security products will not yet block it. The stronger signal comes from crypto-specific defenses. Besides PhishDestroy, the domain appears on the MetaMask and SEAL blocklists, and it is referenced in three AlienVault OTX threat pulses.
Infrastructure
The domain was registered on 2026-10-02, just seven days before PhishDestroy caught it. That short gap is typical of throwaway phishing domains spun up for a quick campaign. It is registered through Cloudflare, Inc. and served from Cloudflare's network, geolocated to Canada. Because Cloudflare acts as a proxy, the address in front of the site does not reveal the operators' actual origin server.
What to do
If you entered Binance credentials on this site, change your password from the official app immediately and reset your 2FA. Then review active sessions, API keys and withdrawal whitelist addresses for anything you did not add. If you connected a wallet or signed anything, revoke token approvals with a trusted revocation tool. Move remaining assets to a fresh wallet if you shared a seed phrase. Contact Binance support through the official app if you see unauthorized activity. Defenders should block the domain at DNS and proxy level, search mail and chat logs for links to it, and report it to Cloudflare for takedown.
注册信息创建 2026年10月2日 (18d · Very New!)—Expires 2027年10月2日
HTTP 状态码302 Found (Temporary)
技术详情Provenance & timestamps
首次发现2026年10月9日
DOM Analysisanalyzed 2026年10月9日score 100/1002 brand signals
Submitted URLhttp://onchain-binance.com/
Favicon Hash
Observed page title
Google
Automated brand references
AppleGoogle
TLS 证书
颁发者 Let's Encrypt / YE1· stored validity ends in 71 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP 声誉不属于此域。
域名服务器 2
audrey.ns.cloudflare.com
dean.ns.cloudflare.com
Location describes the IP network.
TLS 证书
Issuer
Let's Encrypt / YE1
Valid from
2026-10-02 12:25:58
Valid until
2026-12-31 12:25:57
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-09 19:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte7c1cbdd93f9d87736cb4811b9e720d7efb6a55c125f0657c87f5f08a8e68cfaCertificate names · 2 SANs
*.onchain-binance.com
onchain-binance.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-21 02:25:51 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-21 02:25:51 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
我应该立即采取什么措施？
紧急
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(US)
