VirusTotal
9 / 91
“Even geduld...”
Analysis of the domain www-curve.finance, created on February 21 2026, shows a high‑risk brand‑impersonation infrastructure targeting the Curve brand. The site resolves to IP address 188.114.96.3, which belongs to AS13335 Cloudflare, Inc. and is geolocated in the United States. DNS resolution is handled by the Cloudflare authoritative nameservers mark.ns.cloudflare.com and uma.ns.cloudflare.com, indicating the use of Cloudflare’s edge network for traffic forwarding and protection. The SSL certificate presented by the server is issued by Google Trust Services under the WE1 intermediate, confirming that TLS termination is performed by Cloudflare’s managed certificate service.
An HTTP request returns a 403 status code, and the page title observed is "Even geduld...", providing no further functional context. Detected technologies include HTTP/3, HSTS enforcement, Cloudflare Browser Insights, and the Cloudflare CDN itself. Threat intelligence feeds have flagged the domain on a single blocklist (PhishDestroy) and four of ninety‑three VirusTotal security vendors have marked it as malicious, reinforcing the suspicion of abuse. The registrar listed is NiceNIC International Group Co., Limited, a known provider for many short‑lived malicious domains.
The site is classified as a crypto‑scam, suggesting attempts to lure victims into fraudulent cryptocurrency transactions while masquerading as Curve‑related services. While the exact payload or credential‑stealing mechanisms have not been observed, the combination of brand impersonation, Cloudflare‑hosted infrastructure, a non‑standard HTTP response, and multiple vendor detections indicate an active malicious operation. Defenders should block the domain at perimeter firewalls and DNS resolvers, monitor outbound connections to the associated IP, and add the domain to internal blocklists.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
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 reputation is not attributed to this domain.
uma.ns.cloudflare.comLocation describes the IP network.
027a564fba62ef6ef24b399fe109697fff0633dab94b8cc534b28596aa80967fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
15 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.
9 stored lookalike domains
Reported by 1 community member, first seen Feb 12, 2026
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive