Skip to security report
Analytics Dashboard
Domain security and threat intelligence
zhcn-binance.hl.cn favicon

zhcn-binance.hl.cn

In short

zhcn-binance.hl.cn is a Binance impersonation page detected by PhishDestroy on 2026-10-23. Risk: critical (80/100). Registrar: 北京新网数码信息技术有限公司. Status: Last known active. Hosting: OWGELS INTERNATIONAL CO., LIMITED. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

“恭喜，站点创建成功！”

Registrar
北京新网数码信息技术有限公司
Resolved IP
168.222.65.180
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
Stored blocklist matches: 2 Automated brand label: Binance
OTX: 4 refs Oct 23, 2026 1 Report Sent
API
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
0 / 92
engine detections
Google Safe Browsing
No threat flag
OTX
4
community references
Page captures
5
open gallery
Reports sent
1
view timeline
Source evidenceVirusTotal 0 / 92 · OTX 4 references 6 sources

VirusTotal

0 / 92 engine detections

Open report

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
0 / 92
OTX
4 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy’s automated assessment classified zhcn-binance.hl.cn as an impersonation phishing page that pretends to be associated with Binance. The recorded page title was the Chinese phrase “恭喜，站点创建成功！”, which does not contain explicit phishing content. The domain was first seen by PhishDestroy on 2026-10-23 and returned an HTTP 200 response at that time.

How the scam works

Impersonation phishing sites copy the look and name of a legitimate brand to lure users into entering login credentials, two‑factor codes or other sensitive data on a counterfeit interface. Harvested information can be used to hijack accounts or sold to other criminals.

Evidence

VirusTotal scanned the domain on 2026-10-23 with 92 engines and reported zero detections. Google Safe Browsing checked the same day and did not flag the site. URLScan’s machine‑learning engine marked the page as malicious with a score of 99, though its overall verdict was non‑malicious on 2026-10-23. OTX listed four pulses referencing the domain as of 2026-10-23. External blocklists MetaMask and SEAL both included the domain, and PhishDestroy’s internal blocklist added it on 2026-10-23.

Infrastructure

The domain’s TLS certificate was issued on 2026-10-23 and is valid until 2027-01-21. At the time of observation it resolved to IP 168.222.65.180, which belongs to ASN 153656 operated by OWGELS INTERNATIONAL CO., LIMITED in Hong Kong. The authoritative nameservers were ns1.myhostadmin.net and ns2.myhostadmin.net, and no DNSSEC records were present.

What to do

