跳转到安全报告
分析仪表盘
域安全和威胁情报
stakodefi.org favicon

stakodefi.org

“STAKO”

注册商
Cloudflare
Resolved IP
188.114.96.3
Registered
2026年10月13日
威胁判定 高
可用性 未验证 当前可达性未经验证 观察到
Source: HTTP probe
风险信号
存储的阻止列表匹配项：2 品牌冒充：Aave 年轻域名：不到一天
OTX: 3 refs 2026年10月13日 Aave CDN
API
该域名已被标记为恶意域名
报告匹配的公共黑名单：2。 请格外小心——不要输入凭据或个人信息。
报告概览

stakodefi.org — 未验证. 品牌冒充：Aave. 证据摘要: VirusTotal 0/92; URLScan capture; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 66/100. 注册商: Cloudflare.

为保留原始取证记录，下方的 PhishDestroy AI 详细分析仍使用英文。

OTX references
3 community refs
URLScan
URLScan
报告 ↗
TLS 证书
已过期或未验证
年龄
<1 day Brand New!
PhishDestroy
DestroyList
已列入

Source evidence

5 sources

VirusTotal

checked — no detections recorded

报告

OTX

3 community references

报告

CF雷达

provider verdict: suspicious

报告

URLScan capture

存储的报告

报告

Google Safe Browsing

Checked; no threat flag recorded

报告

证据摘要

高
OTX
3 community refs
URLScan
Stored capture

Assessment

stakodefi.org was observed on 2026-10-13 with a PageSpeed performance score of 85, documenting its technical optimization at that time. The domain also appeared in the PhishDestroy internal listing, providing a catalogue entry for reference.

Recorded Evidence

VirusTotal checked stakodefi.org on 2026-10-13, recording 0 detections out of 92 scanners. OTX documented three pulses for the domain on the same date. The PhishDestroy internal listing included stakodefi.org as of 2026-10-13. Registration was recorded with Cloudflare, Inc., and the SSL certificate was issued by Let's Encrypt / YE2, both noted on 2026-10-13.

Interpretation

The PhishDestroy internal listing contains a catalogue record for stakodefi.org, documenting its inclusion for reference. VirusTotal provides a scan-based measurement, offering a snapshot of detection results from multiple security engines. OTX records pulse activity, which may reflect external intelligence entries relevant to the domain. These sources collectively provide a technical and intelligence-based overview, with each record capturing a distinct aspect of the domain's profile.

Recommended Actions

For stakodefi.org, preserve the VirusTotal scan record and OTX pulse entries for ongoing comparison with future intelligence sources. Retain the PhishDestroy internal listing as a reference for catalogue status. Review PageSpeed performance records periodically to monitor changes in technical optimization.

探测与规避分析

隐身和流量分配检查

尚未扫描 目前尚未记录到爬虫与浏览器之间的差异

针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。

存储的隐身标志
尚未扫描
捕获路由
Local 存档于 2026-10-13 17:54:32 UTC
TDS指纹识别实时演示
七个Keitaro指纹，外加爬虫与浏览器的对比，当此面板打开时，由PhishDestroy扫描器运行。
等待

已保存的截图 · 1 capture

Primary capture 1 / 1
来源Primary capture
Recorded2026-10-13 15:53 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://stakodefi.org/
Position1 / 1
Open capture Wayback 下载

Domain details

域名
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX Tags 2026-10all-domainsblocklistcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 Cloudflare US(US)
滥用举报联系方式["registry-abuse@cloudflare.com"]
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询stakodefi.org 的 ICANN RDAP →
注册信息创建 2026年10月13日 (0d · Brand New!) — Expires 2027年10月13日
技术详情Provenance & timestamps
首次发现2026年10月13日
DOM Analysisanalyzed 2026年10月13日score 10/1006 brand signals
Submitted URLhttp://stakodefi.org/
Favicon Hash
页面标题
STAKO
Impersonates
Aave Across Ethereum Near Sui Ups
TLS 证书
Hostname coverage not recorded · 颁发者 Let's Encrypt / YE2 · stored validity ends in 89 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP 声誉不属于此域。

域名服务器 2

  • betty.ns.cloudflare.com
  • razvan.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / YE2
Valid from
2026-10-13 07:45:38
Valid until
2027-01-11 07:45:37
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-13 16:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint51b52060bea627cf7dbbf720e7756bc25fedd75c87e4eb4da51f11bcd3a77ce4

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

viewdns.info · 188.114.96.3rapiddns.io

Latest Classified Outcome 2026-10-13 15:53:51 UTC

Primary outcome 未知 reason: Probe Inconclusive 20% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation 未知 Probe Inconclusive 20% 2026-10-13 15:53:51 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-13 15:53:51 UTC
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.
技术 · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人
网站性能分析

