Skip to security report
Dangerous

Phishing copy of Binance

topic-binance.com.cn favicon
Domain security and threat intelligence

topic-binance.com.cn

Real sitebinance.com
This sitetopic-binance.com.cn
I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded topic-binance.com.cn on 2026-10-27. Listed by external blocklists: MetaMask, SEAL.

Page title: “币安交易平台 - Binance 中文版”

More about the sources
Recorded security signals

Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

Spamhaus DBL: phishing domain Stored blocklist matches: 2
Registrar
United StatesDynadot
Resolved IP
Canada104.21.57.167Cloudflare, Inc. · CDN
First seen by PhishDestroy
2026-10-27
OTX
community references
Page captures
open gallery
Reports sent
view timeline
OTX: 3 refs 2026-10-27 1 Report Sent CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is lingxiaoajling@gmail.com. The latest stored availability evidence still shows the domain reachable; 26 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
26 days
Reports sent
1
Latest case ID
PD-20261027-8ED324
Current status
HTTP 301 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded topic-binance.com.cn on 2026-10-27. Listed by external blocklists: MetaMask, SEAL. Risk: critical (evidence score 100/100). Registrar: Dynadot. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
Blocklist matches
2 external + PhishDestroy list
Scam type (automated label)
Impersonation
Hosting
Canada104.21.57.167Cloudflare, Inc. · CDN
Registrar
United StatesDynadot
OTX
3 community refs
Page captures
7

PhishDestroy analysis, earlier unreviewed version

Overview

PhishDestroy’s intake AI assessment on 2026-10-27 classified the site as malicious because the recorded page title uses Binance’s name and branding and the page prompts registration and app download. The domain was first seen by PhishDestroy on 2026-10-27. An HTTP 301 redirect was observed for the domain on that date.

How the scam works

In a typical fake‑exchange phishing campaign, attackers create a look‑alike site that mimics a well‑known exchange’s branding to lure victims. They then encourage users to register or download a client app, capturing login credentials or prompting wallet authorizations that can be abused to steal funds.

Evidence

VirusTotal scanned the domain on 2026-10-26 and reported zero detections from 92 engines. Google Safe Browsing checked on 2026-10-27 and did not flag the site. URLScan produced a clean verdict on 2026-10-26 and a malicious phishing verdict on 2026-10-27 with a score of 100 and Binance identified as the impersonated brand. OTX listed three pulses referencing the domain on 2026-10-27. External blocklists MetaMask and SEAL both listed the domain, and PhishDestroy’s internal blocklist includes it as of 2026-10-27.

Infrastructure

The recorded IP addresses for topic-binance.com.cn on 2026-10-27 were 172.67.164.236 and 104.21.57.167, both belonging to Cloudflare’s network (AS13335). A Let’s Encrypt TLS certificate for *.topic-binance.com.cn was issued on 2026-10-26 and is valid until 2027-01-24. Cloudflare Radar marked the domain as newly seen and flagged it for security risks.

What to do

Users should avoid entering any Binance credentials or downloading the offered app; if credentials were entered, change passwords immediately. Organizations should block traffic to topic-binance.com.cn, monitor access logs for connections, and add the domain to internal blocklists. Reference the URLScan malicious verdict when investigating potential phishing incidents.

Source evidenceOTX 3 references 6 sources

Spamhaus DBL

phishing domain

URLScan

Malicious

SHA-256 9518568b…23bc66d

Open report
URLScanOriginal source recordObserved: 18 fields
Separate monitor record

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1799b-37ac-753e-b3eb-4147f07339d0
Enriched at
2026-10-27T09:14:00Z
Source timestamps
Urlscan enriched at: 2026-10-27 10:14:00

OTX

3 community references

Open report

PhishDestroy DOM

95 / 100 · heuristic score · 1 brand reference · 1 classification

Content heuristic only; not the final score

