This domain, www.web3ai-defi.net, is flagged as a crypto drainer with an elevated risk rating. The site presents the page title “Web3 DeFi AI”, which aligns with the classified scam type of Crypto Scam. VirusTotal analysis shows that 9 of 95 security vendors have flagged the domain, indicating a non‑trivial detection consensus. The domain lacks an SSL certificate, exposing any transmitted data to interception. Registration records reveal that the domain was created on 25 October 2025 through Gname.com Pte. Ltd., and it is delegated to the Cloudflare nameservers blair.ns.cloudflare.com and scott.ns.cloudflare.com.
DNS resolution points to IP 172.67.194.111, an address owned by Cloudflare, Inc. (AS13335) and geolocated to the United States. The hosting provider’s reputation is reflected in a Gridinsoft trust score of 0 out of 100, and the domain is listed on a single security blocklist. PhishDestroy has also blocked the domain, and the current operational status is reported as offline. Evidence confirms the presence of a malicious infrastructure but lacks detailed payload or victim information. The page content beyond the title has not been publicly analyzed, so the exact mechanisms used to drain cryptocurrency remain uncertain.
Defenders should treat any DNS or HTTP traffic to www.web3ai-defi.net as hostile. Immediate actions include adding the domain to network deny‑lists, blocking the associated IP address, and monitoring for look‑alike subdomains that use the same Cloudflare nameservers. Continuous re‑inspection of the IP reputation and periodic VirusTotal rescans are advised to capture any changes in vendor detections. Given the elevated risk and the confirmed involvement of known security blocklists, proactive containment is recommended.
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.
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='duplicate-disabled-20232.invalid', port=80): Max retries exceeded with url: / (Caused by N
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.
(SG)
