VirusTotal
5 / 91 engine detections
Abrir relatório“MEXC-ZH”
Imitação de MEXC: h5.mexc.stream — Não verificado. Resumo das evidências: VirusTotal 5/91 (alphaMountain.ai, Chong Lua Dao, Fortinet, Gridinsoft, URLQuery)…
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
5 / 91 engine detections
Abrir relatóriono community references
Abrir relatórioprovider verdict: clean
Abrir relatórioNo threat flag
Abrir relatórioNo malicious flag
Abrir relatórioResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
On 24 July 2026, the domain h5.mexc.stream was observed pointing to IP 45.192.98.52, which is registered to AS401701 (cognetcloud INC) in Hong Kong. The domain was registered on 21 February 2026 through Gname.com Pte. Ltd. and uses the authoritative name servers a9.share-dns.com and b9.share-dns.net. No TLS certificate is presented, indicating the site is served over plain HTTP. The page title returned by the server is "MEXC‑ZH", and the threat intelligence tags the activity as a crypto‑scam that impersonates the MEXC exchange. Google Safe Browsing classifies the URL as a social‑engineering threat, and the domain appears on a single external blocklist.
PhishDestroy has also listed the domain as blocked, and the current operational status is offline. VirusTotal records show that the domain was scanned by 93 security vendors; none of the scanners currently flag the host, but the absence of detections does not constitute a safety guarantee. The limited detection footprint, combined with the lack of SSL, suggests a low‑cost infrastructure often employed in short‑lived impersonation campaigns. The registrar Gname.com Pte. Ltd. is a known bulk‑registration provider, which can impede rapid takedown.
Uncertainty remains regarding the exact content that was hosted before the takedown, as no page capture is available. Analysts should continue to monitor the IP address 45.192.98.52 for re‑use, and consider adding the domain to internal blocklists despite the current offline state. Defensive actions include enforcing DNS filtering of the domain and its name servers, updating web‑gateway policies to block HTTP traffic to the IP, and reviewing any recent authentication attempts against MEXC accounts for potential credential harvesting. Ongoing observation of the registrar and ASN for new registrations may provide early warning of similar campaigns.
For the registrable domain mexc.stream behind this subdomain, 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.
a9.share-dns.comLocation describes the IP network.
55f93f77fce585e315d6e6b5d415c102fc1913c9b3c6f2602b8d59572e7b5e5fzhongming.workSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
h5.mexc.stream
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
No threat flag
View source5/91 engine detections
View sourcePage captured
View sourceh5.mexc.stream
View sourceDenunciado por 1 membro da comunidade; visto pela primeira vez em 09/09/2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
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 ↗
h5.mexc.stream)Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.
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
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraEnvie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarRelatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMonitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo
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.