Open report
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
topic-binance.com.cn — Binance Impersonation Phishing
AI description
PhishDestroy flags topic-binance.com.cn as a malicious site impersonating Binance, offering a Chinese‑language trading portal and app download.
AI summary
Overview PhishDestroy’s intake AI assessment on 2026-10-27 classified the site as malicious because the recorded page title uses Binance’s name and branding and the page prompts registration and app download. The domain was first seen by PhishDestroy on 2026-10-27. An HTTP 301 redirect was observed for the domain on that date. How the scam works In a typical fake‑exchange phishing campaign, attackers create a look‑alike site that mimics a well‑known exchange’s branding to lure victims. They then encourage users to register or download a client app, capturing login credentials or prompting wallet authorizations that can be abused to steal funds. Evidence VirusTotal scanned the domain on 2026-10-26 and reported zero detections from 92 engines. Google Safe Browsing checked on 2026-10-27 and did not flag the site. URLScan produced a clean verdict on 2026-10-26 and a malicious phishing verdict on 2026-10-27 with a score of 100 and Binance identified as the impersonated brand. OTX listed three pulses referencing the domain on 2026-10-27. External blocklists MetaMask and SEAL both listed the domain, and PhishDestroy’s internal blocklist includes it as of 2026-10-27. Infrastructure The recorded IP addresses for topic-binance.com.cn on 2026-10-27 were 172.67.164.236 and 104.21.57.167, both belonging to Cloudflare’s network (AS13335). A Let’s Encrypt TLS certificate for *.topic-binance.com.cn was issued on 2026-10-26 and is valid until 2027-01-24. Cloudflare Radar marked the domain as newly seen and flagged it for security risks. What to do Users should avoid entering any Binance credentials or downloading the offered app; if credentials were entered, change passwords immediately. Organizations should block traffic to topic-binance.com.cn, monitor access logs for connections, and add the domain to internal blocklists. Reference the URLScan malicious verdict when investigating potential phishing incidents. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a17b9c-2c7a-75cf-b84b-0d20d797aa6c/ Cloudflare Radar report: https://radar.cloudflare.com/scan/9c0dce21-63c6-46a0-8d4d-d19dcd7d0842 URLQuery report: https://urlquery.net/report/99efa90d-c196-4f42-8f93-dccceabb60ba Stored capture screenshot: https://i.ibb.co/kVb7mG0f/58bb676aa6dc.png Cloudflare Radar screenshot (2026-10-27T04:22:34Z): https://screenshots.phishdestroy.io/cf/9c0dce21-63c6-46a0-8d4d-d19dcd7d0842.png URLQuery screenshot: https://screenshots.phishdestroy.io/uq/99efa90d-c196-4f42-8f93-dccceabb60ba.png URLScan screenshot (2026-10-26T19:06:29Z): https://screenshots.phishdestroy.io/us/01a1799b-37ac-753e-b3eb-4147f07339d0.png URLScan capture report: https://urlscan.io/result/01a1799b-37ac-753e-b3eb-4147f07339d0/ URLScan screenshot (2026-10-27T04:34:53Z): https://screenshots.phishdestroy.io/us/01a17ba3-ad5c-711b-884b-d2492d68817c.png URLScan capture report: https://urlscan.io/result/01a17ba3-ad5c-711b-884b-d2492d68817c/ VirusTotal report: https://www.virustotal.com/gui/domain/topic-binance.com.cn Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=topic-binance.com.cn Archived copy: https://web.archive.org/web/20261027042245/https://topic-binance.com.cn/zh-CN Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
AI generated by
threat-v3-groq
AI generated at
2026-10-27T05:08:04Z
Revision
17d516f5a2d046307e5940e96a71d10fa956c941c95ffdefe0e2242cdcc9939d
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
VirusTotalOriginal source recordObserved: 8 fields
Open complete records
Website checksOriginal source recordRetrieved: 25 fields

Mail configuration

SPF lookups
0

CAA records

Domain
topic-binance.com.cn

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://topic-binance.com.cn/sitemap.xml

Sitemap

Present
Yes
URL count
2

Page title and metadata

Open Graph URL
https://topic-binance.com.cn/zh-CN
Page title
币安交易平台 - Binance 中文版
Open Graph type
website
Indexing directives
index, follow
Open Graph title
币安交易平台 - Binance 中文版
Open Graph site name
币安 Binance
Description
币安 Binance 中文版品牌首页,了解平台介绍、核心交易功能、安全保障与资产管理服务,探索数字资产世界的便捷入口。
Twitter card
summary
Canonical URL
https://topic-binance.com.cn/zh-CN
Open Graph description
币安 Binance 中文版品牌首页,了解平台介绍、核心交易功能、安全保障与资产管理服务,探索数字资产世界的便捷入口。

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
301
Request timings, ms
DNS
212
TLS
59
Waiting
610
Connection
9
Download
0
Response time, ms
890

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
34754
CO₂, grams
0.0013
Cleaner than, %
45

