URLScan verdict
malicious
SignalerThis is the recorded automated analysis. Completion alone is not a safety verdict.
“STAKO”
Assessment based on the stored source evidence below. Review sources →
stakoex.com — Non vérifié. Usurpation de l'identité de la marque : Aave; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 0/92; URLScan malicious verdict; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 90/100. Bureau d’enregistrement: Cloudflare.
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique 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.
malicious
SignalerThis is the recorded automated analysis. Completion alone is not a safety verdict.
2 external matches
DétailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
checked — no detections recorded
SignalerEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
4 community references
SignalerCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: suspicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
rapport stocké
View stored capture ↗ SignalerA preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
SignalerA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
stakoex.com was observed with a VirusTotal check on 2026-10-16, which recorded 0 detections from 92 scanners. The domain was also listed on two external blocklists as of the same date, providing additional context for its security profile.
On 2026-10-16, VirusTotal reported 0 detections out of 92 scanners for stakoex.com. The domain appeared on the MetaMask and SEAL external blocklists on 2026-10-16. PhishDestroy included stakoex.com in its internal listing as of 2026-10-16. The domain was registered with Cloudflare, Inc. on 2026-10-13.
The VirusTotal record contains a scan-based measurement, documenting the absence of detections from its participating scanners on the recorded date. The MetaMask and SEAL blocklist entries represent external security references, while the PhishDestroy internal listing provides another perspective on the domain's profile. These dated records together offer a snapshot of stakoex.com’s observed status from multiple sources.
For ongoing assessment of stakoex.com, preserve the VirusTotal scan results and external blocklist entries for future comparison. Review the PhishDestroy internal listing periodically to track any changes in the domain’s recorded security profile. Use these source records to inform further technical reviews or network policy decisions regarding stakoex.com.
21 · datasets with records / 10 · 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. · 172.67.180.232 · DNS, TLS and retained responses
La réputation Edge-IP n’est pas attribuée à ce domaine.
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
03e3c6ef9bc44ba277f48ab82c9c47e72a588724d8d7afed44fb8ce545b6f9e4Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
down.stakoex.comDomain recordwww.stakoex.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of stakoex.com · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://stakoex.com/https://stakoex.com/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400DYNAMICa4b37845cd137af0-IADkeep-alivegziptext/htmlFri, 16 Oct 2026 02:00:25 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=EEhjqqhWJleQyTBJ2OiH%2Bwixi09XJegFgREq4weFxHVnk88yxwwQUA608P8Jz9b6uAVQfc3TUnKEhmJcuCMX9Owald0KAe3P1Ih6K%2BTk2b%2BkPACGW4oPsz8TkK3Vig%3D%3D"}]}cloudflarecfCacheStatus;desc="DYNAMIC"max-age=31536000chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
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
Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.
Local archivé le 2026-10-16 02:00:26 UTCAucun résultat de vérification enregistré.
Collection history, report status and investigation channels
172.67.180.232.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu
probe_inconclusive
Accessible
10 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 domaines ressemblants enregistrés
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 vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
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.com)Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.
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
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
Ce rapport présente les dernières preuves stockées disponibles pour PhishDestroy. Les horodatages sources sont affichés lorsqu'ils sont disponibles ; la disponibilité et les verdicts des fournisseurs peuvent changer après la collecte.
Le site capturé affichait le titre de la page “STAKO” et usurpait peut-être l'identité de Aave.
PhishDestroy répertorie stakoex.com comme suspect. Il a été vérifié par les moteurs de sécurité 92 ; les verdicts automatisés peuvent changer. La surveillance se poursuit. Observé: 2026-10-16 03:10: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 vous pensez que cette liste est inexacte, déposer un recours. Pour en savoir plus sur notre méthodologie, visitez le Page FAQ.