Analysis on 24 July 2026 indicates that the domain ccx.capital is currently offline but was previously identified as a brand‑impersonation site targeting Ethereum. The site presented the page title “ChainCapX – Institutional Digital Asset Investment Management,” which suggests an attempt to appear as a legitimate digital‑asset investment service. Registration data shows the domain was created on 21 February 2026 through HOSTINGER operations, UAB, and is hosted on IP address 45.61.157.248, which belongs to AS14956 RouterHosting LLC in the United States. The domain uses the generic parking nameservers ns1.dns‑parking.com and ns2.dns‑parking.com, a pattern frequently observed in malicious‑hosting setups. No SSL certificate is associated with the host, and the HTTP service has been taken offline, limiting immediate interaction but preserving forensic artifacts.
Reputation scoring from Gridinsoft assigned a trust score of 0 out of 100, indicating a complete lack of trust. VirusTotal analysis recorded a single positive detection out of 93 scanned security vendors, confirming at least one vendor flagged the domain as malicious. The domain appears on three independent security blocklists and is explicitly blocked by PhishDestroy, MetaMask, and SEAL, reinforcing its classification as a brand‑impersonation threat. The presence on multiple blocklists and the single VirusTotal detection suggest that while detection coverage is limited, the observed indicators are sufficient to consider the domain hostile.
Uncertainty remains regarding the specific payload or credential‑harvesting mechanisms, as no page content or traffic logs have been released. Defenders should continue to block ccx.capital at network gateways, DNS resolvers, and endpoint security solutions. Monitoring for any re‑registration attempts or changes to the underlying IP address is advised, as threat actors often shift infrastructure after takedown.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ccx.capital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
DOM Analysisanalyzed 2026年4月23日score 10/1003 brand signals
Submitted URLhttp://ccx.capital/
案件 ID
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:09:12 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-03 10:15:50 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-03 10:15:50 UTC → 2026-09-30 16:14:55 UTC · 2,861.98hmidpoint estimate ≈ 2026-08-02 01:15:22 UTC · precision very low · basis bounded
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.
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.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
(LT)