Do not enter Binance credentials or any personal information on this site; if you have already done so, change your Binance password and enable strong two‑factor authentication. Monitor your Binance account for unauthorized activity and contact Binance support if needed. Defenders should block the exact domain zhcn-binance.hl.cn in network filters and review logs for any connections to that hostname.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-23T13:36:38Z)URLQuery screenshotURLScan screenshot (2026-10-23T12:55:52Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-10-23T13:03:59Z

Observed: · Retrieved:

Uuid
01a168dc-168a-77df-8636-9d676a0dec56
Final url
https://zhcn-binance.hl.cn/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://zhcn-binance.hl.cn/",
        "from": "http://zhcn-binance.hl.cn/",
        "status": 307
    }
]
Ip
168.222.65.180
Contacted IP addresses
[
    "168.222.65.180"
]
Asns
[
    "153656"
]
Countries
[
    "HK"
]
Document hash
3b319a1e7740a5e3a99f2b9dd8fcf137f0f32773eb44100b012db3196cc6ae5c
Tls
{
    "san": [
        "zhcn-binance.hl.cn"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "LiteSSL RSA CA 2025",
    "subject": "zhcn-binance.hl.cn",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-21T03:59:59Z",
    "valid_from": "2026-10-23T04:00:00Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}
Cloudflare Radar · 2026-10-23T13:36:38Z

Observed: · Retrieved:

Uuid
7de84ca7-9811-40cd-a4c9-7e9cc210a3aa
Final url
https://zhcn-binance.hl.cn/
Status
200
History
[
    {
        "url": "https://zhcn-binance.hl.cn/",
        "status": 200
    }
]
DOM structure hash
d809486d968b06e97c301d72fe7b95d51cc524174f479c9c720fa18a8a1ec7a0
Document hash
3b319a1e7740a5e3a99f2b9dd8fcf137f0f32773eb44100b012db3196cc6ae5c
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "zhcn-binance.hl.cn",
        "type": "A",
        "value": "168.222.65.180"
    }
]
Dnssec valid
false
Ip
168.222.65.180
Registration record
{
    "registrar": "北京新网数码信息技术有限公司",
    "created": "2026-10-23T13:17:13Z",
    "expires": "2027-10-23T13:17:13Z",
    "nameservers": [
        "ns5.west.cn",
        "ns6.west.cn"
    ]
}
VirusTotal · 2026-10-23T13:48:46Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 0,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 92
}
Reputation
0
Tags
[
    "dga"
]
First seen
2026-10-23T12:58:28Z
DNS records
[
    {
        "ttl": 600,
        "type": "A",
        "value": "168.222.65.180"
    },
    {
        "ttl": 500,
        "type": "SOA",
        "rname": "dnsconct.myhostadmin.net",
        "value": "ns1.myhostadmin.net"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.myhostadmin.net"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.myhostadmin.net"
    }
]
Dns at
2026-10-23T13:54:14Z
Jarm
3fd3fd0003fd3fd21c42d42d000000bdfc58c9a46434368cf60aa440385763
Certificate
{
    "san": [
        "zhcn-binance.hl.cn"
    ],
    "issuer": "TrustAsia Technologies, Inc. / LiteSSL RSA CA 2025",
    "serial": "25d53daaf6de7f186c2243a19f1a342fcc68df45",
    "sha256": "1558c51a1f3e76dcb5f753fa23c69a09c1d7a27651a0b65cae3610fc1a74a6f9",
    "subject": "zhcn-binance.hl.cn",
    "valid_to": "2027-01-21T03:59:59Z",
    "valid_from": "2026-10-23T04:00:00Z"
}
Registration record
{
    "status": [
        "ok"
    ],
    "nameservers": [
        "ns5.west.cn",
        "ns6.west.cn"
    ],
    "dnssec": "unsigned"
}
Website checks · 2026-10-23T13:37:58Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "zhcn-binance.hl.cn"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-23T13:06:20Z",
    "first": "2026-10-23T13:06:20Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1058
}
Page title and metadata
{
    "title": "恭喜，站点创建成功！"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 339,
        "tls": 215,
        "wait": 210,
        "connect": 210,
        "download": 1
    },
    "response_ms": 975
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Carbon
{
    "bytes": 917,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "60.247.150.254",
            "host": "ns1.myhostadmin.net"
        },
        {
            "ip": "61.172.183.73",
            "host": "ns2.myhostadmin.net"
        }
    ],
    "zone": "zhcn-binance.hl.cn"
}
Location
{
    "ip": "168.222.65.180",
    "asn": "153656",
    "org": "OWGELS INTERNATIONAL CO., LIMITED",
    "city": "Tsuen Wan",
    "country": "HK"
}
Ssl
{
    "issuer": "TrustAsia Technologies, Inc. / LiteSSL RSA CA 2025",
    "subject": "zhcn-binance.hl.cn"
}
DNS records
{
    "A": [
        "168.222.65.180"
    ],
    "NS": [
        "ns1.myhostadmin.net",
        "ns2.myhostadmin.net"
    ],
    "SOA": "{\"nsname\": \"ns1.myhostadmin.net\", \"hostmaster\": \"dnsconct.myhostadmin.net\", \"serial\": 2026102402, \"refresh\": 43200, \"retry\": 300, \"expire\": 1209600, \"minttl\": 3600}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "168.222.65.180",
    "family": 4
}
Redirects
{
    "chain": [
        "https://zhcn-binance.hl.cn"
    ]
}
Tech stack
{
    "technologies": [
        "Nginx",
        "HSTS"
    ]
}
Registration record
{
    "registrar": "北京新网数码信息技术有限公司",
    "created": "2026-10-23T11:17:13Z",
    "expires": "2027-10-23T11:17:13Z",
    "status": [
        "ok"
    ],
    "nameservers": [
        "ns5.west.cn",
        "ns6.west.cn"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    }
}

Questions about zhcn-binance.hl.cn

Is zhcn-binance.hl.cn legit?

No. PhishDestroy classifies zhcn-binance.hl.cn as a Binance impersonation page (risk: critical, 80/100); it was first detected on 2026-10-23. Treat the site as unsafe.

