VirusTotal
6 / 94 engine detections
レポートを開く“X Token”
暗号資産投資詐欺: xweb3.network — コンテンツが利用できません. 証拠の概要: VirusTotal 6/94 (ADMINUSLabs, alphaMountain.ai, Fortinet, Gridinsoft, Seclookup); PhishDestroy score 70/100.…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 94 engine detections
レポートを開くSuspicious
レポートを開くchecked — no detections recorded
レポートを開くchecked — no match recorded
no community references
レポートを開く14 確認済み — ブロックなし
No threat flag
レポートを開くPage capture
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
On 24 July 2026 analysts observed the domain xweb3.network being taken offline after detection as an elevated‑risk investment‑scam phishing site. The domain was registered on 22 March 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and is hosted on Cloudflare infrastructure, resolving to IP 188.114.96.3, which is geo‑located to Canada and served by Cloudflare, Inc. The authoritative nameservers are phil.ns.cloudflare.com and sandra.ns.cloudflare.com. No TLS certificate was presented, indicating the site operated over plain HTTP. Passive scanning identified the page title “X Token”, and fingerprinting tools detected the presence of Smartsupp live‑chat, Cloudflare Browser Insights, and HTTP/3 support, all consistent with a typical Cloudflare‑protected deployment.
Reputation checks show the domain appears on three independent security blocklists and has been blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal recorded six detections out of ninety‑four submitted scanners, confirming malicious classification by a subset of vendors. The Gridinsoft trust score is 0 out of 100, reinforcing the low credibility assessment. The site was categorized as an investment scam, targeting users with promises related to the “X Token” concept.
While the offline status prevents active probing, the lack of an SSL certificate, the recent creation date, and the low trust score suggest a short‑lived malicious campaign. Uncertainty remains regarding the exact payload delivered to victims, as no sample URLs or malicious scripts have been disclosed. Defenders should continue to block the domain at network perimeter and DNS layers, monitor for any resurgence of the same IP address or Cloudflare nameserver pair, and update endpoint detection rules to flag the identified Smartsupp and Cloudflare Browser Insights signatures. Ongoing collection of any malicious payloads or phishing emails referencing “X Token” will be required to refine detection and response capabilities.
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 の評判はこのドメインに起因しません。
sandra.ns.cloudflare.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of xweb3.network · checked Mar 21, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='xweb3.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
xweb3.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
6/94 engine detections
View sourceNo threat flag
View sourcexweb3.network
View sourcePD-20260321-AAC2BB
保存された類似ドメイン:52 件
コミュニティの 1 人が報告・初回確認 2026年3月21日
PD-20260321-AAC2BB Recipient: abuse@publicdomainregistry.com Registrar: PublicDomainRegistry (PDR Ltd.) (India) Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
xweb3.network)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.