VirusTotal
5 / 89
BildirInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Hyperliquid”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
hyperliquidfoundation.xyz — Ulaşılabilir · erişim kısıtlı (HTTP 403). Marka kimliğine bürünme: Hyperliquid; Dolandırıcılık türü: Impersonation. Kanıt özeti: VirusTotal 5/89 (alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, SOCRadar); URLQuery 1 alert; PhishDestroy score 76/100. Kayıt kuruluşu: DYNADOT.
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
5 / 89
BildirEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
1 threat-system alert
BildirAlerts refer to the preserved scan. They do not describe the current state of the site.
1 community reference
BildirCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
saklanan rapor
Bildir A preserved page image documents what the collector received; a capture is not a safety verdict.
Analiz tamamlandı
BildirThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
BildirA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | app.hyperliquid-testnet.xyz |
malicious | Sinkholed |
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-01, hyperliquidfoundation.xyz returned an HTTP 403 response during an HTTP check. The domain was first observed on 2026-09-14, and its registration date is recorded as 2026-08-07.
The domain was first observed on 2026-09-14, the same date as an OTX check that recorded 1 pulse and an SSL scan naming Google Trust Services / WE1 as the certificate issuer. VirusTotal, checked on 2026-09-16, reported 5 detections across 89 scanners. The HTTP check on 2026-10-01 recorded status 403, and the domain appears in the PhishDestroy internal listing. The registrar is recorded as DYNADOT LLC, with registration on 2026-08-07, and the resolved IP 188.114.97.3 is associated with Cloudflare, Inc. in CA.
The OTX pulse count, VirusTotal detection ratio, and PhishDestroy listing are separate source records with different collection dates, so they should be read as distinct observations rather than a combined score. The first observation on 2026-09-14 and the HTTP check on 2026-10-01 bracket a period in which the recorded response was 403, but the dates alone do not establish what changed. The 403 response describes only the recorded request outcome, not all content that may exist on the domain.
Preserve the OTX record, the VirusTotal result, and the PhishDestroy listing for hyperliquidfoundation.xyz as separate dated references. Compare the HTTP response record against the first-observation record before drawing conclusions about the domain. Re-check hyperliquidfoundation.xyz and retain each new source record alongside the existing ones.
Bu ana bilgisayar için saklanmış tarayıcı-karşı-tarayıcı gözlemleri ile Keitaro tarzı trafik dağıtım sistemleri için gerçek zamanlı parmak izi kontrolü.
cloudflareTarayıcı notu: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Tarama Sırasında Sağlayıcının Yanıtı: cloudflare_phishing_interstitial
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.
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.
Edge-IP itibarı bu etki alanıyla ilişkilendirilmez.
jo.ns.cloudflare.comlex.ns.cloudflare.comLocation describes the IP network.
02407c05dee82fdc988663fbf29c93ddf9dbe93cbc291fd89f54da7592176647Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
172.67.136.186.13 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.
PD-20260914-D2BF14 Recipient: abuse@dynadot.com 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
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
Template-based draft · optional AI wording assistance requires separate consent
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin