VirusTotal
0 / 92 engine detections
レポートを開く“genesis-flarenetwork.cfd”
ブロックリスト掲載ドメイン: genesis-flarenetwork.cfd — 未検証. 証拠の概要: VirusTotal 0/92; 3 external blocklist matches (MetaMask, ScamSniffer, SEAL); PhishDestroy score 75/100.…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
0 / 92 engine detections
レポートを開く2 community references
レポートを開くScan report
レポートを開く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
genesis-flarenetwork.cfd is on the PhishDestroy blocklist. Its name pairs "genesis" with "flarenetwork", which echoes the Flare Network blockchain project, but nothing ties it to that project. PhishDestroy first saw it on 2026-10-07, the same day it was registered. As of 2026-10-19 its DNS no longer resolves, so the site is effectively offline, though it could come back on the same or a new address.
The page title is just the domain name, so it shows no brand, product or lure. The risk comes from the name and from who flagged it. A "genesis" label beside a blockchain project's name is a common pattern for pages that promise a launch, airdrop or claim to holders of that ecosystem's tokens. Three of the blocklists that list this domain are run by wallet-security teams, which points to a threat aimed at crypto wallet users. With such a page, the danger is connecting a wallet, signing what the site asks for, or typing in a recovery phrase.
VirusTotal showed 0 detections out of 92 engines on 2026-10-07, the day the domain was registered. That says little about safety. Brand-new domains are often missed by general antivirus engines in their first hours. The stronger signal is from crypto-focused sources: besides PhishDestroy, the domain appears on the MetaMask, ScamSniffer and SEAL blocklists. It is also referenced in 2 AlienVault OTX threat-intelligence pulses.
The domain was registered through Spaceship, Inc. on 2026-10-07 and was on PhishDestroy's radar that same day. That points to a short-lived setup rather than an established service. It uses the low-cost .cfd extension and sits behind Cloudflare (AS13335) at 172.67.188.106 in the US. Because of that proxy, the address shown does not reveal the real origin server.
If you opened this site and connected a wallet, check that wallet's token approvals and revoke any you granted around 2026-10-07 or later. Move funds to a fresh wallet if you signed anything you did not fully understand. If you entered a seed phrase or private key, treat the wallet as compromised and transfer assets to a new one created on a clean device right away. Only use Flare-related links from the project's official channels. Defenders should block the domain at DNS and proxy level and watch for similar names that pair "genesis" with ecosystem brands on cheap TLDs.
Last checked
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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 の評判はこのドメインに起因しません。
Location describes the IP network.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
2 community references
View sourceNo threat flag
View source0/92 engine detections
View sourcegenesis-flarenetwork.cfd
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
genesis-flarenetwork.cfd
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 ↗
genesis-flarenetwork.cfd)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.