VirusTotal
5 / 91 engine detections
Open reportexchexch.exchange is a blocklisted domain detected by PhishDestroy on 2026-02-13. Risk: critical (78/100). Registrar: NiceNIC. Hosting: Cloudflare, Inc. VirusTotal: 5/91 engines flag it. Do not enter credentials or connect a wallet.
“ExchExch.Exchange — Fast Crypto Swap | exch.cx Alternative”
5 / 91 engine detections
Open reportMalicious
Open report23 community references
Open report14 checked — no blocks
No threat flag
Open reportPage capture
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This report analyzes the domain exchexch.exchange, identified as a fake cryptocurrency exchange. The site presented itself as "ExchExch.Exchange — Fast Crypto Swap," implying it was an alternative to the legitimate exch.cx platform. The primary threat posed by this domain is phishing and financial fraud, as fake exchanges are designed to steal user login credentials and deposited cryptocurrency funds.
Technical analysis reveals the domain was flagged as malicious by 5 out of 95 vendors on VirusTotal, with specific flagging from alphaMountain.ai, CyRadar, Fortinet, Seclookup, and SOCRadar. It appears on one blocklist. The domain was registered on February 21, 2026, through NiceNIC International Group Co., Limited, and resolves to IP address 172.67.205.7 in the United States, hosted on AS13335 Cloudflare, Inc. The site uses an SSL certificate issued by Google Trust Services / WE1, and its nameservers are will.ns.cloudflare.com and jo.ns.cloudflare.com.
The domain is currently offline and has a GridinSoft trust rating of 0/100, indicating a very low level of trustworthiness. The risk level for any user who may have interacted with this site is high, as it was designed to facilitate theft of cryptocurrency assets. Users should avoid any future access to this domain or related services.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 019c5579-da0e-71e9-b952-3688ac27000f |
|---|---|
| Final url | https://exchexch.exchange/ |
| Status | 200 |
| Ip | 172.67.205.7 |
| Contacted domains | [
"fonts.gstatic.com",
"static.cloudflareinsights.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.250.195.131",
"104.16.80.73",
"142.250.76.106",
"172.67.205.7"
] |
| Asns | [
"15169",
"13335"
] |
| Countries | [
"US"
] |
| Document hash | 7926c5f6ac1074a0797b08a107c87b5388ac567f2e8e21fff6452903007f52cf |
| Globals | [
"crashReport",
"updateReceive",
"updateMinAmount",
"initCustomSelect",
"initSwap",
"__cfBeacon"
] |
| Cookies | [
"PHPSESSID"
] |
| Tls | {
"san": [
"exchexch.exchange",
"*.exchexch.exchange"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "exchexch.exchange",
"protocol": "QUIC",
"valid_to": "2026-05-14T02:21:29Z",
"valid_from": "2026-02-13T01:22:44Z"
} |
| Domain age days | 177 |
| Apex age days | 177 |
| Tls age days | 0 |
| Tls valid days | 90 |
| Requests | 58 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-0.1.0-1-d9114fd"
],
"score": 70,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=UTF-8"
} |
Observed: · Retrieved:
| Uuid | 9b4b3107-028d-444c-9b3d-7670788bda20 |
|---|---|
| Final url | https://exchexch.exchange/ |
| Status | 200 |
| History | [
{
"url": "https://exchexch.exchange/",
"status": 200
}
] |
| DOM structure hash | 78efd3f2ddcde5c15f6605e858e231d61182411b09eb888b0ce9dc4501c424b2 |
| Document hash | 8fc6b8f328be99abc7f641078b6e9576fb666263241f38d39f216728b732b970 |
| Domain risks | [
"DGA Domains",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| DNS records | [
{
"name": "exchexch.exchange",
"type": "A",
"value": "172.67.205.7"
},
{
"name": "exchexch.exchange",
"type": "A",
"value": "104.21.22.125"
},
{
"name": "exchexch.exchange",
"type": "AAAA",
"value": "2606:4700:3034::6815:167d"
},
{
"name": "exchexch.exchange",
"type": "AAAA",
"value": "2606:4700:3032::ac43:cd07"
}
] |
| Dnssec valid | false |
| Ip | 172.67.205.7 |
| Verdict | {
"tags": [
"dga domains"
],
"malicious": true,
"categories": [
"dga domains"
]
} |
| Registration record | {
"registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
"created": "2025-08-19T21:53:51Z",
"updated": "2025-08-24T21:53:52Z",
"expires": "2026-08-19T21:53:51Z",
"nameservers": [
"will.ns.cloudflare.com",
"jo.ns.cloudflare.com"
]
} |
No. PhishDestroy classifies exchexch.exchange as a blocklisted domain (risk: critical, 78/100); it was first detected on 2026-02-13. VirusTotal: 5/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on exchexch.exchange. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
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 reputation is not attributed to this domain.
jo.ns.cloudflare.comLocation describes the IP network.
4f72f3f35e6a65f021950f132f9436f8b89ea8f523f2d19bac2346959ff70946exchexch.exchange*.exchexch.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 exchexch.exchange · checked Mar 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='exchexch.exchange', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
exchexch.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Reachable→Unavailable
23 community references
View source5/91 engine detections
View sourceNo threat flag
View sourceexchexch.exchange
View sourcePage captured
View sourceReported by 1 community member, first seen Feb 12, 2026
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
exchexch.exchange)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.