Skip to security report
Domain security and threat intelligence
zap.exchange favicon

zap.exchange

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

Registrar
NameCheap
Resolved IP
198.177.120.137
Registered
Dec 2, 2025
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 7/89 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: MetaMask
OTX: 4 refs Sep 2, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 7. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
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
Source evidenceVirusTotal 7 / 89 · OTX 4 references 7 sources

VirusTotal

7 / 89 engine detections

Open report

Spamhaus DBL

DBL_PHISH

URLQuery

checked — no detections recorded

Open report

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
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 Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 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
TLS Certificate
Issued by Sectigo Limited · stored validity ends in 90 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar NameCheap (Unknown)
RegistrationCreated Dec 2, 2025 (322d) — Expires Dec 2, 2026
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedSep 2, 2026
DOM Analysisanalyzed Oct 9, 2026score 95/1009 brand signals
IoC Extractionscanned Sep 3, 20260 wallet · 1 Telegram IoC
Submitted URLhttp://zap.exchange/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

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 Nothing is sent automatically.

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

Edge-IP reputation is not attributed to this domain.

Nameservers 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.

TLS certificate

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 Unknown
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
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
VIPRE
Site Performance Analysis

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
Saved result
Unreachable
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

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 14
  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. VirusTotal · Detection count

    0→3

  14. Availability monitor · First collection record

    Reachable

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

Lookalike domains

79 stored lookalike domains

Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report 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

Community intelligence

2 community reports

CategoryPHISHING

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

Evidence & External Reports

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.
Submitted Evidence Snapshot
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
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including zap.exchange)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

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?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

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

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/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>