Skip to security report
Domain security and threat intelligence
okex-web.hl.cn favicon

okex-web.hl.cn

In short

okex-web.hl.cn is an OKX impersonation page detected by PhishDestroy on 2026-10-23. Risk: critical (95/100). Registrar: 万商云集(成都)科技股份有限公司. Status: Last known active. Hosting: OWGELS INTERNATIONAL CO., LIMITED. PhishDestroy sent 1 abuse report. VirusTotal: 4/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“恭喜,站点创建成功!”

Registrar
万商云集(成都)科技股份有限公司
Resolved IP
82.41.66.136
Registered
Oct 12, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 4/92 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: OKX Young domain: 11 days old
Oct 23, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 4 / 92 7 sources

VirusTotal

4 / 92 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
4 / 92
Page captures
6

PhishDestroy threat report

Overview

PhishDestroy listed okex-web.hl.cn as a suspicious domain. The recorded page title was “恭喜,站点创建成功!” (Congratulations, site created successfully!). The domain was first seen by PhishDestroy on 2026-10-23.

How the scam works

A suspicious domain can be used to imitate legitimate services, host deceptive content, or attempt credential collection. No specific malicious flow or credential‑harvesting form was observed on the captured page. The classification reflects the risk indicated by external detections rather than confirmed behavior.

Evidence

VirusTotal reported four malicious detections on 2026-10-23 from alphaMountain.ai, Fortinet, LevelBlue and Webroot. Google Safe Browsing checked on 2026-10-23 and returned no flag. urlscan.io captured the site on 2026-10-13; its engine score was 95 (malicious) but the overall verdict was clean. OTX listed zero pulses as of 2026-10-23. PhishDestroy’s internal blocklist marked the domain as suspicious on 2026-10-22, while external blocklists showed no entries on 2026-10-22.

Infrastructure

The recorded IP was 82.41.66.136, which belongs to OWGELS INTERNATIONAL CO., LIMITED in Hong Kong. DNS records observed on 2026-10-19 listed ns1.kenpains.com and ns2.kenpains.com as authoritative name servers. The TLS certificate seen on 2026-10-12 was issued by TrustAsia Technologies, Inc. and was valid until 2027-01-10. The domain age was recorded as zero days at the time of observation.

What to do

Do not submit any credentials or personal information to the site; if you have already done so, change passwords on the affected service immediately. Security teams should block the exact domain and monitor outbound traffic to 82.41.66.136 for suspicious activity. Review access logs for any requests to this host and apply standard phishing‑mitigation policies.

Collected source details

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

URLScan · 2026-10-23T02:24:30Z

Observed: · Retrieved:

