Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
zap.exchange favicon

zap.exchange

“zap.exchange — Swap crypto and fiat. Instantly.”

Bureau d’enregistrement
NameCheap
Resolved IP
198.177.120.137
Registered
02/12/2025
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 7/89 Spamhaus DBL: DBL_PHISH Correspondances de la liste de blocage stockée : 2 Libellé de marque automatique : MetaMask
OTX: 4 refs 02/09/2026 1 Report Sent CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 7. Listes de blocage publiques signalant une correspondance : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260902-E3D1E5
Current status
HTTP 301 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Résumé du rapport

Usurpation de MetaMask: zap.exchange — Dernier actif connu (HTTP 301). Résumé des preuves: VirusTotal 7/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 7 / 89 · OTX 4 references 7 sources

Spamhaus DBL

DBL_PHISH

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critique
VirusTotal
7 / 89
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/zap_africaStored page reference

IoC extraction recorded 2026-09-03 04:00:10 UTC

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Répertorié View source
PhishDestroy PhishDestroy list View source
SEAL Répertorié View source

Last checked

Capture enregistrée · 3 captures

Observed page title
zap.exchange — Swap crypto and fiat. Instantly.
Automated brand references
BNB Chain Ethereum Instagram Polygon Solana Telegram TikTok Tron +1
Certificat TLS
Émis par Sectigo Limited · stored validity ends in 90 days

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement NameCheap (Unknown)
Contact anti-abusabuse@namecheap.com
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 02/12/2025 (322d) — Expires 02/12/2026
Statut HTTP301 Moved Permanently
Détails techniquesProvenance & timestamps
Première détection02/09/2026
DOM Analysisanalyzed 09/10/2026score 95/1009 brand signals
IoC Extractionscanned 03/09/20260 wallet · 1 Telegram IoC
Submitted URLhttp://zap.exchange/
Favicon Hash
ID du dossier
ICANN OVERSIGHT

Contexte de l’accréditation et du RAA

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
198.177.120.137
Observed location
Frankfurt am Main, DE
Server header
cloudflare

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 2

  • dns1.namecheaphosting.com
  • dns2.namecheaphosting.com

Mail routing 3 MX records

  • mx1-hosting.jellyfish.systemspriority 5
  • mx2-hosting.jellyfish.systemspriority 10
  • mx3-hosting.jellyfish.systemspriority 20

Location describes the IP network.

Certificat TLS

Issuer
Sectigo Limited
Valid from
2025-12-02 00:00:00
Valid until
2026-12-02 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:18 UTC
Collection source
PhishDestroy collector
Certificate fingerprint2a38c26fc6d0d587b4ab8e41bc9efff2aca079b04acb626aa737735951a4743f
Certificate names · 1 SANs
  • www.zap.exchange

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 22:37:44 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 22:37:44 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 22:37:44 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

7 / Les fournisseurs de sécurité 89 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
VIPRE
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of zap.exchange · checked Sep 2, 2026

74
Needs Work
Performance
FCP
3.49s
First Contentful Paint
LCP
3.49s
Largest Contentful Paint
CLS
0.133
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
6.03s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

redirect: raw=redirect_301; http=301; via=https_proxy; location=https://zapexchange.app/; server=LiteSpeed

Browser
zap.exchange — Swap crypto and fiat. Instantly.
Crawler
301 Moved Permanently
zap.exchange
Résultat enregistré
Inaccessible
Stored observation history19

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

Earlier observations 14
  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  13. VirusTotal · Detection count

    0→3

  14. Availability monitor · First collection record

    Accessible

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    7/89 engine detections

    View source
  4. Abuse report sent

    PD-20260902-E3D1E5

    abuse@namecheap.com
  5. Added to PhishDestroy

    zap.exchange

    View source
  6. URLScan

    Page captured

    View source

Domaines ressemblants

79 domaines ressemblants enregistrés

Tout afficher (67)
metasmask.io insertion Rapport interne metramask.io insertion Rapport interne mewtamask.io insertion Rapport interne mmetamask.io homoglyph Rapport interne mtamask.io omission Rapport interne mwetamask.io insertion Rapport interne nmetamask.io homoglyph Rapport interne metamark.io bitsquatting Rapport interne metamaskj.io addition Rapport interne metammask.io homoglyph Rapport interne metamnask.io homoglyph Rapport interne emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Renseignement communautaire

2 signalements communautaires

CatégoriePHISHING

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

Données factuelles et rapports externes

Community Scam Report — ChainAbuse
2 reports filed for zap.exchange (2 written by people) · category: Phishing · source checked
“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”
— reported by Anonymous on Sep 2, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260902-E3D1E5 Recipient: abuse@namecheap.com
Page title stored with report: zap.exchange — Swap crypto and fiat. Instantly.
PDF notice generated Notice text archived (289 chars)
Abuse notice text as sent to the provider
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
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

6 evidence signal groups linked 1 stored notification records Dernier actif connu
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Official reporting routes

Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

Template-based draft · optional AI wording assistance requires separate consent

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Que dois-je faire tout de suite ?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment zap.exchange)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/zap.exchange"
  title="PhishDestroy threat report for zap.exchange"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>