VirusTotal
19 / 92
“vpnmyha.shop — Быстрый и надёжный VPN”
vpnmyha.shop — Último activo conocido (HTTP 200). Resumen de las pruebas: VirusTotal 19/92 (alphaMountain.ai, BitDefender, Certego, Chong Lua Dao, CRDF); 1 external blocklist match (CryptoFirewall); CF Radar malicious; PhishDestroy score 100/100. Registrador: Registrar of domain na….
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
vpnmyha.shop was observed in a CryptoFirewall blocklist entry dated 2026-10-13, which records its presence as a listed domain. The domain also received a PageSpeed performance score of 72 on the same date.
CryptoFirewall documented vpnmyha.shop as an external blocklist entry on 2026-10-13. VirusTotal checked the domain on 2026-10-09, recording 19 detections out of 92 total scanners. OTX referenced vpnmyha.shop in 7 pulses as of 2026-10-13. PhishDestroy internally listed the domain, and a PageSpeed check was performed on 2026-10-13 with a score of 72.
VirusTotal contains a detection measurement for vpnmyha.shop, which quantifies how many scanners flagged the domain in its check. CryptoFirewall and OTX provide blocklist and pulse references, respectively, documenting their own criteria for inclusion. The evidence spans several sources, offering a snapshot of technical and security-related observations from multiple dates.
vpnmyha.shop should be reviewed against the CryptoFirewall blocklist entry and VirusTotal detection record for ongoing monitoring. Preserve the OTX pulse references and PhishDestroy internal listing for future comparison. These records can be used to track changes in domain status and inform any subsequent analysis or checks.
Observaciones almacenadas de rastreadores frente a navegadores para este servidor, además de una comprobación en tiempo real de la huella digital para sistemas de distribución de tráfico al estilo Keitaro.
nginx/1.24.0 (Ubuntu)Nota del escáner: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.24.0 (Ubuntu)
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.
ns2.reg.ruLocation describes the IP network.
849bf3b4c1316b0022c8f4f6b42bfe4feade32f0f2600a41c063dd30b3f922a7www.vpnmyha.shopSaved 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 vpnmyha.shop · checked Oct 13, 2026
212.192.14.75. 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.
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
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.