Skip to security report
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
wto-htx.com.cn favicon

wto-htx.com.cn

In short

wto-htx.com.cn is a HTX impersonation page detected by PhishDestroy on 2026-10-26.

“htx信息导航 - 火币htx第三方信息站 · 简体中文网”

Registrar
Dynadot
Resolved IP
104.21.74.141
Registered
Oct 24, 2026
PhishDestroy assessment Critical
80/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Stored blocklist matches: 2 Automated brand label: HTX Scam type: Impersonation Young domain: 2 days old
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
source verdict
Page captures
open gallery
Domain age
Reports sent
view timeline
Oct 26, 2026 1 Report Sent CDN
X Telegram API

Analysis

Domain summary

wto-htx.com.cn is a HTX impersonation page detected by PhishDestroy on 2026-10-26. Risk: critical (80/100). Registrar: Dynadot. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
VirusTotal
0 / 92
Page captures
3

PhishDestroy threat report

Overview

As observed on 2026-10-26, the captured screenshot shows a dark Chinese-language page branded htx火币 that headlines an official-entrance Android package download and package parameters for Huobi HTX, with navigation for installation order, download, registration and FAQs. The page also displayed tiles claiming registered users, tradeable assets, country coverage and 24-hour Chinese-language service. PhishDestroy classified this as impersonation and an impersonation phishing page, first seen by PhishDestroy on 2026-10-26 after a trusted auto intake based on an admin report and AI assessment.

How the scam works

The captured screenshot shows prominent 安卓下载 and 火币注册 buttons next to Android package parameters (v6.92.0, 168MB, Android 6.0 and above), steering visitors toward installing an exchange application obtained outside official channels. As a category risk, such third-party download and registration funnels enable distribution of tampered applications or credential-harvesting sign-up flows while borrowing a real exchange's branding. A top-of-page disclaimer claiming independent third-party status does not remove that install and credential risk.

Evidence

The captured screenshot shows the official-entrance download headline, package parameters, registration buttons and promotional statistics. On 2026-10-26 urlscan flagged it malicious with an ML score of 42 while its overall score was 0; VirusTotal did not flag it; Spamhaus did not list it; Google Safe Browsing did not flag it; OTX recorded 0 pulses. External blocklists MetaMask and SEAL listed the domain and PhishDestroy's internal blocklist flagged it, all checked on 2026-10-26. The HTTP entry funneled to HTTPS with a 307 redirect and no cross-site redirect; site inspection found one tracker request using a Cloudflare beacon and no distinct JavaScript framework, and two separate page SHA256 hashes are recorded for campaign pivoting (04d05978fdb1).

Infrastructure

Hosting is behind Cloudflare with a Cloudflare WAF in front; no registrar identity is recorded. Notable weaknesses: CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, COEP and CORP all absent; HSTS present with max-age 31536000 but not covering all subdomains; no SPF, DKIM or DMARC; CAA present; DNSSEC unsigned; TLS 1.3 with TLS_AES_256_GCM_SHA384, forward secrecy and ALPN h2; the certificate was 2 days old at capture.

What to do

If you submitted account details or installed the package from this page, change your password on the genuine exchange service, enable two-factor authentication, and review the device for unfamiliar installed applications. Do not treat the third-party disclaimer or a valid TLS certificate as proof of legitimacy. Defenders should block wto-htx.com.cn at DNS or proxy layers, watch for further HTX-branded lookalike domains, and retain the recorded capture hashes for pivoting.

Source evidenceVirusTotal 0 / 92 8 sources

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

6b6f6fcf-240c-412d-8f71-5ded1d4a21a8

Final URL

https://wto-htx.com.cn/

HTTP response

200

Navigation history

  • URL
    https://wto-htx.com.cn/
    Status
    200

DOM structure hash

84d6ec43a3964195cc080bde291da13e94d2534f836b7124f6648ea3e02a7d08

Document hash

0bd16aec87a78f9df3ede30987edcea00878cd8d89ea76a825cc91617d3ad51d

Domain risk categories

  • Newly Seen Domains
  • Security Risks

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    wto-htx.com.cn
    Type
    A
    Value
    172.67.158.251
  • Name
    wto-htx.com.cn
    Type
    A
    Value
    104.21.74.141
  • Name
    wto-htx.com.cn
    Type
    AAAA
    Value
    2606:4700:3033::6815:4a8d
  • Name
    wto-htx.com.cn
    Type
    AAAA
    Value
    2606:4700:3036::ac43:9efb

DNSSEC valid

No

IP address

172.67.158.251

