URLScan verdict
malicious
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
“STAKO”
Assessment based on the stored source evidence below. Review sources →
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
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
2 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
checked — no detections recorded
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA 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
ReportA 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.
The domain stakobit.com was observed on 2026-10-16 with entries on both the MetaMask and SEAL external blocklists, providing a dated indicator of its listing status. A PageSpeed performance score was also recorded on the same date, contributing additional technical context for this domain.
On 2026-10-16, stakobit.com was listed on the MetaMask and SEAL external blocklists. VirusTotal checked the domain on 2026-10-16, reporting 0 detections out of 92 total scanners. PhishDestroy internally listed the domain, and OTX referenced it in 4 pulses as of 2026-10-16. The domain was registered with Cloudflare, Inc. on 2026-10-13, and a PageSpeed performance score of 45 was recorded on 2026-10-16.
PhishDestroy contains an internal listing for stakobit.com, which documents its presence in a specialized monitoring system. VirusTotal provides a measurement of how many security scanners detected issues with the domain, while OTX records its mention in multiple intelligence pulses. These records offer a cross-section of how the domain is referenced and evaluated across several security and intelligence sources.
Preserve the blocklist entries for stakobit.com from MetaMask and SEAL for ongoing reference. Retain the VirusTotal scan results and OTX pulse records to compare with future security intelligence. Maintain the internal listing from PhishDestroy to track any updates or changes in its assessment. Use these source records as benchmarks for future monitoring and evaluation.
19 · datasets with records / 12 · 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.196.94 · DNS, TLS and retained responses
Edge-IP reputation is not attributed to this domain.
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
Saved 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.stakobit.comDomain recordwww.stakobit.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of stakobit.com · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://stakobit.com/https://stakobit.com/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400DYNAMICa4b37c994bf10261-CDGkeep-alivegziptext/htmlFri, 16 Oct 2026 02:03:22 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=J0doq8iC4H05JisLK58qL3kXTFZNALzL1fckQtfDyR3puBRLIGopDAH39xQ1V1hFasJ023LKCqGVa7ryt%2Bcej54LStlzzzIRoP2JwrLc5tyubDtmP4PM%2BqqFU9kuhHU%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
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Local archived 2026-10-16 02:03:23 UTCNo live-check result has been retained.
Collection history, report status and investigation channels
172.67.196.94.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown
probe_inconclusive
Reachable
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 stored lookalike domains
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
stakobit.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “STAKO”. Apparent target: Aave.
Stored VirusTotal result for stakobit.com: 92 engines checked. Observed: 2026-10-16 03:10:55 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.
submit an appeal or review the FAQ page.