VirusTotal
0 / 92
engines flag the domain
“VelocityDEX - High-Frequency Trading DEX”
0 / 92
engines flag the domain
No threat flag
Not on Google threat lists at check time
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 188.114.97.1 · TLS: Google Trust Services
Each check shows its own collection time. Zero detections do not guarantee safety.
冒充 Google: velocitydex.org — 未验证. 证据摘要: VirusTotal 2/92 (Forcepoint ThreatSeeker, SOCRadar); PhishDestroy score 81/100. 注册商: Namecheap.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
2 / 92 engine detections
打开报告4 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
velocitydex.org is an impersonation phishing page that presents itself as "VelocityDEX - High-Frequency Trading DEX." It is aimed at crypto traders looking for a fast decentralized exchange. PhishDestroy first flagged it on 2026-10-08. On 2026-10-19 the site was still responding, though DNS for its content had gone inactive, so the page may reappear or move.
Fake DEX fronts like this rely on the language of speed and professional trading to make a wallet connection feel routine. Once a visitor connects, the page can ask for token approvals or transaction signatures that look like ordinary trading steps. In practice these approvals let the operator move the approved assets out of the wallet. Some variants also push direct deposits into a supposed trading balance that can never be withdrawn. The victim loses whatever tokens were approved or sent, often without seeing an obvious warning.
Independent detection is thin. On 2026-10-16, only 2 of 92 VirusTotal engines flagged the domain: Forcepoint ThreatSeeker and SOCRadar. PhishDestroy is the only blocklist carrying it. It appears in 4 AlienVault OTX threat pulses, which shows other researchers have tied it to malicious activity. Most security tools will not stop a visitor yet, which makes a clean scan result here misleading.
The domain was registered through Namecheap on 2026-07-02, roughly three months before PhishDestroy detected it. That gap is consistent with a domain left to age before the campaign went live. The site sits behind Cloudflare's network, with the hosting location listed as Canada, so the real origin server is hidden from view. Its certificate comes from Google Trust Services, which means the padlock in the browser says nothing about whether the site is legitimate.
If you connected a wallet to velocitydex.org, review and revoke any token approvals granted around that session using a reputable approval checker. Then move remaining funds to a fresh wallet if you signed anything you did not fully understand. Never re-enter a seed phrase on any site claiming to restore access. If you deposited funds, do not pay any "unlock" or withdrawal fee, because that money will be lost too. Defenders should block the domain at DNS and proxy level, watch for lookalike VelocityDEX domains, and report it to Cloudflare and Namecheap abuse teams.
Edge-IP 声誉不属于此域。
harmony.ns.cloudflare.comtrace.ns.cloudflare.comLocation describes the IP network.
c4526bb99f1e66e698ae98110bdbf1f81277f53343e759e0de17c9ca08196f07Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of velocitydex.org · checked Oct 8, 2026
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.
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
可访问
No threat flag
View source2/92 engine detections
View source4 community references
View sourcevelocitydex.org
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
velocitydex.org
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 ↗
velocitydex.org)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.