Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
idoaiyf.com favicon

idoaiyf.com

“Netflix”

Registrador
Name.com
Resolved IP
216.198.79.1
Registered
17/08/2026
PhishDestroy assessment Crítico
Disponibilidad Contenido no disponible El contenido no estaba disponible en la última observación. Observado · HTTP probe
VirusTotal detecciones: 12/91 Etiqueta automática de marca: Netflix
27/09/2026 1 Report Sent CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 12. Tenga extrema precaución: no ingrese credenciales o información personal.
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
Page captures
open gallery
Domain age
Reports sent
view timeline
Resumen del informe

Suplantación de Netflix: idoaiyf.com — Contenido no disponible. Resumen de las pruebas: VirusTotal 12/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET)…

El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.

Source evidenceVirusTotal 12 / 91 6 sources

VirusTotal

12 / 91 engine detections

Abrir informe

Google Safe Browsing

No threat flag

Abrir informe

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Inteligencia de seguridad de red
CF Cloudflare Radar Verdict Malicioso
Phishing Phishing Security threats

Analysis

Crítico
VirusTotal
12 / 91
Page captures
3

PhishDestroy threat report

Overview

idoaiyf.com is a phishing site that posed as Netflix, with a page titled simply "Netflix" to pass as the real streaming service. It targeted Netflix subscribers and anyone who could be persuaded they had an account problem. PhishDestroy first detected it on 2026-09-27. The site went offline on 2026-09-28, and its DNS was still inactive when we last checked on 2026-10-19.

How the scam works

Netflix phishing usually starts with an email or text warning that a payment failed or the account is about to be suspended. The link leads to a copy of the Netflix sign-in page, like the one on idoaiyf.com. The victim types in their email and password, and these pages often go on to ask for card details to "restore" the subscription. The attackers can then take over the account, reuse the password on other services where it was used, and make fraudulent charges on the card.

Evidence

Twelve of 91 VirusTotal engines flagged the domain on 2026-09-27. Among them were alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET, Emsisoft, Fortinet and G-Data, which means several unrelated security vendors reached the same conclusion. urlscan.io rated the page malicious and recognized Netflix branding on it, which confirms the impersonation. The domain is on the PhishDestroy blocklist.

Infrastructure

The domain was registered through Name.com, Inc. on 2026-08-17, about six weeks before we caught it. That gap fits a pattern where a disposable domain is registered ahead of time and then used for a short campaign. The site was hosted on Amazon's AMAZON-02 network in the United States. It was live for only about a day after detection, so most of its victims were likely reached in that short window or just before it.

What to do

If you entered your Netflix login on this site, change your Netflix password right away. Then sign out of all devices from your account settings. Change the password anywhere else you used the same one. If you typed in card details, call your bank to block the card, and check your statements for charges you don't recognize. Defenders should block the domain, search mail logs for Netflix-themed messages that link to it, and reset credentials for any users who clicked through.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura guardada · 3 captures

Domain details

Dominio
URLScan verdict Malicioso score 100 Phishing brand: Netflix report ↗
IP Context Vercel shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
Registrador Name.com US(US)
Contacto de abusoabuse@name.com, abuse@vercel.com
Registro de la ICANNICANN Lookup (RDAP) →
RegistroCreado 17/08/2026 (63d · New) — Expires 17/08/2027
Tiempo hasta la primera indisponibilidad 20h
Qué contabilizamos Tiempo transcurrido desde el primer informe de abuso almacenado hasta la primera observación de que el contenido no estaba disponible. Esto no establece la causa.
Qué contiene cada informe Los registros de informes salientes almacenados pueden hacer referencia a evidencia disponible en ese momento, como veredictos de proveedores, datos de registro, detalles de alojamiento, clasificaciones o capturas de pantalla. Esta página no infiere la carga útil entregada, el recibo, el acuse de recibo o la acción exacta por parte de un destinatario.
Detalles técnicosProvenance & timestamps
Primera detección27/09/2026
DOM Analysisanalyzed 27/09/2026score 88/1001 brand signal
Submitted URLhttp://idoaiyf.com/hcaptcha
Favicon Hash
ID del caso
Observed page title
Netflix
Automated brand references
Netflix
Certificado TLS
Emitido por YR1

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.198.79.1
Network ASN
AS16509
Organization
AMAZON-02 - Amazon.com, Inc., US
Observed location
US
Server header
Vercel

La reputación de Edge-IP no se atribuye a este dominio.

