VirusTotal
1 / 92
DenunciarEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“MYXA VPN — бесплатный VPN без лимитов и тормозов”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@reg.ru.
The latest stored availability evidence still shows the domain reachable; 41 hours 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.
myxavpn.com — Último ativo conhecido (HTTP 200). Representação da marca: Telegram; Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 1/92 (CRDF); URLQuery 2 det.; 1 external blocklist match (CryptoFirewall); PhishDestroy score 81/100. Registrador: Registrar of Domain Na….
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
1 / 92
DenunciarEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 det.
Alerts refer to the preserved scan. They do not describe the current state of the site.
1 external matches
DetalhesA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
10 community references
DenunciarCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
relatório armazenado
View stored capture ↗ DenunciarA preserved page image documents what the collector received; a capture is not a safety verdict.
Análise concluída
DenunciarThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
DenunciarA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
The domain myxavpn.com was included in the CryptoFirewall blocklist on 2026-10-16, as recorded by an external security source. On the same date, a PageSpeed performance score of 100 was measured for the domain, documenting a technical aspect of its web infrastructure.
On 2026-10-16, myxavpn.com appeared in the CryptoFirewall blocklist and was listed internally by PhishDestroy. VirusTotal recorded 1 detection out of 92 total scanners for this domain on 2026-10-08. OTX documented 10 pulses referencing myxavpn.com on 2026-10-16. The domain was registered with Registrar of Domain Names REG.RU LLC on 2024-08-03.
PhishDestroy contains an internal listing of myxavpn.com, which documents its inclusion in a database used for tracking domains. VirusTotal provides a measurement of how many security vendors flagged the domain during its scan, offering a perspective on its recognition by security engines. OTX records reflect community-driven intelligence entries, while the CryptoFirewall blocklist entry documents an external security assessment. These sources together offer a range of technical and reputational records for the domain.
For myxavpn.com, retain the CryptoFirewall blocklist entry and the VirusTotal scan record for future reference and comparison. Preserve the OTX pulse documentation and the PhishDestroy internal listing to track any updates in security intelligence. Use these records to inform ongoing technical and reputational assessments of the domain.
24 · datasets with records / 7 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/myxavpn_botStored page referenceIoC extraction recorded 2026-10-16 04:00:08 UTC
1 · external source matches
Registrar of Domain Names REG.RU LLC · 78.17.86.72 · DNS, TLS and retained responses
ns1.reg.runs2.reg.rumxs1.reg.rupriority 5mxs2.reg.rupriority 10Location describes the IP network.
adde141083cba07abc7a3aa45a92b3c74f19efbe5bf26d2a24d2ee0ada6590famyxavpn.spacewww.myxavpn.comwww.myxavpn.spaceSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
app.myxavpn.comDomain recordav01.myxavpn.comDomain recordav02.myxavpn.comDomain recordbritish.myxavpn.comDomain recordcur01.myxavpn.comDomain recorddocs.myxavpn.comDomain recordestonia.myxavpn.comDomain recordfl01.myxavpn.comDomain recordfl02.myxavpn.comDomain recordfl03.myxavpn.comDomain recordfl04.myxavpn.comDomain recordfl05.myxavpn.comDomain recordfr01.myxavpn.comDomain recordfr02.myxavpn.comDomain recordfr03.myxavpn.comDomain recordfr04.myxavpn.comDomain recordfr05.myxavpn.comDomain recordger.myxavpn.comDomain recordger01.myxavpn.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of myxavpn.com · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://myxavpn.com/https://myxavpn.com/Server: nginx/1.24.0 (Ubuntu)Content-Type: text/htmlContent-Encoding: gzipsummarykeep-alivegziptext/htmlFri, 16 Oct 2026 01:30:25 GMTW/"6a45660a-42db"Wed, 01 Jul 2026 19:10:02 GMTnginx/1.24.0 (Ubuntu)chunkedValues retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy response is stored, but it does not establish whether the file exists.
/sitemap.xml
A legacy response is stored, but it does not establish whether the file exists.
/.well-known/security.txt
A legacy response is stored, but it does not establish whether the file exists.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Observações armazenadas comparando o rastreador com o navegador para este host, além de uma verificação em tempo real da assinatura digital para sistemas de distribuição de tráfego do tipo Keitaro.
nginx/1.24.0 (Ubuntu)Local arquivado em 2026-10-16 01:30:26 UTCNota do digitalizador: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.24.0 (Ubuntu)
Nenhum resultado desta verificação foi salvo.
1 · outbound report records
78.17.86.72.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconhecido→live_content
content_served
live_content→Desconhecido
probe_inconclusive
Desconhecido→live_content
content_served
0→1
Desconhecido
Desconhecido
probe_inconclusive
13 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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
PD-20261016-2DB91E Recipient: abuse@reg.ru Registrar: REG.RU (Russia) Policy Violations: Abuse policy + ICANN contractual obligations; phishing classified as bad-faith use in UDRP; domains may be suspended/removed Applicable Laws: Criminal Code RF Art.159 (fraud), Art.272 (illegal access), Art.273 (malware creation), Art.274.1 (critical infrastructure interference)
Recovery steps, reporting contacts and complaint drafts
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 ↗
myxavpn.com)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
Este relatório apresenta as últimas evidências armazenadas disponíveis para PhishDestroy. Os carimbos de data/hora de origem são mostrados quando disponíveis; a disponibilidade e os veredictos do fornecedor podem mudar após a coleta.
O site capturado exibia o título da página “MYXA VPN — бесплатный VPN без лимитов и тормозов” e pode estar se passando por Telegram.
A partir de 2026-10-16 02:40:26 UTC, myxavpn.com tinha detecções de mecanismos de segurança 1.
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
Se você acredita que esta listagem é imprecisa, enviar um recurso. Para conhecer nossa metodologia, acesse o Página de perguntas frequentes.