Registration record

Registrar
Dynadot Inc
Registered
Expires
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
Original source fields · JSON
Uuid
6b6f6fcf-240c-412d-8f71-5ded1d4a21a8
Final url
https://wto-htx.com.cn/
Status
200
History
[
    {
        "url": "https://wto-htx.com.cn/",
        "status": 200
    }
]
DOM structure hash
84d6ec43a3964195cc080bde291da13e94d2534f836b7124f6648ea3e02a7d08
Document hash
0bd16aec87a78f9df3ede30987edcea00878cd8d89ea76a825cc91617d3ad51d
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "wto-htx.com.cn",
        "type": "A",
        "value": "172.67.158.251"
    },
    {
        "name": "wto-htx.com.cn",
        "type": "A",
        "value": "104.21.74.141"
    },
    {
        "name": "wto-htx.com.cn",
        "type": "AAAA",
        "value": "2606:4700:3033::6815:4a8d"
    },
    {
        "name": "wto-htx.com.cn",
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:9efb"
    }
]
Dnssec valid
false
Ip
172.67.158.251
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-24T11:41:14Z",
    "expires": "2027-10-24T11:41:14Z",
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}

URLScan

Malicious · engine verdict · score 42

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a1780f-b200-707c-8273-92f65e07de2f

Final URL

https://wto-htx.com.cn/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://wto-htx.com.cn/
    From
    http://wto-htx.com.cn/
    Status
    307

IP address

104.21.74.141

Contacted domains

  • static.cloudflareinsights.com

Contacted IP addresses

  • 104.16.79.73
  • 104.21.74.141

Autonomous systems (ASN)

  • 13335

Linked domains

  • www.wto-htx.com.cn

Document hash

04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747

JavaScript globals

  • __cfBeacon

Cookies

  • server_session_7d25baa6

Domain age, days

0

Registered domain age, days

0

Certificate age, days

2

Certificate validity, days

89

Page requests

7

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
42
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Content-type
image/png
Original source fields · JSON
Uuid
01a1780f-b200-707c-8273-92f65e07de2f
Final url
https://wto-htx.com.cn/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://wto-htx.com.cn/",
        "from": "http://wto-htx.com.cn/",
        "status": 307
    }
]
Ip
104.21.74.141
Contacted domains
[
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.79.73",
    "104.21.74.141"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.wto-htx.com.cn"
]
Document hash
04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747
Globals
[
    "__cfBeacon"
]
Cookies
[
    "server_session_7d25baa6"
]
Domain age days
0
Apex age days
0
Tls age days
2
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 42,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "image/png"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a1780f-b200-707c-8273-92f65e07de2f
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
0
Suspicious
0
Undetected
37

Reputation score

0

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    emma.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.74.141
  • TTL, seconds
    21600
    Type
    NS
    Value
    austin.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3033::6815:4a8d
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3036::ac43:9efb
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    austin.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.158.251

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.wto-htx.com.cn
  • wto-htx.com.cn
Issuer
Let's Encrypt / YE2
Serial
683275c65cbf09947aa91b17b107e625fca
SHA-256
b7d39f6c97750432eb31db719bee7857b531cd3f899b12483bc7bb27e3fbd003
Subject
wto-htx.com.cn
Valid until
Valid from

Registration record

Status
  • clientTransferProhibited
Nameservers
  • austin.ns.cloudflare.com
  • emma.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
