VirusTotal
4 / 89
“Murex.exchange - Надежный онлайн обменник”
murex.exchange returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The same record set notes that the domain was first observed on 2026-07-27, giving a bounded window for the observations discussed here.
The PhishDestroy internal listing for murex.exchange is recorded as true, and the OTX check on 2026-08-14 counted 3 pulses. VirusTotal, checked on 2026-09-14, reported 4 detections across 89 scanners. The SSL scan on 2026-08-12 identified the issuer as Let's Encrypt / YR2, while the PageSpeed check on 2026-08-12 returned a performance score of 64. The registrar is recorded as NameCheap, Inc., and the IP address 91.108.190.226 is associated with GB and NetWarm LTD.
The named sources were captured on different dates, so their counts and statuses describe separate moments rather than one synchronized snapshot. Because the PhishDestroy listing, OTX pulses, VirusTotal detections and HTTP response were recorded at different times, a reader should compare them as dated observations, not as a single current state. The PageSpeed and SSL records from 2026-08-12 sit between the earliest and latest checks, which further limits direct comparison across all fields.
Anyone reviewing murex.exchange should retain the dated records exactly as captured, including the HTTP check, OTX count, VirusTotal result and the PhishDestroy listing, so later observations can be compared against them. Subsequent checks of murex.exchange should be logged with their own dates and source names before any conclusion is drawn. During review, avoid submitting passwords, payment details or other sensitive information to the site until the recorded observations have been independently verified.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx
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.
meilani.ns.cloudflare.commx.yandex.netpriority 10Location describes the IP network.
d7e209aeb1ef7b74ce19a51bc2d7a81b42bacf258a4e69f28ae8a59da9f0e8efwww.murex.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 murex.exchange · checked Aug 12, 2026
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
1 community report
CategoryIMPERSONATION
This is a coordinated "frozen order" exchange scam operated through a Telegram account named "Flowisland Support." The group poses as a cryptocurrency exchange service. Method of operation: After a victim sends crypto for a swap (SOL to TRX), the operators claim the order is "fr
“This is a coordinated "frozen order" exchange scam operated through a Telegram account named "Flowisland Support." The group poses as a cryptocurrency exchange service. Method of operation: After a victim sends crypto for a swap (SOL to TRX), the operators claim the order is "frozen" due to a fabricated network error — e.g. a "7th validator error" on Solana, or a claimed amount mismatch (5.55 vs 5.56 SOL). No such error exists; this is a pretext. They then demand the victim make a second ident”
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
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