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.
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-19 01:08:09 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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
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
ccx.capital
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(LT)
