Analysis of hyperliquid-claim.online indicates a crypto-themed phishing domain impersonating Hyperliquid, a decentralized exchange. The domain was registered on September 16, 2025, through HOSTINGER operations, UAB, and resolved to IP 82.25.113.137, hosted on AS47583 (Hostinger International Limited, FR). No SSL certificate was present, and nameservers were set to ns1.dns-parking.com and ns2.dns-parking.com. The page title, 'Bot Verification,' aligns with known airdrop scam patterns, where victims are prompted to complete fraudulent verification steps to claim non-existent crypto rewards.
Infrastructure review shows the domain was taken offline prior to July 24, 2026, though its prior activity remains under investigation. It appeared on one security blocklist (PhishDestroy) and was classified as an airdrop scam. Gridinsoft assigned a trust score of 0/100, reflecting high suspicion. While VirusTotal scans by 95 vendors returned no active detections, this absence does not confirm safety.
The domain’s registration details, hosting provider, and scam classification suggest targeted abuse of Hyperliquid’s branding to deceive users. Defenders should treat hyperliquid-claim.online as malicious and prioritize blocking the domain and its resolving IP. Monitoring for similar domains using the same registrar, nameservers, or hosting infrastructure may help identify related threats. Further forensic analysis is recommended if logs indicate user interaction with this domain.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='hyperliquid-claim.online', port=80): Max retries exceeded with url: / (Caused by NewConnec
DOM Analysisanalyzed 2026年4月23日score 48/1001 brand signal
Submitted URLhttps://hyperliquid-claim.online/
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:09:46 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-17 16:28:52 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 16:28:52 UTC → 2026-09-30 16:14:55 UTC · 2,519.77hmidpoint estimate ≈ 2026-08-09 04:21:53 UTC · precision very low · basis bounded
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.
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.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Brand Impersonation
Impersonation of Hyperliquid
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
(LT)
