VirusTotal
11 / 92 engine detections
Abrir informe“MYXA VPN — бесплатный VPN без лимитов и тормозов”
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; 4 days 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.
Suplantación de Telegram: myxavpn.com — Último activo conocido (HTTP 200). Resumen de las pruebas: VirusTotal 11/92 (alphaMountain.ai, BitDefender, Certego…
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
11 / 92 engine detections
Abrir informe2 det.
Abrir informe10 community references
Abrir informeprovider verdict: clean
Abrir informeNo threat flag
Abrir informeNo malicious flag
Abrir informeResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
myxavpn.com is an impersonation phishing page that presents itself as MYXA VPN, a free VPN service. Its Russian-language title promises a free VPN without limits or slowdowns, so it targets Russian-speaking users looking for a no-cost way around restrictions. PhishDestroy first saw the domain on 2026-10-16. As of 2026-10-19, the site is online and its content is live.
The page is titled "MYXA VPN — бесплатный VPN без лимитов и тормозов", which promises a free VPN with no limits and no slowdowns. Impersonation sites like this borrow a service's name and branding to gain trust, then use the offer to push visitors into an action that benefits the operator. That action is usually downloading a so-called client, creating an account, or entering payment or login details. Victims can lose credentials, personal information or money, and a fake VPN installer can put unwanted software on their device. The page markets itself as a VPN service, and PhishDestroy classifies it as impersonation.
Independent detection is still thin. On 2026-10-16, VirusTotal showed 1 of 92 engines flagging the domain, with CRDF as the only vendor. The domain appears on the PhishDestroy and CryptoFirewall blocklists. It is also referenced in 10 AlienVault OTX threat pulses. The low antivirus count means many security products will not warn visitors yet, so blocklist coverage matters more here.
The domain was registered on 2024-08-03 through Registrar of Domain Names REG.RU LLC. The site is hosted at 78.17.86.72 on the SNOWD Snowd Security OU network, which is registered in Estonia, and the server is located in Finland. Its TLS certificate was issued by Let's Encrypt (YE1). A valid padlock only means the connection is encrypted and says nothing about whether the site is legitimate.
Do not download or install any VPN client from this site, and do not enter details on it. If you installed something from it, uninstall it, run a full malware scan, and change passwords for accounts you used on that device. If you entered login credentials, change them at once and turn on two-factor authentication. If you entered card details, contact your bank to block the card and dispute any charges. Defenders should block the domain and its hosting IP at DNS, proxy and email gateways, and add it to internal threat feeds given its low vendor coverage.
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
Last checked
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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
0→1
11/92 engine detections
View sourceNo threat flag
View source10 community references
View sourcePD-20261016-2DB91E
Page captured
View sourcemyxavpn.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
myxavpn.com
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)
Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
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)Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.
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álisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraEnvía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarInformes de phishing recientes y cambios de disponibilidad observados
MonitorizarSupervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un 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.