This domain, claim.hyperlnaene.foundation, was observed hosting a page titled “Hyperlane – Token claim” and is attributed to a crypto‑scam campaign that pretends to be associated with Binance. The domain was registered on 21 February 2026 and is currently taken offline. DNS resolution points to 104.21.16.1, an address owned by Cloudflare (AS13335) located in the United States. The SSL certificate presented is identified as “WE1”, which does not correspond to a trusted certificate authority.
Reputation scoring from Gridinsoft assigns a zero‑point trust rating (0/100). Independent blocklists, including PhishDestroy and ScamSniffer, have listed the domain, and it appears on two additional security blocklists. VirusTotal analysis shows that 7 of 93 scanning engines flagged the domain as malicious, reinforcing the suspicion of phishing activity. The site is classified as a “Crypto Scam” and explicitly impersonates the Binance brand.
Available evidence confirms the domain’s creation date, hosting details, SSL fingerprint, and blocklist presence, but the content of the page beyond the title has not been captured, leaving the exact phishing mechanics unknown. No public WHOIS anomalies or registrar information are provided, and no further infrastructure such as command‑and‑control endpoints has been identified. Defenders should block any network traffic to claim.hyperlnaene.foundation, add the IP 104.21.16.1 to deny‑list rules where feasible, and monitor for similar Cloudflare‑hosted domains that use the “WE1” certificate pattern. Security teams should also update brand‑protection feeds for Binance to include this indicator and continue to consult threat‑intel platforms for any emerging variants that reuse the same page title or host under the same ASN.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-19 01:15:36 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:52 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:52 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:23 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.
Last analyzed Previous stored snapshot: 11 detections
BitDefender
Chong Lua Dao
CRDF
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Lionic
Sophos
VIPRE
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
353.95
Estimate basis
Bounded by observations
Estimate precision
Low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='claim.hyperlnaene.foundation', port=80): Max retries exceeded with url: / (Caused by NewCo
claim.hyperlnaene.foundation
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
我应该立即采取什么措施？
紧急
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