DNS servers

Nameservers
  • IP address
    172.64.33.141
    Host
    sam.ns.cloudflare.com
  • IP address
    172.64.32.77
    Host
    brenda.ns.cloudflare.com
DNS zone
topic-binance.com.cn

Location

IP address
2606:4700:3036::6815:39a7
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
topic-binance.com.cn

DNS records

A
  • 172.67.164.236
  • 104.21.57.167
NS
  • brenda.ns.cloudflare.com
  • sam.ns.cloudflare.com
SOA
Primary nameserver
brenda.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418527270
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3036::6815:39a7
  • 2606:4700:3036::ac43:a4ec

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3036::6815:39a7
IP version
6

Redirects

Redirect chain
  • https://topic-binance.com.cn
  • https://topic-binance.com.cn/zh-CN
Count
1

Page links

External link addresses
  • https://download.bsmkweb.cc/pack/BNApp_F0001837.apk
  • https://www.bsmkweb.cc/zh-CN/register
  • https://www.topic-binance.com.cn/zh-CN
  • https://zh.topic-binance.com.cn/zh-CN
  • https://cn.topic-binance.com.cn/zh-CN
  • https://zhcn.topic-binance.com.cn/zh-CN
  • https://web.topic-binance.com.cn/zh-CN
  • https://app.topic-binance.com.cn/zh-CN
  • https://home.topic-binance.com.cn/zh-CN
  • https://btc.topic-binance.com.cn/zh-CN
  • https://boot.topic-binance.com.cn/zh-CN
  • https://deriv.topic-binance.com.cn/zh-CN
  • https://c2c.topic-binance.com.cn/zh-CN
  • https://p2p.topic-binance.com.cn/zh-CN
  • https://web3.topic-binance.com.cn/zh-CN
  • https://earn.topic-binance.com.cn/zh-CN
  • https://wallet.topic-binance.com.cn/zh-CN
  • https://market.topic-binance.com.cn/zh-CN
  • https://trade.topic-binance.com.cn/zh-CN
External links
19
Internal links
7

Registration record

Registrar
Dynadot Inc
Registered
Expires
Status
  • clientTransferProhibited
Nameservers
  • sam.ns.cloudflare.com
  • brenda.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=utf-8
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Domain: topic-binance.com.cn
Protective DNS results
Resolvers: 12; Blocked count: 0
Crawler rules
Agents: *; Present: ✓; Sitemaps: https://topic-binance.com.cn/sitemap.xml
Sitemap
Present: ✓; URL count: 2
Page title and metadata
Ogurl: https://topic-binance.com.cn/zh-CN; Title: 币安交易平台 - Binance 中文版; Ogtype: website; Robots: index, follow; Ogtitle: 币安交易平台 - Binance 中文版; Ogsitename: 币安 Binance; Description: 币安 Binance 中文版品牌首页,了解平台介绍、核心交易功能、安全保障与资产管理服务,探索数字资产世界的便捷入口。; Twittercard: summary; Canonicalurl: https://topic-binance.com.cn/zh-CN; Ogdescription: 币安 Binance 中文版品牌首页,了解平台介绍、核心交易功能、安全保障与资产管理服务,探索数字资产世界的便捷入口。
Trackers
Requests: 2
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 301; Timings: DNS: 212; TLS: 59; Wait: 610; Connect: 9; Download: 0; Response ms: 890
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 34754; Co2 grams: 0.0013; Cleaner than: 45
DNS server
NS: (IP: 172.64.33.141; Host: sam.ns.cloudflare.com), (IP: 172.64.32.77; Host: brenda.ns.cloudflare.com); Zone: topic-binance.com.cn
Location
IP: 2606:4700:3036::6815:39a7; ASN: 13335; Org: Cloudflare, Inc.; City: Toronto; Country: CA
SSL
Issuer: Let's Encrypt / YE1; Subject: topic-binance.com.cn
DNS records
A: 172.67.164.236, 104.21.57.167; NS: brenda.ns.cloudflare.com, sam.ns.cloudflare.com; Soa: Nsname: brenda.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2418527270; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:3036::6815:39a7, 2606:4700:3036::ac43:a4ec
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:3036::6815:39a7; Family: 6
Redirects
Chain: https://topic-binance.com.cn, https://topic-binance.com.cn/zh-CN; Count: 1
Page links
External: https://download.bsmkweb.cc/pack/BNApp_F0001837.apk, https://www.bsmkweb.cc/zh-CN/register, https://www.topic-binance.com.cn/zh-CN, https://zh.topic-binance.com.cn/zh-CN, https://cn.topic-binance.com.cn/zh-CN, https://zhcn.topic-binance.com.cn/zh-CN, https://web.topic-binance.com.cn/zh-CN, https://app.topic-binance.com.cn/zh-CN, https://home.topic-binance.com.cn/zh-CN, https://btc.topic-binance.com.cn/zh-CN, https://boot.topic-binance.com.cn/zh-CN, https://deriv.topic-binance.com.cn/zh-CN, https://c2c.topic-binance.com.cn/zh-CN, https://p2p.topic-binance.com.cn/zh-CN, https://web3.topic-binance.com.cn/zh-CN, https://earn.topic-binance.com.cn/zh-CN, https://wallet.topic-binance.com.cn/zh-CN, https://market.topic-binance.com.cn/zh-CN, https://trade.topic-binance.com.cn/zh-CN; External count: 19; Internal count: 7
Registration record
Registrar: Dynadot Inc; Created: 2026-10-25T09:46:52Z; Expires: 2027-10-25T08:46:52Z; Status: clientTransferProhibited; Nameservers: sam.ns.cloudflare.com, brenda.ns.cloudflare.com
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=utf-8