Servidores de nombres 2

  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

Location describes the IP network.

Certificado TLS

Issuer
YR1
Collection source
PhishDestroy collector

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS inactivo reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Desconocido Probe Inconclusive 20% 2026-10-19 01:16:43 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-09-27 11:01:14 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-27 11:01:14 UTC → 2026-09-30 16:14:55 UTC · 77.23h midpoint estimate ≈ 2026-09-29 01:38:04 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Tecnologías · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

12 / Los proveedores de seguridad de 91 marcaron este dominio
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Emsisoft
Fortinet
G-Data
Kaspersky
Netcraft
SOCRadar
Webroot

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of idoaiyf.com · checked Sep 27, 2026

77
Needs Work
Performance
FCP
0.76s
First Contentful Paint
LCP
2.67s
Largest Contentful Paint
CLS
0.012
Cumulative Layout Shift
TBT
822ms
Total Blocking Time
SI
2.93s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
77.23
Estimate basis
Bounded by observations
Estimate precision
Low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history12

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

Earlier observations 7
  1. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Accesible→No disponible

  7. Availability monitor · First collection record

    Accesible

Recorded activity

5 entries
  1. Abuse report sent

    PD-20260927-ED1726

    abuse@name.com
  2. URLScan

    Page captured

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. VirusTotal

    12/91 engine detections

    View source
  5. Added to PhishDestroy

    idoaiyf.com

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

idoaiyf.com

Datos y informes externos

Instantánea de evidencia enviada
Sent: Ledger records: 1 Case ID: PD-20260927-ED1726 Recipient: abuse@name.com
Page title stored with report: Netflix
PDF notice generated Notice text archived (653 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (US):
18 U.S.C. § 1343 - Wire Fraud
18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA)
15 U.S.C. § 45 - FTC Act (Deceptive Practices)
Federal laws prohibit wire fraud, computer fraud, and deceptive business practices.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

5 evidence signal groups linked 1 stored notification records Contenido no disponible
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Official reporting routes

¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales. Más información sobre el fraude en las ayudas de recuperación →

Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente · Revíselo y envíelo usted mismo
After a phishing incident

Recomendaciones y consejos para las víctimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

¿Qué debo hacer ahora mismo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Cambiar todas las contraseñas — correo electrónico, cuentas de Exchange, cualquier cosa que utilice la misma contraseña
  • Activar la autenticación de dos factores utilizando una aplicación de autenticación (no SMS). Desactivar la recuperación mediante SMS
  • Tarjetas de congelación si has introducido tus datos bancarios en la página de phishing

¿Qué información debo recopilar para mi informe?

Directrices del FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Fechas y horas exactas — de cada transacción y del primer contacto con el estafador
  • Capturas de pantalla — páginas web fraudulentas, mensajes de chat, correos electrónicos, transacciones con monederos electrónicos, redes sociales
  • Todas las URL y dominios utilizados por el estafador (incluidos idoaiyf.com)
  • Comunicaciones — correos electrónicos, mensajes de texto, números de teléfono y nombres de usuario que utilizó el estafador

Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.

¿Dónde debo denunciar la estafa?

  • IC3 del FBI — Centro de Denuncias de Delitos en Internet (sistema federal de denuncia de EE. UU.)
  • Europol — Informes sobre la ciberdelincuencia en Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Policía local — deja constancia oficial, aunque no puedan actuar de inmediato

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Páginas web falsas — Clones idénticos al milímetro de sitios web legítimos, con dominios ligeramente modificados
  • Sacrificio de cerdos — Se ganaba la confianza de las víctimas a lo largo de varias semanas a través de Telegram, WhatsApp o aplicaciones de citas, y luego les robaban el dinero.
  • Estafas relacionadas con la recuperación — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Estafas basadas en la inteligencia artificial — los «deepfakes», el phishing automatizado y los sitios web generados por IA, que hacen que el fraude sea más difícil de detectar

¿Cómo puedo protegerme en el futuro?

  • Añadir a favoritos las páginas web oficiales — Nunca hagas clic en enlaces de correos electrónicos, mensajes directos o anuncios
  • Verificar dominios — comprobar si PhishDestroy antes de interactuar. Comprueba que sea HTTPS, la ortografía y la antigüedad del dominio
  • «Demasiado bueno para ser verdad» = estafa — rendimientos garantizados, recomendaciones de famosos, plazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/idoaiyf.com"
  title="PhishDestroy threat report for idoaiyf.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>