Public blocklists
2 external matches
DetallesA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Assessment based on the stored source evidence below. Review sources →
stakoex.app — No verificado. Suplantación de marca: Aave. Resumen de las pruebas: VirusTotal 0/92; URLScan capture; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 66/100. Registrador: CloudFlare.
The evidence summary below uses retained observations. Each source keeps its own collection date.
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.
2 external matches
DetallesA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
checked — no detections recorded
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.
informe almacenado
View stored capture ↗ DenunciarA preserved page image documents what the collector received; a capture is not a safety verdict.
Report stored; verdict not recorded
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.
Evidence-based analysis Generated from the observations retained in this report. No stored AI narrative is available for this record. Each source retains its own collection date.
PhishDestroy first observed stakoex.app on Oct 16, 2026. Stored content metadata identifies Aave as the apparent target. Page analysis recorded additional brand references to Across, Binance, Near, Sui, and Ups. Current evidence score: 66/100 (high).
Positive findings are stored from 2 sources: MetaMask and SEAL. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Oct 16, 2026 at 02:20 UTC. Additional recorded evidence: VirusTotal recorded 0 detections among 92 engines on Oct 16, 2026 at 02:39 UTC. AlienVault OTX listed 4 community pulse references (not vendor detections) on Oct 16, 2026 at 02:41 UTC. URLScan captured the page on Oct 16, 2026 at 02:07 UTC.
The collector marked the hostname reachable on Oct 16, 2026 at 02:07 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 16, 2026 at 00:07 UTC. Registration records for the domain list CloudFlare, Inc. as the registrar and Oct 13, 2026 as the creation date. Registration preceded first observation by 2 days. At collection time, the hostname resolved to 104.21.21.115 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Oct 16, 2026 at 02:20 UTC returned 10/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance.
The content indicators and 2 positive source findings support the current Aave impersonation and phishing classification. The target field identifies Aave.
17 · datasets with records / 14 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
2 · external source matches
CloudFlare, Inc. · 104.21.21.115 · DNS, TLS and retained responses
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.
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
down.stakoex.appDomain recordwww.stakoex.appDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of stakoex.app · checked Oct 16, 2026
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy response is stored, but it does not establish whether the file exists.
/sitemap.xml
A legacy response is stored, but it does not establish whether the file exists.
/.well-known/security.txt
The scanner received HTTP 404 or 410 for this file.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
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.
No hay un resultado de comprobación guardado.
Collection history, report status and investigation channels
104.21.21.115.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconocido
probe_inconclusive
Accesible
9 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.
Shared hosting, registrar records and related domains
95 dominios similares almacenados
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
stakoex.app)Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.
Este informe presenta la última evidencia almacenada disponible para PhishDestroy. Las marcas de tiempo de origen se muestran cuando están disponibles; La disponibilidad y los veredictos de los proveedores pueden cambiar después de la recolección.
PhishDestroy enumera a stakoex.app como sospechoso. Fue verificado por motores de seguridad 92; Los veredictos automatizados pueden cambiar. El seguimiento continúa. Observado: 2026-10-16 02:39:58 UTC
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
Si cree que esta lista es inexacta, presentar una apelación. Para conocer nuestra metodología, visita el Página de preguntas frecuentes.