Questions about topic-binance.com.cn

Is topic-binance.com.cn legit?

PhishDestroy rates topic-binance.com.cn as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-27. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is topic-binance.com.cn safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on topic-binance.com.cn. A confirmed blockchain transaction cannot be reversed.

What should I do if I used topic-binance.com.cn?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (7)

All capture links and hashes (7)
topic-binance.com.cn: Binance impersonation — Blocked by MetaMask, flagged by SEAL, Spamhaus DBL. PhishDestroy risk score 95/100 (critical).
Social preview card topic-binance.com.cn: Binance impersonation — Blocked by MetaMask, flagged by SEAL, Spamhaus DBL. PhishDestroy risk score 95/100 (critical). v cee1e2a3e6f6

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Binance report ↗
IP Context Canada104.21.57.167 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
RegistrationExpires 2027-10-25
WHOIS statusTransfer locked (registrar)
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First Detected2026-10-27
DOM Analysisanalyzed 2026-10-27score 95/1001 brand signal
Submitted URLhttp://topic-binance.com.cn/
Favicon Hash
Case ID
Observed page title
币安交易平台 - Binance 中文版
Automated brand references
Binance
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 63 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada104.21.57.167
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • brenda.ns.cloudflare.com
  • sam.ns.cloudflare.com

SOA

  • nsname: brenda.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418527270
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-26 13:41:38
Valid until
2027-01-24 13:41:37
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintd4c5e826ebb689807b8953680a44a3d8c148e043574f9f1fcb3f8cfc3f00a6ad
Certificate names · 2 SANs
  • *.topic-binance.com.cn
  • topic-binance.com.cn

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-11-21 11:02 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-21 11:02 UTC
RDAP registration
Observed timeline last reachable: 2026-11-21 11:02 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.
Technologies · 2 identified
Open complete records

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 96

Google PageSpeed Insights — mobile performance audit of topic-binance.com.cn ·

96
Good
Performance
FCP
0.91 s
First Contentful Paint
LCP
2.1 s
Largest Contentful Paint
CLS
0.107
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.65 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://topic-binance.com.cn/
Final URL: https://topic-binance.com.cn/zh-CN
币安交易平台 - Binance 中文版
币安 Binance 中文版品牌首页,了解平台介绍、核心交易功能、安全保障与资产管理服务,探索数字资产世界的便捷入口。
Response
HTTP 200
HTML body
33.9 KB
Compressed
7.7 KB
Links
81 internal · 2 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: 币安交易平台 - Binance 中文版
Open Graph description: 币安 Binance 中文版品牌首页,了解平台介绍、核心交易功能、安全保障与资产管理服务,探索数字资产世界的便捷入口。
Twitter card: summary
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a50ee95e5d09dc7d-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Tue, 27 Oct 2026 04:21:02 GMT
Last-Modified
Sun, 25 Oct 2026 03:36:09 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=X8uYQYwFDtXQUKnLJgP9ULzZqChNyhrro4P5FvoA5bMKa5oDyOafBh9SxNjaJBH1a9Ky97kySSKd8exNMNCfPlApP%2Ffx8plWw7hxgwhqivqP%2FzXDXXqjejzrqlR8vnvE1ITMpJJXEA%
Server
cloudflare
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data123
Open complete records

