VirusTotal
5 / 89
DenunciarInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“ReLai”
Assessment based on the stored source evidence below. Review sources →
No stored capture is available for this domain.
fgu.autos — No verificado. Resumen de las pruebas: VirusTotal 5/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar, VIPRE); PhishDestroy score 88/100. Registrador: Dynadot.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el 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.
5 / 89
DenunciarEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
4 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.
80/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
DenunciarA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
fgu.autos returned HTTP status 200 in an HTTP check recorded on 2026-10-01, the most recent availability observation in this evidence set. The same domain was first observed on 2026-09-04, roughly four weeks earlier, according to the recorded first-observation date.
The HTTP check on 2026-10-01 recorded status 200 for fgu.autos, while the first observation of the domain is dated 2026-09-04. VirusTotal, checked on 2026-09-18, reported 5 detections across 89 scanners, and OTX, checked on 2026-09-14, listed 4 pulses. The PhishDestroy internal listing was recorded as true, and a PageSpeed check on 2026-09-14 produced a performance score of 96. The registrar is Dynadot Inc, and the SSL certificate issuer is Let's Encrypt / YR1, scanned on 2026-09-14.
The HTTP 200 record describes only the response captured on that date, not the domain's content or its present availability. The VirusTotal and OTX figures reflect separate source observations made on different dates, so they should be read as distinct records rather than combined into a single trend. The PhishDestroy listing and the PageSpeed score likewise come from different checks, and the chronology from first observation to the HTTP check spans several weeks without establishing what occurred in between.
Preserve the fgu.autos HTTP check record and the PhishDestroy listing entry as separate source records for later comparison. Compare the VirusTotal and OTX observations against future checks of fgu.autos, keeping each source's own record distinct. Retain the PageSpeed result alongside these records so that later measurements of fgu.autos can be reviewed against the same source set.
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.
Nota del escáner: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fgu.autos', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOCK
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.dyna-ns.netLocation describes the IP network.
bbb552bbd63227b525903a60e5b9da3ecc2340f93992d73e1c12c5bd6858ac6fbcf.autosbfe.latesd.autosfcv.autosgdb.autosghu.autoshdu.lathfs.latjfm.latjfu.latjgc.latkfh.autosmhx.latwhu.autosSaved 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 fgu.autos · checked Sep 14, 2026
6 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.
1 reporte de la comunidad
CategoríaPIGBUTCHERING
I was contacted via telegram by someone claiming to work for a company that increased app views. When you viewed an app- you were paid 5-10$ per app. Then you had to complete a “node tasks “ with bitcoin in order to become a full time employee and receive your commissions. Upon c
“I was contacted via telegram by someone claiming to work for a company that increased app views. When you viewed an app- you were paid 5-10$ per app. Then you had to complete a “node tasks “ with bitcoin in order to become a full time employee and receive your commissions. Upon completing task 1 I sent $240 in bitcoin then was told I had to complete task 2 to cash out my original payment and that would cost $700 when I did that they said their financial department was closing and I had to wait u”
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.