VirusTotal
9 / 92 engine detections
فتح التقرير“Zest Protocol | The Bitcoin liquidity protocol”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 13 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
انتحال Sei: zestprotocol.forum — لم يتم التحقق منها. ملخص الأدلة: VirusTotal 9/92 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet)…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
9 / 92 engine detections
فتح التقرير4 det.
فتح التقريرSuspicious
فتح التقرير3 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
zestprotocol.forum is an impersonation phishing page posing as Zest Protocol. It uses the real project's tagline as its page title: "Zest Protocol | The Bitcoin liquidity protocol." It targets people who lend, borrow or supply liquidity in Bitcoin DeFi and expect to reach the genuine app. PhishDestroy first flagged it on 2026-10-07. As of 2026-10-19 the domain was still registered, but its DNS was no longer serving the page.
The site copies Zest Protocol's name and branding. The unusual .forum ending makes it look like a community or support hub rather than an obvious fake. Pages like this usually push visitors to "connect wallet" and then ask them to approve a transaction, sign a message, or type in a recovery phrase to "fix" or "claim" something. Any of those steps can hand an attacker control of the funds. A leaked seed phrase exposes the entire wallet, not just the assets held in the protocol.
VirusTotal shows 9 of 92 engines flagging the domain as of 2026-10-11. The flagging vendors include alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a modest count, but these are independent vendors reaching the same verdict within days. The crypto-focused blocklists carry more weight here: MetaMask, ScamSniffer and SEAL all list the domain alongside PhishDestroy, so many wallet users will see a warning before the page loads. Three AlienVault OTX threat pulses also reference it.
The domain was registered on 2026-10-06 through Spaceship, Inc., and PhishDestroy caught it the next day. That one-day gap fits a site built for a fast, short-lived campaign. Traffic passed through Cloudflare (AS13335, US), so the visible IP address belongs to Cloudflare's network, not the operator's actual server. A free automated Let's Encrypt certificate gave the page a padlock, which says nothing about whether the site is legitimate.
If you connected a wallet on zestprotocol.forum, open a token-approval checker for every chain you used and revoke any permissions granted around the time of your visit. If you signed a transaction you did not fully understand, or entered a seed phrase, assume the wallet is compromised. Create a new wallet and move your remaining assets to it right away. Reach Zest Protocol only through bookmarked or officially announced addresses, never through links in DMs, replies or search ads. Defenders should block the domain and watch for lookalike registrations that pair the Zest Protocol name with new top-level domains.
Last checked
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 إلى هذا المجال.
ashley.ns.cloudflare.comevan.ns.cloudflare.comLocation describes the IP network.
986353248d791766a7e175bb4b2112fcc92ed78e3fee0e1f61d1255d8f83bb0eSaved 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 zestprotocol.forum · checked Oct 7, 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.
zestprotocol.forum
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
غير معروف→live_content
content_served
غير معروف→live_content
content_served
live_content→inactive
http_no_content
غير معروف→live_content
content_served
يمكن الوصول إليه
No threat flag
View source9/92 engine detections
View source3 community references
View sourcePD-20261007-29B0CD
zestprotocol.forum
View sourcePage captured
View sourcePD-20261007-29B0CD Recipient: abuse@spaceship.com إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
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 ↗
zestprotocol.forum)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.