Captured network requests

Network requests: 4 SHA-256 hashes: 4 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:55 UTC.

Open this scan on URLScan 01a17b9c-2c7a-75cf-b84b-0d20d797aa6c ↗

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

Our scanner could not complete this check.

Browser
币安交易平台 - Binance 中文版
Crawler
301 Moved Permanently
topic-binance.com.cn
Stored observation history22
Open complete records
All retained availability observations105
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    topic-binance.com.cn detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Blocklist Detection · OTX Community References · Automated brand label: Binance · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Dynadot Inc. Abuse contacts: 1.
    • lingxiaoajling@gmail.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

5 entries

Lifecycle

  1. Added to PhishDestroy
  2. First abuse report sent+22 min
  1. AlienVault OTX

    3 community references

    +19 min
  2. Abuse report sent

    PD-20261027-8ED324 · Receipt 83679

    lingxiaoajling@gmail.com
    +14 min
  3. URLScan

    Page captured

    +5 min
  4. Wayback Machine

    Page archived

    +2 min
  5. Added to PhishDestroy

    topic-binance.com.cn

How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Lookalike domains

187 stored lookalike domains

Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.

Showing 12 of 187

Show 88 more
binabce.com Replaced character Variant of binance.com NS ns1.dnsowl.com binacne.com Swapped characters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binan.ce.com Split into subdomain Variant of binance.com A 13.248.169.48NS ns1.afternic.com binancecom.com Variant Variant of binance.com A 46.175.135.11MX mail.radinko.comNS ns1.radinko.com binanci.com Vowel swap Variant of binance.com A 107.161.23.204NS ns1.dnsowl.com binanco.com Vowel swap Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binancr.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binancs.com Replaced character Variant of binance.com A 34.111.46.214NS dora.ns.cloudflare.com binancw.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binande.com Replaced character Variant of binance.com NS melina.ns.cloudflare.com binanfe.com Replaced character Variant of binance.com A 34.111.46.214NS dora.ns.cloudflare.com binanve.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanxe.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binnace.com Swapped characters Variant of binance.com A 207.246.78.75NS ns1.dnsowl.com binonce.com Vowel swap Variant of binance.com A 103.224.182.241MX park-mx.above.comNS ns1.abovedomains.com binsnce.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binunce.com Vowel swap Variant of binance.com A 103.224.212.251NS ns1.abovedomains.com binynce.com Replaced character Variant of binance.com A 94.75.193.73MX mail.h-email.netNS ns1.thednscloud.com binznce.com Replaced character Variant of binance.com NS dns1.registrar-servers.com bniance.com Swapped characters Variant of binance.com A 103.59.100.240NS carlos.ns.cloudflare.com bunance.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net ibnance.com Swapped characters Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com ninance.com Replaced character Variant of binance.com A 52.20.84.62NS ns1.atom.com b-inance.com Added hyphen Variant of binance.com A 198.16.35.91NS a.share-dns.com b8inance.com Inserted character Variant of binance.com A 46.8.8.220MX mail.parktons.comNS ns.parktons.com b8nance.com Replaced character Variant of binance.com A 103.224.182.238MX park-mx.above.comNS ns1.abovedomains.com b9nance.com Replaced character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com bbinance.com Repeated character Variant of binance.com A 47.52.200.94NS donald.ns.cloudflare.com bhinance.com Inserted character Variant of binance.com A 46.175.135.11MX mail.radinko.comNS ns1.radinko.com bi-nance.com Added hyphen Variant of binance.com A 34.133.74.21NS ns-cloud-d1.googledomains.com biance.com Missing character Variant of binance.com A 8.223.50.77MX route1.mx.cloudflare.netNS raphaela.ns.cloudflare.com bibance.com Replaced character Variant of binance.com A 107.161.23.204NS ns1.dnsowl.com bibnance.com Inserted character Variant of binance.com A 103.224.182.253MX park-mx.above.comNS ns1.abovedomains.com bihance.com Replaced character Variant of binance.com A 104.21.54.163NS dora.ns.cloudflare.com bihnance.com Inserted character Variant of binance.com A 188.114.96.3NS cass.ns.cloudflare.com biinance.com Repeated character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net bijnance.com Inserted character Variant of binance.com A 62.116.130.8MX redirect.domain-robot.orgNS a.ns14.net biknance.com Inserted character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com bimance.com Lookalike letters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net bimnance.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com bin-ance.com Added hyphen Variant of binance.com A 13.248.169.48NS ns1.afternic.com binaance.com Repeated character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binabnce.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binace.com Missing character Variant of binance.com A 104.21.80.13NS josephine.ns.cloudflare.com binahce.com Replaced character Variant of binance.com A 209.196.146.115NS ns3.epik.com binamnce.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binan-ce.com Added hyphen Variant of binance.com NS a.share-dns.com binanbce.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binanc-e.com Added hyphen Variant of binance.com A 188.114.96.3MX route1.mx.cloudflare.netNS melinda.ns.cloudflare.com binanc.com Missing character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanc3.com Replaced character Variant of binance.com A 34.111.46.214NS dora.ns.cloudflare.com binancce.com Repeated character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binancve.com Inserted character Variant of binance.com A 104.21.19.3NS dora.ns.cloudflare.com binancxe.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binancz.com Replaced character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binandce.com Inserted character Variant of binance.com A 62.116.130.8MX redirect.domain-robot.orgNS a.ns14.net binane.com Missing character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanec.com Lookalike letters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanhce.com Inserted character Variant of binance.com NS a.ns14.net binanmce.com Inserted character Variant of binance.com A 104.21.5.88NS dante.ns.cloudflare.com binannce.com Lookalike letters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanvce.com Inserted character Variant of binance.com A 104.21.62.177NS dora.ns.cloudflare.com binanxce.com Inserted character Variant of binance.com A 188.114.96.3NS dora.ns.cloudflare.com binarnce.com Lookalike letters Variant of binance.com NS ns1.julydns.com binasnce.com Inserted character Variant of binance.com A 104.21.91.34NS dora.ns.cloudflare.com binawnce.com Inserted character Variant of binance.com A 46.8.8.220MX mail.parktons.comNS ns.parktons.com binbance.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binhance.com Inserted character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com binmance.com Inserted character Variant of binance.com A 103.224.212.244NS ns1.abovedomains.com binnance.com Lookalike letters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binnce.com Missing character Variant of binance.com A 34.212.97.116NS a.dnspod.com binqance.com Inserted character Variant of binance.com A 172.233.219.123MX mx156.hostedmxserver.comNS ns1.parklogic.com binsance.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binwnce.com Replaced character Variant of binance.com A 104.21.45.206NS dante.ns.cloudflare.com binyance.com Inserted character Variant of binance.com A 62.116.130.8MX redirect.domain-robot.orgNS a.ns14.net bionance.com Inserted character Variant of binance.com A 81.169.145.65MX smtpin.rzone.deNS docks10.rzone.de birnance.com Lookalike letters Variant of binance.com MX ALT1.ASPMX.L.GOOGLE.comNS 1-you.njalla.no biunance.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com bjnance.com Replaced character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com bnance.com Missing character Variant of binance.com A 13.248.169.48NS ns1.afternic.com bninance.com Inserted character Variant of binance.com A 104.21.36.233NS dante.ns.cloudflare.com boinance.com Inserted character Variant of binance.com A 94.75.193.70MX mail.h-email.netNS ns1.thednscloud.com bonance.com Replaced character Variant of binance.com A 198.185.159.145MX alt1.aspmx.l.google.comNS ns-cloud-b1.googledomains.com buinance.com Inserted character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com bvinance.com Inserted character Variant of binance.com A 13.248.169.48NS ns3.afternic.com clinance.com Lookalike letters Variant of binance.com A 52.44.244.98MX mail1.namebrightmail.comNS ns1.namebrightdns.com dinarce.com Lookalike letters Variant of binance.com A 44.227.65.245MX fwd1.porkbun.comNS curitiba.ns.porkbun.com ginance.com Replaced character Variant of binance.com A 13.248.158.7NS 1ns.yahoo.com

Showing 100 of 187

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261027-8ED324 Recipient: lingxiaoajling@gmail.com
Page title stored with report: 币安交易平台 - Binance 中文版
Blocklist hits included with submission: MetaMask, SEAL
PDF notice generated Notice text archived (291 characters)
Abuse notice text as sent to the provider
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including topic-binance.com.cn)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

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?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/topic-binance.com.cn"
  title="PhishDestroy threat report for topic-binance.com.cn"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>