First seen
2026-10-24T03:52:41Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "emma.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.74.141"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "austin.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::6815:4a8d"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:9efb"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "austin.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.158.251"
    }
]
Dns at
2026-10-26T03:06:16Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.wto-htx.com.cn",
        "wto-htx.com.cn"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "683275c65cbf09947aa91b17b107e625fca",
    "sha256": "b7d39f6c97750432eb31db719bee7857b531cd3f899b12483bc7bb27e3fbd003",
    "subject": "wto-htx.com.cn",
    "valid_to": "2027-01-22T02:50:42Z",
    "valid_from": "2026-10-24T02:50:43Z"
}
Registration record
{
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "austin.ns.cloudflare.com",
        "emma.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-26 02:54:16 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-26T02:54:16Z
fetched_at
2026-10-26T11:56:09Z
stats
{"timeout":0,"harmless":55,"malicious":0,"suspicious":0,"undetected":37}

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-10-26T12:14:28Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-26T12:14:28Z
source_timestamp
2026-10-26 13:14:28
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
wto-htx.com.cn — Huobi HTX Android download impersonation
ai_description
PhishDestroy assesses wto-htx.com.cn as an impersonation phishing page presenting a lookalike Huobi HTX Android app download offer.
ai_generated_at
2026-10-26T20:16:43Z
ai_generated_by
mimo-flash
interpretation
Narrative generation metadata, separate from provider 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
Website checksOriginal source recordRetrieved: 27 fields

Mail configuration

SPF lookups
0

CAA records

Domain
wto-htx.com.cn

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
6557

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://www.wto-htx.com.cn/sitemap.xml

Sitemap

Present
Yes
URL count
1

Page title and metadata

Page title
htx信息导航 - 火币htx第三方信息站 · 简体中文网
Open Graph type
website
Indexing directives
index,follow,max-image-preview:large
Open Graph image
og.svg
Open Graph title
火币htx信息导航站 · 安卓取包参数
Keywords
火币交易所下载
Open Graph site name
火币htx信息导航站
Theme color
#101915
Description
火币交易所下载,打造智能做市系统。通过app下载接入流动性池,AI动态调整价差。实测做市收益较传统策略提升42%,回撤降低60%。
Twitter card
summary_large_image
Canonical URL
https://www.wto-htx.com.cn/index.html
Open Graph description
安全策略的调整经过灰度验证,先在小部分账户生效,观察期内未出现异常再扩大范围,降低误判带来的影响。

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
23
Waiting
607
Connection
7
Download
1
Response time, ms
640

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
15869
CO₂, grams
0.0006
Cleaner than, %
62

DNS servers

Nameservers
  • IP address
    108.162.193.70
    Host
    austin.ns.cloudflare.com
  • IP address
    173.245.58.112
    Host
    emma.ns.cloudflare.com
DNS zone
wto-htx.com.cn

Cookies

Cookies
  • Name
    server_session_7d25baa6
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax

Location

IP address
2606:4700:3036::ac43:9efb
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
wto-htx.com.cn

DNS records

A
  • 172.67.158.251
  • 104.21.74.141
NS
  • emma.ns.cloudflare.com
  • austin.ns.cloudflare.com
SOA
Primary nameserver
austin.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418472480
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3036::ac43:9efb
  • 2606:4700:3033::6815:4a8d

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000
Observation
HSTS header does not include all subdomains.

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
max-age=31536000
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:3033::6815:4a8d
IP version
6

Redirects

Redirect chain
  • https://wto-htx.com.cn

Page links

External link addresses
  • https://www.wto-htx.com.cn/index.html
External links
1
Internal links
7

Registration record

Registrar
Dynadot Inc
Registered
Expires
Status
  • clientTransferProhibited
Nameservers
  • emma.ns.cloudflare.com
  • austin.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "wto-htx.com.cn"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-26T11:56:59Z",
    "first": "2026-10-26T11:56:59Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 6557
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://www.wto-htx.com.cn/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 1
}
Page title and metadata
{
    "title": "htx信息导航 - 火币htx第三方信息站 · 简体中文网",
    "ogType": "website",
    "robots": "index,follow,max-image-preview:large",
    "ogImage": "og.svg",
    "ogTitle": "火币htx信息导航站 · 安卓取包参数",
    "keywords": "火币交易所下载",
    "ogSiteName": "火币htx信息导航站",
    "themeColor": "#101915",
    "description": "火币交易所下载,打造智能做市系统。通过app下载接入流动性池,AI动态调整价差。实测做市收益较传统策略提升42%,回撤降低60%。",
    "twitterCard": "summary_large_image",
    "canonicalUrl": "https://www.wto-htx.com.cn/index.html",
    "ogDescription": "安全策略的调整经过灰度验证,先在小部分账户生效,观察期内未出现异常再扩大范围,降低误判带来的影响。"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 23,
        "wait": 607,
        "connect": 7,
        "download": 1
    },
    "response_ms": 640
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 15869,
    "co2_grams": 0.0006,
    "cleaner_than": 62
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.193.70",
            "host": "austin.ns.cloudflare.com"
        },
        {
            "ip": "173.245.58.112",
            "host": "emma.ns.cloudflare.com"
        }
    ],
    "zone": "wto-htx.com.cn"
}
Cookies
{
    "cookies": [
        {
            "name": "server_session_7d25baa6",
            "secure": true,
            "http_only": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "2606:4700:3036::ac43:9efb",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "wto-htx.com.cn"
}
DNS records
{
    "A": [
        "172.67.158.251",
        "104.21.74.141"
    ],
    "NS": [
        "emma.ns.cloudflare.com",
        "austin.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"austin.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418472480, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3036::ac43:9efb",
        "2606:4700:3033::6815:4a8d"
    ]
}
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
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3033::6815:4a8d",
    "family": 6
}
Redirects
{
    "chain": [
        "https://wto-htx.com.cn"
    ]
}
Page links
{
    "external": [
        "https://www.wto-htx.com.cn/index.html"
    ],
    "external_count": 1,
    "internal_count": 7
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-24T09:41:14Z",
    "expires": "2027-10-24T09:41:14Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "emma.ns.cloudflare.com",
        "austin.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    }
}

Questions about wto-htx.com.cn

Is wto-htx.com.cn legit?

No. PhishDestroy classifies wto-htx.com.cn as a HTX impersonation page (risk: critical, 80/100); it was first detected on 2026-10-26. Treat the site as unsafe.

Is wto-htx.com.cn safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on wto-htx.com.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 wto-htx.com.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 · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 3 captures

All capture links and hashes (3)
wto-htx.com.cn: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 80/100 (critical).
Social preview card wto-htx.com.cn: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 80/100 (critical). v 2bcef264a34a

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Dynadot US(US)
RegistrationCreated Oct 24, 2026 (2d · Brand New!) — Expires Oct 24, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 80/1001 brand signal
Submitted URLhttp://wto-htx.com.cn/
Favicon Hash
Case ID
Observed page title
htx信息导航 - 火币htx第三方信息站 · 简体中文网
Automated brand references
Htx
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.74.141
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • austin.ns.cloudflare.com
  • emma.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-24 02:50:43
Valid until
2027-01-22 02:50:42
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb7d39f6c97750432eb31db719bee7857b531cd3f899b12483bc7bb27e3fbd003
Certificate names · 2 SANs
  • *.wto-htx.com.cn
  • wto-htx.com.cn

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

Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.wto-htx.com.cnDomain record
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of wto-htx.com.cn · checked Oct 26, 2026

98
Good
Performance
FCP
1.52 s
First Contentful Paint
LCP
1.52 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
3.56 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://wto-htx.com.cn/
Final URL: https://wto-htx.com.cn/
htx信息导航 - 火币htx第三方信息站 · 简体中文网
火币交易所下载,打造智能做市系统。通过app下载接入流动性池,AI动态调整价差。实测做市收益较传统策略提升42%,回撤降低60%。
Response
HTTP 200
HTML body
15.9 KB
Compressed
5.2 KB
Links
23 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: 火币htx信息导航站 · 安卓取包参数
Open Graph description: 安全策略的调整经过灰度验证,先在小部分账户生效,观察期内未出现异常再扩大范围,降低误判带来的影响。
Twitter card: summary_large_image
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a509476bfa769698-IAD
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Mon, 26 Oct 2026 11:56:40 GMT
Last-Modified
Sat, 24 Oct 2026 03:55:32 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=tgPK7DV1zGhdqA3BY7etkOH1wz5gJ395a2vJAzeorM%2Fj8nW8WlsE7ts71TUHOV0yTo5fnM0QQPpKJHECnxv%2B%2FZSGsU31EvegiYnk8B96nocBPaGRrRicZnpvVflEHnLhLA%3D%3D"
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

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. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:55:40.000000
    Evidence SHA-256
    f4a7ec839db8b2ffb09fcfcc67b0ed521c49f9c953f6c4a9cc25670fd1e235e4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:55:40
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:55:40.000000
    Evidence SHA-256
    f4a7ec839db8b2ffb09fcfcc67b0ed521c49f9c953f6c4a9cc25670fd1e235e4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:55:40
    Evidence reason

Threat Response Pipeline

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

Recorded events: 11. 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: 1 of 1
  • Threat Ingested
    wto-htx.com.cn detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Blocklist Detection · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 42
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Brand Impersonation
    Automated brand label: HTX
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Dynadot Inc. Abuse contacts: 1.
    • mrc662108@gmail.com
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261026-CDC70E · Receipt 83440

    mrc662108@gmail.com
  2. Wayback Machine

    Page archived

    View source
  3. VirusTotal

    0/92 engine detections

    View source
  4. Added to PhishDestroy

    wto-htx.com.cn

    View source
  5. URLScan

    Page captured

    View source
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.

Check for cloaking

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

wto-htx.com.cn

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261026-CDC70E Recipient: mrc662108@gmail.com
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
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 1 stored notification records Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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.

Official reporting routes

More official reporting routes
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.

Report to Your Local Authorities

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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 wto-htx.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/wto-htx.com.cn"
  title="PhishDestroy threat report for wto-htx.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>