Google PageSpeed Insights — mobile performance audit of stakodefi.org · checked Oct 13, 2026

85
Needs Work
Performance
FCP
1.67s
First Contentful Paint
LCP
1.67s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
239ms
Total Blocking Time
SI
10.99s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://stakodefi.org/
Final URL: https://stakodefi.org/
STAKO
响应
HTTP 200
HTML body
4.2 KB
Compressed
1.7 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a49f85fb3a8fb240-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Tue, 13 Oct 2026 15:54:31 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=WVLWeHH38mvd6nA2%2Bh7D5bZvVqPANaF8%2Bvr4E9UG7I4dj2WjIESPq9jSal%2F2esxNJUasDeOGWRe8fn%2BWu545SKF4C%2BhcENJKyfoYUb6txN2FV4kXiwtfOuG1yPEUP67Y"}]}
Server
cloudflare
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Archived

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-10-13 15:53:51 UTC
    Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.

威胁响应 Pipeline

发现
Analysis
Monitoring

9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

已捕获威胁
stakodefi.org 已检测到并排入队，待进行全面分析
2026年10月13日
URLScan.io Capture
已存储 URLScan report with capture artifacts
2026年10月13日
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
黑名单检测
见于 2 blocklists: MetaMask, SEAL
2026年10月13日
OTX Community References
3 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Brand Impersonation
Impersonation of Aave
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
2026年10月13日
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月13日
DestroyList 已发布
Listed in the public PhishDestroy/DestroyList repository
2026年10月13日
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web Symantec网站评审 AviraURL reporting Avast / AVGURL reporting 卡巴斯基OpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

公共封禁名单状态

仿冒域名

已存储 95 个仿冒域名

aavef.com addition 内部报告 xn--ave-ila.com homoglyph 内部报告 1ave.com replacement a1ve.com replacement a2ve.com replacement aa.ve.com subdomain aaev.com transposition aage.com replacement aav4.com replacement aavi.com vowel-swap aavo.com vowel-swap aavr.com replacement
显示全部（83）
aavs.com replacement aavw.com replacement aove.com vowel-swap auve.com vowel-swap avae.com transposition awve.com replacement ayve.com replacement azve.com replacement oave.com vowel-swap save.com replacement uave.com vowel-swap wave.com replacement 1aave.com insertion 2ave.com replacement a-ave.com hyphenation aa6e.com bitsquatting aaave.com repetition aabe.com replacement aace.com replacement aacve.com insertion aare.com bitsquatting aate.com bitsquatting aauc.com homoglyph aaue.com homoglyph aav.com omission aav3.com replacement aava.com bitsquatting aavbe.com insertion aavc.com homoglyph aavce.com insertion aavd.com bitsquatting aavec.com addition aaved.com addition aavee.com addition aaveg.com addition aavek.com addition aavel.com addition aaven.com addition aaveo.com addition aaveq.com addition aaver.com addition aaves.com addition aavet.com addition aavex.com addition aavey.com addition aavg.com bitsquatting aavm.com bitsquatting aavu.com bitsquatting aavve.com repetition aavz.com replacement aawe.com bitsquatting acve.com bitsquatting aeve.com bitsquatting aive.com bitsquatting aqave.com insertion aqve.com bitsquatting asave.com insertion asve.com replacement ave.com omission awave.com insertion ayave.com insertion azave.com insertion cave.com bitsquatting eave.com bitsquatting iave.com bitsquatting qaave.com insertion saave.com insertion waave.com insertion xn--80aap9w.com cyrillic xn--aa-g7r68c.com homoglyph xn--aa-g7r83g.com homoglyph xn--aav-5qa.com homoglyph xn--aav-mra.com homoglyph xn--ae-dla019z.com homoglyph xn--ae-dla4955b.com homoglyph xn--ae-dla6031a.com homoglyph xn--ae-e5s275e.com homoglyph xn--ae-tfb535y.com homoglyph yaave.com insertion yave.com replacement zaave.com insertion aavea.com addition aavew.com addition

证据与外部报告

证券分析
URLScan Stored capture VirusTotal ChainPatrol URLQuery SSL 实验室 Hostname coverage not recorded CF雷达 打开报告 OTX 3 refs WOT ScamAdviser 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
OSINT与情报分析
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox 哈德逊岩 Sign-in search IntelX crt.sh 证书 WHOIS Wayback
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析

您是否受到本网站的影响？

3 evidence signal groups linked 0 reports recorded 未验证
If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息，或者从此域下载了文件，请立即采取措施。以下资源可帮助您报告事件并保护自己。

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

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

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息，确保安全

请实时监控威胁，或者如果您认为这是误报，请对该条目提出异议

实时威胁动态 对该列表提出异议
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/stakodefi.org"
  title="PhishDestroy threat report for stakodefi.org"
  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>