VirusTotal
5 / 92 engine detections
レポートを開く“Zest Protocol | The Bitcoin liquidity protocol”
Bitcoinなりすまし: sitemv4c57e5h81k.cfd — 未検証. 証拠の概要: VirusTotal 5/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar, VIPRE); 3 external blocklist…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 92 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開く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
sitemv4c57e5h81k.cfd is an impersonation phishing page that presents itself as "Zest Protocol | The Bitcoin liquidity protocol". It targets Bitcoin holders who are looking for yield or lending in Bitcoin DeFi and want the real Zest service. PhishDestroy first flagged it on 2026-10-13. As of 2026-10-19 the domain still responded, but DNS for its content was inactive, so the phishing page itself was no longer resolving.
The page borrows the name and tagline of a Bitcoin liquidity protocol so that visitors arriving from search ads, social posts or direct messages believe they are on the genuine app. Fake DeFi front ends like this usually ask the visitor to connect a wallet and then present transaction or signature requests dressed up as deposits, claims or account verification. Some ask outright for a recovery phrase to "restore" access. Approving those prompts or typing the seed phrase hands control of the funds to the operators, and transfers made on-chain are practically impossible to reverse.
On 2026-10-16, five of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar and VIPRE. That is a low count, which is common for throwaway domains in their first days. The stronger signal comes from crypto-specific blocklists. Besides PhishDestroy, the domain is listed by MetaMask, ScamSniffer and SEAL, so wallet users relying on those protections should already see a warning.
The domain was registered on 2026-10-11 through Spaceship, Inc., two days before PhishDestroy caught it. That short gap fits a disposable campaign domain on a cheap .cfd extension with a random-looking name. Traffic runs through Cloudflare (AS13335, US), which hides the real origin server. The Let's Encrypt certificate gives the site a padlock, but the padlock only means the connection is encrypted and says nothing about who runs the site.
If you connected a wallet here, open a token-approval checker for that wallet and revoke any permissions you do not recognize. If you entered a recovery phrase, treat the wallet as compromised and move any remaining assets to a new wallet with a freshly generated seed. Reach Zest Protocol only through links you have verified yourself, never through ads or messages. Defenders should block the domain at DNS and proxy level, search their logs for visits since 2026-10-11, and report it to Cloudflare and Spaceship for takedown.
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 の評判はこのドメインに起因しません。
walt.ns.cloudflare.comLocation describes the IP network.
b2655ac740d71784c369173e01975bd1e2524119246cbc3d3510bd16f6c0894cSaved 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 sitemv4c57e5h81k.cfd · checked Oct 13, 2026
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
live_content→dns_inactive
dns_nxdomain
不明→live_content
content_served
No threat flag
View source5/92 engine detections
View sourcesitemv4c57e5h81k.cfd
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
sitemv4c57e5h81k.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 ↗
sitemv4c57e5h81k.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.