PhishDestroy is currently investigating hyperliquid.services for potential brand impersonation. This domain poses a risk to users of Hyperliquid, as it may be used in phishing campaigns to steal credentials or private keys. The domain's 'under_investigation' status signals an elevated risk that requires user vigilance.
Our analysis reveals several key data points. The domain, created on August 06, 2025, resolves to IP address 35.214.240.206. The SSL certificate is issued by Let's Encrypt. hyperliquid.services is registered through Web Commerce Communications Limited dba WebNic.cc. As of the latest scan, VirusTotal shows a score of 0/95, meaning it hasn't been widely flagged as malicious yet. This low detection rate does not guarantee safety, especially given the recent domain creation date and the potential for targeted attacks.
Users should exercise extreme caution when interacting with hyperliquid.services or any communication claiming to be from Hyperliquid. Always verify the authenticity of websites and communications through official Hyperliquid channels. Do not enter sensitive information such as passwords or private keys on the site without independent verification. Report any suspicious activity to Hyperliquid's official support channels and PhishDestroy immediately.
Detection-evasion evidence
Cloaking confirmed: scanners and visitors see different content
ObservedDifferent content was served to scanners and to visitors
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
Stored cloaking flag
Observed
Cloaking type
content_divergence
Cloaking score
1/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='hyperliquid.services', port=80): Max retries exceeded with url: / (Caused by NewConnection
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='hyperliquid.services', port=80): Max retries exceeded with url: / (Caused by NewConnection
checked Oct 11, 2026
Time to First Unavailability30 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedMar 28, 2026
DOM Analysisanalyzed Jul 29, 2026score 70/1001 brand signal
Submitted URLhttps://hyperliquid.services/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:14:40 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-15 22:17:59 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:59 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:27 UTC · precision 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.
Technologies · 1 identified
N
Nginx
Web serversReverse proxies
High-performance HTTP server and reverse proxy, known for stability and low resource usage.
Last analyzed First positive detection Previous stored snapshot: 1 detection
Gridinsoft
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of hyperliquid.services· checked Mar 28, 2026
92
Good
Performance
FCP
2.57s
First Contentful Paint
LCP
2.76s
Largest Contentful Paint
CLS
0.024
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.57s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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
hyperliquid.services detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Apr 27, 2026
Time to First Unavailability
727 hours elapsed from detection to the first unavailable 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+
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (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.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
5 evidence signal groups linked1 reports recordedContent unavailable
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.
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 →
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · hyperliquid.services
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Report 
