VirusTotal
12 / 92
“gov-lygi.shop | 520: Web server is returning an unknown error”
gov-lygi.shop — Último activo conocido (HTTP 301). Suplantación de marca: Google; Tipo de estafa: Impersonation. Resumen de las pruebas: VirusTotal 12/92 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, Chong Lua Dao, Forcepoint ThreatSeeker); Google Safe Browsing flagged; Spamhaus DBL_PHISH; PhishDestroy score 100/100. Registrador: Dynadot.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
gov-lygi.shop was recorded with a Google Safe Browsing observation on 2026-10-12, documenting a social engineering threat. The domain was first observed on 2026-10-11, providing a recent timeline for these findings.
Google Safe Browsing flagged gov-lygi.shop for social engineering on 2026-10-12. VirusTotal recorded 12 detections out of 92 scanners on 2026-10-09. OTX noted three pulses referencing the domain on 2026-10-12. The PhishDestroy internal listing included this domain as of the latest check. The PageSpeed performance score was recorded as 100 on 2026-10-12.
The VirusTotal record contains a quantitative scan result, documenting how many security engines detected gov-lygi.shop. Google Safe Browsing provides a classification of the domain's threat type, while OTX records the number of pulses referencing the domain. These sources together offer insight into how multiple security intelligence platforms have evaluated the domain within a short period after its first observation.
For gov-lygi.shop, retain the VirusTotal, Google Safe Browsing, and OTX records for ongoing comparison. Review the PhishDestroy internal listing for updates and reference all dated observations when assessing changes in the domain's security profile.
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.
cloudflareNota del escáner: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://gov-lygi.shop/; server=cloudflare
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.
La reputación de Edge-IP no se atribuye a este dominio.
ryan.ns.cloudflare.comLocation describes the IP network.
37b4fb72c06dcc40a55df9b3f3135586e5c5317f0a765ba1ec444e899788465fSaved 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 gov-lygi.shop · checked Oct 12, 2026
104.21.56.95. 11 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.