Uuid
01a16692-e129-7767-9856-a8953c94e0f4
Final url
https://okex-web.hl.cn/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://okex-web.hl.cn/",
        "from": "http://okex-web.hl.cn/",
        "status": 307
    }
]
Ip
82.41.66.136
Contacted IP addresses
[
    "82.41.66.136"
]
Asns
[
    "153656"
]
Countries
[
    "HK"
]
Document hash
3b319a1e7740a5e3a99f2b9dd8fcf137f0f32773eb44100b012db3196cc6ae5c
Tls
{
    "san": [
        "okex-web.hl.cn"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "LiteSSL RSA CA 2025",
    "subject": "okex-web.hl.cn",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-10T04:59:59Z",
    "valid_from": "2026-10-12T05:00:00Z"
}
Domain age days
9
Apex age days
9
Tls age days
10
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "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-23T02:02:57Z

Observed: · Retrieved:

Uuid
4198863f-2861-4611-a3c5-77496a97c4a5
Final url
https://okex-web.hl.cn/
Status
200
History
[
    {
        "url": "https://okex-web.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": "okex-web.hl.cn",
        "type": "A",
        "value": "82.41.66.136"
    }
]
Dnssec valid
false
Ip
82.41.66.136
Registration record
{
    "registrar": "万商云集(成都)科技股份有限公司",
    "created": "2026-10-12T13:33:47Z",
    "expires": "2027-10-12T13:33:47Z",
    "nameservers": [
        "ns1.kenpains.com",
        "ns2.kenpains.com"
    ]
}
VirusTotal · 2026-10-19T01:14:57Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 39
}
Vendor labels
{
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "LevelBlue": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
First seen
2026-10-12T16:26:10Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.kenpains.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.kenpains.com"
    },
    {
        "ttl": 600,
        "type": "SOA",
        "rname": "admin.kenpains.com",
        "value": "ns1.kenpains.com"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "82.41.66.136"
    }
]
Dns at
2026-10-19T01:20:20Z
Jarm
3fd3fd0003fd3fd21c42d42d000000bdfc58c9a46434368cf60aa440385763
Certificate
{
    "san": [
        "okex-web.hl.cn"
    ],
    "issuer": "TrustAsia Technologies, Inc. / LiteSSL RSA CA 2025",
    "serial": "4fb8e8a2d1c4a4626945cff695799d4aa5beeb53",
    "sha256": "ced3cb7e57e9564096733cd89ac3f8d98d9f7d92aacf384a3c279d67d8d1daa8",
    "subject": "okex-web.hl.cn",
    "valid_to": "2027-01-10T04:59:59Z",
    "valid_from": "2026-10-12T05:00:00Z"
}
Registration record
{
    "status": [
        "ok"
    ],
    "nameservers": [
        "ns1.kenpains.com",
        "ns2.kenpains.com"
    ],
    "dnssec": "unsigned"
}
Website checks · 2026-10-23T02:07:33Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "okex-web.hl.cn"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-23T01:52:44Z",
    "first": "2026-10-12T08:54:20Z",
    "changes": 0,
    "days_archived": 2,
    "scans_per_day": 0.09,
    "avg_page_bytes": 872
}
Page title and metadata
{
    "title": "恭喜,站点创建成功!"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 912,
        "tls": 187,
        "wait": 184,
        "connect": 183,
        "download": 0
    },
    "response_ms": 1466
}
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
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 917,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "183.253.57.217",
            "host": "ns1.kenpains.com"
        },
        {
            "ip": "1.193.216.197",
            "host": "ns2.kenpains.com"
        }
    ],
    "zone": "okex-web.hl.cn"
}
Location
{
    "ip": "82.41.66.136",
    "asn": "153656",
    "org": "OWGELS INTERNATIONAL CO., LIMITED",
    "city": "Hong Kong",
    "country": "HK"
}
Ssl
{
    "issuer": "TrustAsia Technologies, Inc. / LiteSSL RSA CA 2025",
    "subject": "okex-web.hl.cn"
}
DNS records
{
    "A": [
        "82.41.66.136"
    ],
    "NS": [
        "ns2.kenpains.com",
        "ns1.kenpains.com"
    ],
    "SOA": "{\"nsname\": \"ns1.kenpains.com\", \"hostmaster\": \"admin.kenpains.com\", \"serial\": 1791870020, \"refresh\": 3600, \"retry\": 300, \"expire\": 1209600, \"minttl\": 1800}"
}
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": "82.41.66.136",
    "family": 4
}
Redirects
{
    "chain": [
        "https://okex-web.hl.cn"
    ]
}
Tech stack
{
    "technologies": [
        "Nginx",
        "HSTS"
    ]
}
Registration record
{
    "registrar": "万商云集(成都)科技股份有限公司",
    "created": "2026-10-12T11:33:47Z",
    "expires": "2027-10-12T11:33:47Z",
    "status": [
        "ok"
    ],
    "nameservers": [
        "ns1.kenpains.com",
        "ns2.kenpains.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    }
}

Questions about okex-web.hl.cn

Is okex-web.hl.cn legit?

No. PhishDestroy classifies okex-web.hl.cn as an OKX impersonation page (risk: critical, 95/100); it was first detected on 2026-10-23. VirusTotal: 4/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is okex-web.hl.cn safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on okex-web.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 okex-web.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 · 6 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 23, 2026
Registrar 万商云集(成都)科技股份有限公司
RegistrationCreated Oct 12, 2026 (11d · Very New!) — Expires Oct 12, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 83/100
Submitted URLhttp://okex-web.hl.cn/
Favicon Hash
Case ID
Observed page title
恭喜,站点创建成功!
TLS Certificate
Issued by TrustAsia Technologies, Inc. / LiteSSL RSA CA 2025 · stored validity ends in 78 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
82.41.66.136
Network ASN
AS153656
Organization
OWGELS INTERNATIONAL CO., LIMITED
Observed location
Hong Kong, HK
Server header
nginx

Nameservers 2

  • ns1.kenpains.com
  • ns2.kenpains.com

Location describes the IP network.

TLS certificate

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

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

Latest Classified Outcome 2026-10-23 10:36:03 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-23 10:36:03 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 10:36:03 UTC last content: 2026-10-23 10:36:03 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.
Recorded subdomains1

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

  • cn.okex-web.hl.cnDomain record

The original observation time is not recorded for these hostnames.

Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
Fortinet
LevelBlue
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of okex-web.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
1.91s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

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 · Recorded state

    Unknown→live_content

    content_served

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261023-9B60AF

    johnbergeson41@outlook.com
  2. URLScan

    Page captured

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. VirusTotal

    4/92 engine detections

    View source
  5. Added to PhishDestroy

    okex-web.hl.cn

    View source

Lookalike domains

89 stored lookalike domains

0kx.com homoglyph 0okx.com insertion 9kx.com replacement 9okx.com insertion akx.com vowel-swap ekx.com vowel-swap gkx.com bitsquatting ikx.com replacement iokx.com insertion kkx.com bitsquatting kokx.com insertion kox.com transposition
Show all (77)
kx.com omission lkx.com replacement lokx.com insertion mkx.com bitsquatting nkx.com bitsquatting o0kx.com insertion ocx.com bitsquatting oicx.com homoglyph oikx.com insertion oix.com bitsquatting ojkx.com insertion ojx.com bitsquatting ok-x.com hyphenation ok.com omission ok8.com bitsquatting okc.com replacement okd.com replacement okh.com bitsquatting okix.com insertion okjx.com insertion okkx.com insertion oklx.com insertion okmx.com insertion okox.com insertion okp.com bitsquatting oks.com replacement okw.com replacement okx0.com addition okx4.com addition okx5.com addition okxcom.com various okxj.com addition okxr.com addition oky.com bitsquatting okz.com bitsquatting olcx.com homoglyph olex.com homoglyph olkx.com insertion olx.com replacement omkx.com insertion omx.com replacement oox.com bitsquatting opkx.com insertion ox.com omission oxk.com transposition pkx.com replacement ukx.com vowel-swap xn--j1ahw.com cyrillic xn--kx-4ja.com homoglyph okx1.com addition okx2.com addition okx3.com addition okx6.com addition okx8.com addition okx9.com addition okxa.com addition okxb.com addition okxc.com addition okxd.com addition okxf.com addition okxg.com addition okxh.com addition okxi.com addition okxk.com addition okxl.com addition okxm.com addition okxn.com addition okxo.com addition okxp.com addition okxq.com addition okxs.com addition okxt.com addition okxv.com addition okxw.com addition okxx.com addition okxy.com addition okxz.com addition

Check for cloaking

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

okex-web.hl.cn

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-9B60AF Recipient: johnbergeson41@outlook.com
Page title stored with report: 恭喜,站点创建成功!
PDF notice generated
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.

Official reporting routes

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 okex-web.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

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.

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/okex-web.hl.cn"
  title="PhishDestroy threat report for okex-web.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>