VirusTotal
11 / 91 engine detections
レポートを開く“web3”
フィッシング: web3backup.online — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 11/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET); PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 91 engine detections
レポートを開く3 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis of www.web3backup.online shows a domain registered on October 03, 2025 through Hosting Concepts B.V. d/b/a Registrar.eu. The authoritative nameservers are ns1.openprovider.nl, ns2.openprovider.be, and ns3.openprovider.eu, indicating the use of OpenProvider services for DNS. DNS resolution points to IP address 35.204.150.5, which is assigned to Google LLC (AS396982) and geolocated to the Netherlands. The site presented an SSL certificate issued to Webador / by.webador.com, suggesting the use of a low‑cost web‑hosting or site‑builder platform.
An HTTP request returns a 404 status code, and the page title retrieved is simply "web3"; no further content was captured before the domain was taken offline. The domain appears on one security blocklist and is listed as blocked by PhishDestroy. VirusTotal scans recorded four detections out of ninety‑five security vendors, confirming that multiple scanners flag the domain as malicious. The threat classification in the intelligence set is a crypto scam, aligning with the "web3" title and the observed phishing behavior.
While the offline status prevents direct observation of phishing payloads or credential‑harvesting forms, the combination of recent registration, use of reputable hosting infrastructure, a valid TLS certificate, and multiple vendor detections indicates a deliberate attempt to exploit cryptocurrency‑related interest. Defenders should continue to monitor the IP address 35.204.150.5 for any future malicious activity, enforce blocklist updates that include this domain, and consider applying sink‑hole or DNS‑filtering rules for the associated OpenProvider nameservers. Additional scrutiny of any traffic matching the domain's TLS fingerprint or HTTP 404 response pattern is advisable, as threat actors may reactivate the domain or replicate the infrastructure under a new label.
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.
ns1.openprovider.nlns2.openprovider.bens3.openprovider.euLocation describes the IP network.
b233ba37ab33bc2f8e12b335d21a419e5a38f8826e034e1de6b3afba974b430dSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
alive_content: raw=ok; http=200; via=https_proxy; server=openresty
web3backup.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→inactive
hosting_placeholder · placeholder_page
不明→inactive
hosting_placeholder · placeholder_page
No threat flag
View source3 community references
View source11/91 engine detections
View sourcePage captured
View sourceweb3backup.online
View sourceコミュニティの 1 人が報告・初回確認 2025年11月22日
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
web3backup.online)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.