VirusTotal
6 / 92 engine detections
打开报告钓鱼: hekodex.com — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 6/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); PhishDestroy score…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 92 engine detections
打开报告3 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
hekodex.com is on the PhishDestroy blocklist as a suspicious domain. It has not yet been tied to a specific scam type or impersonated brand. PhishDestroy first flagged it on 2026-10-07, only days after it was registered. As of 2026-10-19 the domain was still live, and visitors who load it are redirected elsewhere instead of seeing content hosted on the domain itself.
The danger sits in the redirect. Anyone opening hekodex.com ends up at a destination the domain owner can change at any time, so the same link can lead to different pages from one day to the next. The "dex" in the name echoes the naming common in crypto trading services, which would make it easy to share as a trading or swap link. No specific scheme has been confirmed. The realistic risk is that a visitor lands on a page that asks for a wallet connection, a signature, a deposit or login details.
On 2026-10-19, VirusTotal showed 6 of 92 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That count is modest, but these six vendors flagged it independently of PhishDestroy's own listing. The domain also appears in three AlienVault OTX threat pulses, meaning other researchers have tagged it in shared threat reporting. Among the blocklists covered here, PhishDestroy is currently the only one listing it.
The domain was registered on 2026-10-03 through Fewmoretaps OU, which trades as Trustname.com. It was on our blocklist four days later, a short gap that is typical of throwaway domains set up for a single campaign. It resolves to Cloudflare's network in the US, which hides the server that actually hosts the site. The Let's Encrypt certificate gives the site a padlock in the browser, but that only means the connection is encrypted and says nothing about whether the site is safe.
Do not open or share hekodex.com, and treat any message promoting it as untrustworthy. If you connected a wallet after being redirected, review what you signed and revoke any approvals you gave to unfamiliar contracts. If you sent funds, move your remaining assets to a fresh wallet. If you typed a password or seed phrase, change the password, turn on two-factor authentication, and treat the seed phrase as compromised. Defenders should block the domain at DNS and proxy level and watch for redirect chains that start from it.
Edge-IP 声誉不属于此域。
teagan.ns.cloudflare.comLocation describes the IP network.
2506f18ca207e685dcb5d1fc65a210602140d7f1ba6304478fb68ff7373f74afSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
1→2
未知→redirected
http_redirect
No threat flag
View source6/92 engine detections
View source3 community references
View sourcehekodex.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
hekodex.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
hekodex.com)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.