The domain curver.finance was registered on 19 January 2026 through Hostinger Operations, UAB and is currently resolved to the IPv6 address 2a02:4780:84:1485:354a:ef59:48db:de97, which is assigned to AS47583 Hostinger International Limited in Lithuania. The domain’s nameservers are ns1.dns-parking.com and ns2.dns-parking.com, a configuration typically associated with parked or inactive sites. As of the report date (24 July 2026) the site is offline, preventing live content inspection. However, the page title that was observed prior to takedown reads “Swap - Curve”, directly referencing the Curve DeFi platform. The threat profile classifies the site as a wallet/seed phishing operation that impersonates Curve, aiming to harvest private keys or recovery phrases from unsuspecting users.
Security telemetry shows that 16 of 95 VirusTotal scanners flagged the domain, indicating a moderate-to-high level of malicious detection across independent engines. The site lacks an SSL/TLS certificate, meaning any HTTP connections would be unencrypted and vulnerable to interception. The Gridinsoft trust score is 0 / 100, reinforcing the assessment of a low‑trust entity. Google Safe Browsing has flagged the URL for social engineering, and the domain appears on three external blocklists, including PhishDestroy, MetaMask, and SEAL.
These blocklists have already taken action to prevent access from wallets and browsers that support crypto interactions. Given the evidence, analysts should treat curver.finance as a high‑risk impersonation vector. Defensive measures include adding the domain to internal DNS and URL filtering rules, monitoring the associated IP range and registrar for future registrations, and alerting users of Curve to never disclose seed phrases or private keys to unsolicited “Swap” interfaces. Continuous watch‑listing of Hostinger‑registered domains that resolve to the same IPv6 subnet can help pre‑empt re‑deployment of similar phishing infrastructure.
Extracted from stored page analysis
Observed indicators
2 wallet · 4 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年3月24日score 15/1004 brand signals
IoC Extractionscanned 2026年8月2日2 wallet · 4 Telegram IoCs
Submitted URLhttp://curver.finance/
ケース ID
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-19 01:08:21 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-04-21 22:27:32 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-21 22:27:32 UTC → 2026-09-30 16:14:55 UTC · 3,881.79hmidpoint estimate ≈ 2026-07-11 19:21:13 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.
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='curver.finance', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
curver.finance
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
詐欺による金銭の返還を装った詐欺 — 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.
(LT)
