VirusTotal
7 / 89 engine detections
فتح التقرير“zap.exchange — Swap crypto and fiat. Instantly.”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
انتحال MetaMask: zap.exchange — آخر نشاط معروف (HTTP 301). ملخص الأدلة: VirusTotal 7/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
7 / 89 engine detections
فتح التقريرDBL_PHISH
checked — no detections recorded
فتح التقرير4 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
zap.exchange is an impersonation phishing page that presents itself as an instant swap service under the title "Swap crypto and fiat. Instantly." It targets people who want a quick conversion between cryptocurrency and fiat money. PhishDestroy first flagged it on 2026-09-02. On 2026-10-19 the domain was still alive and its content was reachable through a redirect, so it remains a live risk.
Fake swap and exchange sites rely on a promise of speed. The visitor is asked to send funds for conversion, enter account details, or connect a wallet to "swap." The converted funds never arrive. Wallet connections can be used to request signatures or token approvals that let the operator move assets. The page title presents the site as a standalone exchange rather than naming another brand, while our classification places it in the impersonation category.
Wallet-focused blocklists back the classification. MetaMask and SEAL both list the domain alongside PhishDestroy, so many wallet users are already warned before the page loads. Spamhaus lists it in its DBL as a phishing domain. On VirusTotal, 7 of 89 engines flagged it as of 2026-09-14: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar and VIPRE. That count is modest, so many browsers and security tools will not block it. Four AlienVault OTX threat pulses also reference it.
The domain was registered through NameCheap, Inc. on 2025-12-02, about nine months before PhishDestroy detected it. A domain held that long before use can look older and more trustworthy to reputation filters. It is hosted at 198.177.120.137 in Germany. Its certificate is a domain-validated one from Sectigo, which only proves control of the domain. The browser padlock says nothing about whether the service is legitimate.
Do not send any more funds, and ignore any demand for a "verification" or "release" fee to unlock a pending swap. Paying more only adds to the loss. If you connected a wallet or signed anything, revoke the token approvals granted to unfamiliar addresses with a reputable approval checker. Move remaining assets to a fresh wallet if you ever entered a seed phrase. If you typed passwords or exchange credentials, change them and reset two-factor authentication. Defenders should block zap.exchange at DNS and proxy level, hunt for past visits in their logs, and report the domain to the registrar and hosting provider.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/zap_africaStored page referenceIoC extraction recorded 2026-09-03 04:00:10 UTC
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 إلى هذا المجال.
dns1.namecheaphosting.comdns2.namecheaphosting.commx1-hosting.jellyfish.systemspriority 5mx2-hosting.jellyfish.systemspriority 10mx3-hosting.jellyfish.systemspriority 20Location describes the IP network.
2a38c26fc6d0d587b4ab8e41bc9efff2aca079b04acb626aa737735951a4743fwww.zap.exchangeSaved 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 zap.exchange · checked Sep 2, 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.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://zapexchange.app/; server=LiteSpeed
zap.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
0→3
يمكن الوصول إليه
4 community references
View sourceNo threat flag
View source7/89 engine detections
View sourcePD-20260902-E3D1E5
zap.exchange
View sourcePage captured
View source٧٩ نطاقًا متشابهًا محفوظًا
بلاغان مجتمعيان
الفئةPHISHING
Two websites, zap.exchange and zapexchange.app, are impersonating Zap, a cryptocurrency exchange operated by Zap Exchange UAB, a registered Lithuanian virtual asset service provider. Our legitimate site is zap.africa. The fraudulent sites solicit visitors to enter cryptocurrency
“Two websites, zap.exchange and zapexchange.app, are impersonating Zap, a cryptocurrency exchange operated by Zap Exchange UAB, a registered Lithuanian virtual asset service provider. Our legitimate site is zap.africa. The fraudulent sites solicit visitors to enter cryptocurrency wallet seed phrases and induce them to send funds to the operators to perform exchanges. A seed phrase grants complete and irreversible control of a wallet; no legitimate exchange requests one. The sites also display o”
PD-20260902-E3D1E5 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
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 ↗
zap.exchange)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.