The domain mexc.monster is a confirmed phishing site engaged in brand impersonation targeting the cryptocurrency exchange MEXC. It presents itself as the legitimate MEXC platform to deceive users into entering credentials or transferring funds, posing an elevated risk of financial loss through cryptocurrency scams. As of the latest verification, mexc.monster has been taken offline, though users who interacted with it while active remain at risk.
Technical analysis shows mexc.monster was flagged by 2 of 95 security vendors on VirusTotal, including CRDF and Gridinsoft, which assigned a trust score of 0 out of 100. The domain appears on one security blocklist, PhishDestroy, and was registered on August 31, 2025, through Gname.com Pte. Ltd. It resolved to the IP address 45.192.98.52, hosted in Hong Kong under AS401701 (cognetcloud INC), with no SSL certificate issued. The observed page title matched the legitimate MEXC branding in Chinese, reinforcing the impersonation attempt.
Users who accessed mexc.monster should immediately change any passwords or credentials entered on the site and enable two-factor authentication on their legitimate MEXC accounts. For cryptocurrency-related exposure, revoke any token approvals granted to unknown contracts and consider transferring funds to a new wallet. Report the phishing domain to the impersonated brand (MEXC) via their official support channels, and submit it to platforms like Google Safe Browsing, PhishTank, or local cybersecurity authorities for further action.
DOM Analysisanalyzed 2026年10月20日score 81/1001 brand signal
Submitted URLhttps://mexc.monster/
Favicon Hash
ICANN OVERSIGHT
認定と 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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 22:18:17 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:18:04 UTCcurrent episode first observed: 2026-10-02 16:16:28 UTCobserved RIP window: 2026-09-15 22:18:04 UTC → 2026-10-02 16:16:28 UTC · 401.97hmidpoint estimate ≈ 2026-09-24 07:17:16 UTC · precision low · basis bounded
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.
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Chong Lua Dao
Gridinsoft
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
401.97
Estimate basis
Bounded by observations
Estimate precision
Low
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.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='mexc.monster', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
mexc.monster
保存済みの結果
Cloaked / Filtered
Stored observation history16
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(SG)