Is zhcn-binance.hl.cn safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on zhcn-binance.hl.cn. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used zhcn-binance.hl.cn?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded2026-10-23 13:05 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttp://zhcn-binance.hl.cn/
Position1 / 5
Open capture Wayback Download

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 23, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar 北京新网数码信息技术有限公司
Abuse contactjohnbergeson41@outlook.com, report@abuseradar.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for zhcn-binance.hl.cn →
RegistrationExpires Oct 23, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 80/100
Submitted URLhttp://zhcn-binance.hl.cn/
Case ID
Observed page title
恭喜，站点创建成功！
TLS Certificate
Issued by TrustAsia Technologies, Inc. / LiteSSL RSA CA 2025 · stored validity ends in 89 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
168.222.65.180
Network ASN
AS153656
Organization
OWGELS INTERNATIONAL CO., LIMITED
Observed location
Tsuen Wan, HK
Server header
nginx

Nameservers 4

  • ns1.myhostadmin.net
  • ns2.myhostadmin.net
  • ns5.west.cn
  • ns6.west.cn

Location describes the IP network.

TLS certificate

Issuer
TrustAsia Technologies, Inc. / LiteSSL RSA CA 2025
Valid from
2026-10-23 04:00:00
Valid until
2027-01-21 03:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1558c51a1f3e76dcb5f753fa23c69a09c1d7a27651a0b65cae3610fc1a74a6f9
Certificate names · 1 SAN
  • zhcn-binance.hl.cn

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

viewdns.info · 168.222.65.180rapiddns.io
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of zhcn-binance.hl.cn · checked Oct 23, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.08s
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://zhcn-binance.hl.cn/
恭喜，站点创建成功！
Response
HTTP 200
HTML body
917 B
Compressed
537 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 9
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
917
Content-Type
text/html
Date
Fri, 23 Oct 2026 13:06:28 GMT
Etag
"6adaedef-395"
Last-Modified
Fri, 23 Oct 2026 05:17:35 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    0/92 engine detections

    View source
  4. Abuse report sent

    PD-20261023-A3D7A9

    johnbergeson41@outlook.com
  5. Added to PhishDestroy

    zhcn-binance.hl.cn

    View source
  6. URLScan

    Page captured

    View source

Lookalike domains

187 stored lookalike domains

binanceb.com addition Internal report binancej.com addition Internal report binanceo.com addition Internal report binancep.com addition Internal report binanceu.com addition Internal report binancet.com addition Internal report binancev.com addition Internal report binancez.com addition Internal report benance.com vowel-swap bi.nance.com subdomain biannce.com transposition bin1nce.com replacement
Show all (88)
binabce.com replacement binacne.com transposition binan.ce.com subdomain binancecom.com various binanci.com vowel-swap binanco.com vowel-swap binancr.com replacement binancs.com replacement binancw.com replacement binande.com replacement binanfe.com replacement binanve.com replacement binanxe.com replacement binnace.com transposition binonce.com vowel-swap binsnce.com replacement binunce.com vowel-swap binynce.com replacement binznce.com replacement bniance.com transposition bunance.com replacement ibnance.com transposition ninance.com replacement b-inance.com hyphenation b8inance.com insertion b8nance.com replacement b9nance.com replacement bbinance.com repetition bhinance.com insertion bi-nance.com hyphenation biance.com omission bibance.com replacement bibnance.com insertion bihance.com replacement bihnance.com insertion biinance.com repetition bijnance.com insertion biknance.com insertion bimance.com homoglyph bimnance.com insertion bin-ance.com hyphenation binaance.com repetition binabnce.com insertion binace.com omission binahce.com replacement binamnce.com insertion binan-ce.com hyphenation binanbce.com insertion binanc-e.com hyphenation binanc.com omission binanc3.com replacement binancce.com repetition binancve.com insertion binancxe.com insertion binancz.com replacement binandce.com insertion binane.com omission binanec.com homoglyph binanhce.com insertion binanmce.com insertion binannce.com homoglyph binanvce.com insertion binanxce.com insertion binarnce.com homoglyph binasnce.com insertion binawnce.com insertion binbance.com insertion binhance.com insertion binmance.com insertion binnance.com homoglyph binnce.com omission binqance.com insertion binsance.com insertion binwnce.com replacement binyance.com insertion bionance.com insertion birnance.com homoglyph biunance.com insertion bjnance.com replacement bnance.com omission bninance.com insertion boinance.com insertion bonance.com replacement buinance.com insertion bvinance.com insertion clinance.com homoglyph dinarce.com homoglyph ginance.com replacement

Showing 100 of 187

Check for cloaking

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

zhcn-binance.hl.cn

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-A3D7A9 Recipient: johnbergeson41@outlook.com
PDF notice generated
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 zhcn-binance.hl.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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
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.

Request a correction or appeal How PhishDestroy works
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/zhcn-binance.hl.cn"
  title="PhishDestroy threat report for zhcn-binance.hl.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>