Spamhaus DBL
DBL_PHISH
“币安 Binance · 币安官网”
The domain h5-binance.com.cn was observed in a MetaMask blocklist entry dated 2026-10-11, documenting its inclusion on that external list as of that date. The domain was also referenced in multiple other security sources, providing a broader context for its recorded status.
On 2026-10-11, MetaMask and SEAL both listed h5-binance.com.cn on their respective external blocklists. OTX recorded four pulses referencing the domain on the same date. PhishDestroy contained an internal listing for the domain as of 2026-10-11.
PhishDestroy provides an internal listing for h5-binance.com.cn, which records its presence in their database on the stated date. OTX pulses represent community-submitted intelligence, documenting references or reports about the domain from various contributors. The inclusion of the domain on MetaMask and SEAL blocklists, alongside OTX and PhishDestroy records, captures a multi-source snapshot of its status within different security monitoring contexts.
For h5-binance.com.cn, preserve the MetaMask and SEAL blocklist entries for future reference and blocklist comparison. Retain the OTX pulse records and the PhishDestroy internal listing to track any changes or new observations. Use these source records to inform ongoing monitoring and review of the domain’s recorded status across security intelligence sources.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=https_proxy; location=https://h5-binance.com.cn/zh-CN; server=cloudflare
Edge-IP reputation is not attributed to this domain.
brenda.ns.cloudflare.comsam.ns.cloudflare.comLocation describes the IP network.
f258f4dd9950a5c71ce2efc127ca69bc0383c10d4fd0c38fd4b3f8fa5781a625Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
104.21.70.20. 9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive