Skip to security report
Analytics Dashboard
Domain security report
apph5-binance.com.cn favicon

apph5-binance.com.cn

“币安 - binanceApp下载”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
Stored blocklist matches: 2 Automated brand label: Binance Young domain: 1 days old
OTX: 4 refs Oct 15, 2026 Binance 1 Report Sent
API
Registrar
Web Commerce Communica…
Resolved IP
154.210.244.222
Registered
Oct 15, 2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 24H+ 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 liujianjian258@gmail.com. The latest stored availability evidence still shows the domain reachable; 46 hours 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
46 hours
Reports sent
1
Latest case ID
PD-20261015-FF0FF0
Current status
HTTP 200 at latest stored check

Additional indicators at a glance

OTX references
4 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Hostname mismatch
Sectigo Limited / Sectigo Public Server Authentication CA DV R36 · Certificate hostname mismatch
Age
1d Brand New!
Observed status
Last known active 200
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

VirusTotal

checked — no detections recorded

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

4 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: suspicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
OTX
4 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

The domain apph5-binance.com.cn was observed in a security context with a PhishDestroy internal listing on 2026-10-15. On the same date, VirusTotal recorded a scan of the domain. Additional intelligence was captured from OTX, which referenced four pulses for this domain.

Recorded Evidence

PhishDestroy internally listed apph5-binance.com.cn on 2026-10-15. VirusTotal checked the domain on 2026-10-15, recording 0 detections out of 92 scanners. OTX referenced the domain in four pulses as of 2026-10-15. The SSL certificate for this domain was issued by Sectigo Limited / Sectigo Public Server Authentication CA DV R36 and was scanned on 2026-10-15.

Interpretation

PhishDestroy provides a listing for this domain, documenting its presence in their internal catalogue. VirusTotal’s record contains the results of a multi-scanner security check, while OTX records the domain’s inclusion in several intelligence pulses. These sources together offer a technical snapshot of how apph5-binance.com.cn has been referenced and scanned in security intelligence systems as of the recorded dates.

Recommended Actions

For ongoing monitoring, retain the PhishDestroy internal listing and VirusTotal scan results for apph5-binance.com.cn. Compare future OTX pulse references and VirusTotal scanner results for any changes in recorded observations. Maintain a record of the SSL certificate scan for technical context in future reviews.

Data coverage & collection

23 · datasets with records / 8 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
0 / 92 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
2 · external matches
Cloudflare Radar
suspiciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Web Commerce Communications LimitedCollection time not recorded
Network & DNS
154.210.244.222 · 4 · nameserversCollection time not recorded
TLS certificate
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
2 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
Response records
1 · outgoing report records
Availability history
4 · stored state changes
Source observation history
1 · stored source events
Lookalike relationships
100 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 8

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • PageSpeed performance
  • Recorded subdomains
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Web Commerce Communications Limited · 154.210.244.222 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 15, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Web Commerce Communica… MY(MY)
Abuse contactliujianjian258@gmail.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for apph5-binance.com.cn →
RegistrationCreated Oct 15, 2026 (1d · Brand New!) — Expires Oct 15, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 15, 2026
DOM Analysisanalyzed Oct 15, 2026score 80/1002 brand signals
Submitted URLhttp://apph5-binance.com.cn/
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
154.210.244.222
Network ASN
AS9294
Organization
GNET INC.
Observed location
Hong Kong, HK
Server header
nginx
Nameservers 4
  • a.share-dns.com
  • a6.share-dns.com
  • b.share-dns.net
  • b6.share-dns.net

Location describes the IP network.

TLS certificate

Issuer
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Valid from
2026-10-15 00:00:00
Valid until
2027-05-01 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-15 16:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint5944abf0b34cff890b3fdd4d18994ee9eeb3d9be0cd4a4b5726bfc587ad68f84
Certificate names · 1 SANs
  • www.apph5-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.

viewdns.info · 154.210.244.222rapiddns.io

Latest Classified Outcome 2026-10-17 10:45:43 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-17 10:45:43 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 10:45:43 UTC last content: 2026-10-17 10:45:43 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
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
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://apph5-binance.com.cn/
Final URL: https://apph5-binance.com.cn/
币安 - binanceApp下载
了解币安相关产品资讯、官网识别、App下载安全、注册流程、AI技术与行业动态，提供独立、清晰、实用的中文指南。
Response
HTTP 200
HTML body
47.2 KB
Compressed
17.5 KB
Links
26 internal · 8 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=UTF-8
Cache-Control: no-store, no-cache, must-revalidate
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: 币安 - binanceApp下载
Open Graph description: 了解币安相关产品资讯、官网识别、App下载安全、注册流程、AI技术与行业动态，提供独立、清晰、实用的中文指南。
Saved response-header values · 11
Cache-Control
no-store, no-cache, must-revalidate
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Thu, 15 Oct 2026 14:59:14 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Pragma
no-cache
Server
nginx
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Archived
Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-15 14:59:16 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-15 14:59:16 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-15 14:59:16 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Registration & observation details3

Availability observations

Last reachable observation
Last content 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.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
nginx
Capture routing
Local archived 2026-10-15 14:59:16 UTC

Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-10-15 14:58:36 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 154.210.244.222.
Stored observation history5

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

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  5. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

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

Threat Ingested
apph5-binance.com.cn detected and queued for full analysis
Oct 15, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Oct 15, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Oct 17, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 17, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 15, 2026
Brand Impersonation
Impersonation of Binance
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Oct 15, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Web Commerce Communications Limited, 1 abuse contact
liujianjian258@gmail.com
Oct 15, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Oct 15, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

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

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery Report stored SSL Labs Certificate hostname mismatch 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-20261015-FF0FF0 Recipient: liujianjian258@gmail.com
Page title stored with report: 币安 - binanceApp下载
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider 
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
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 Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

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 apph5-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

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
Read the evidence in context

About This Report: apph5-binance.com.cn

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “币安 - binanceApp下载”. Apparent target: Binance.

Stored VirusTotal result for apph5-binance.com.cn: 92 engines checked. Observed: 2026-10-15 16:01:57 UTC

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A 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/apph5-binance.com.cn"
  title="PhishDestroy threat report for apph5-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>