Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
aerodrome.network favicon

aerodrome.network

“aerodrome.network | 522: Connection timed out”

Registrador
Tucows
Resolved IP
188.114.97.3
Registered
21/02/2026
PhishDestroy assessment Crítico
First observed Feb 26, 2026 22:22 UTC · PhishDestroy
VirusTotal detecciones: 6/90 Coincidencias de la lista de bloqueo almacenadas: 3 Etiqueta automática de marca: Aerodrome
OTX: 23 refs 26/02/2026 CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 6. Listas de bloqueo públicas que informan una coincidencia: 3. Tenga extrema precaución: no ingrese credenciales o información personal.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Resumen del informe

Suplantación de Aerodrome: aerodrome.network — No verificado. Resumen de las pruebas: VirusTotal 6/90 (alphaMountain.ai, Chong Lua Dao, Emsisoft, Forcepoint…

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

Source evidenceVirusTotal 6 / 90 · OTX 23 references 5 sources

VirusTotal

6 / 90 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.

Analysis

Crítico
VirusTotal
6 / 90
OTX
23 community refs
Page captures
2

PhishDestroy threat report

The domain aerodrome.network was registered on 21 February 2026 through Tucows Domains Inc. It resolves to the Cloudflare‑owned address 188.114.97.3 (AS13335, United States) and is served by the nameservers peyton.ns.cloudflare.com and frida.ns.cloudflare.com. The site is protected by Cloudflare with HTTP/3 enabled and presents an SSL certificate issued by Google Trust Services / WE1. HTTP requests return a 403 status and the only observable page title is "aerodrome.network | 522: Connection timed out". Gridinsoft assigns the domain a trust score of 0 / 100. The domain appears on four public blocklists and is actively blocked by PhishDestroy, Polkadot, Enkrypt and Codeesura. VirusTotal analysis shows that 2 of 93 security vendors flagged the domain as malicious. The threat is classified as brand impersonation targeting the Aerodrome brand, with the scam type recorded as impersonation. Current intelligence indicates the infrastructure remains active as of 12 July 2026. Defenders should add aerodrome.network to deny‑list rules, monitor DNS queries for the 188.114.97.3 address, and enforce blocklist updates to ensure traffic is blocked at network perimeter. Continuous observation is recommended to detect any change in response codes or additional malicious payloads.

Blocklist matchesPolkadot · PhishDestroy · Enkrypt · Codeesura 4
Polkadot Incluido View source
PhishDestroy PhishDestroy list View source
Enkrypt Incluido View source
Codeesura Incluido View source

Last checked

Captura guardada · 2 captures

Observed page title
aerodrome.network | 522: Connection timed out
Automated brand references
Aerodrome
Certificado TLS
Emitido por Google Trust Services / WE1

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
OTX tags 2026-02activeall-domainsblockchainblocklistcontentcryptocrypto scamcryptocurrencydestroylistdominiosdrainerfraudlive+4 more
Registrador Tucows CA(CA)
Contacto de abusodomainabuse@tucows.com
Registro de la ICANNICANN Lookup (RDAP) →
RegistroCreado 21/02/2026 (241d) — Expires 11/10/2027
Cloaking Cloaking Detected Status split · score 2/6
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='aerodrome.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
checked 20/10/2026
Detalles técnicosProvenance & timestamps
Primera detección26/02/2026
DOM Analysisanalyzed 23/04/2026score 100/1001 brand signal
Favicon Hash
ICANN OVERSIGHT

Acreditación y contexto RAA

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft No se envía nada automáticamente.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

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

Servidores de nombres 1

  • frida.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Google Trust Services / WE1
Valid from
2026-03-14 09:32:18
Valid until
2026-06-12 10:30:45
Validity
Stored certificate expired
Collection time
2026-03-15 08:07:34 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7cff06d13e6ff386928b5e7855dbbe4a952af5e57f5412f2a2fc682256984a12

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-20 10:00:22 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-13 10:00:36 UTC current episode first observed: 2026-10-13 20:21:07 UTC observed RIP window: 2026-10-13 10:00:36 UTC → 2026-10-13 20:21:07 UTC · 10.34h midpoint estimate ≈ 2026-10-13 15:10:51 UTC · precision medium · 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

6 / Los proveedores de seguridad de 90 marcaron este dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
Chong Lua Dao
Emsisoft
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
Registration & observation details8

Availability observations

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

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

Check for cloaking

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

Different responses detected

status_split · unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='aerodrome.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr

aerodrome.network
Resultado guardado
Inaccesible
Stored observation history17

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 12
  1. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    redirected→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  4. Availability monitor · Recorded state

    No disponible→Accesible

  5. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    Accesible→No disponible

  11. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/7a2b1682-33db-4598-9785-30aac1723819

  12. Availability monitor · Recorded state

    Accesible→No disponible

Recorded activity

5 entries
  1. AlienVault OTX

    23 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    6/90 engine detections

    View source
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    aerodrome.network

    View source

Inteligencia comunitaria

1 reporte de la comunidad

CategoríaPHISHING

Automated report created by SEAL

Reportes de la comunidad

Reportado por 1 miembro de la comunidad; visto por primera vez el 07/08/2025

Reportes almacenados
1
URL únicas reportadas
1
Aceptado1

Datos y informes externos

Third-Party Detection — ChainAbuse
1 report filed for aerodrome.network · category: Phishing · source checked
Flagged by SEAL on Apr 14, 2024 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

4 evidence signal groups linked 0 stored notification records No verificado

Listed domains receive at least one abuse report; this entry has no retained notification history.

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 aerodrome.network)
  • 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/aerodrome.network"
  title="PhishDestroy threat report for aerodrome.network"
  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>