VirusTotal
1 / 93 engine detections
فتح التقرير“ChainCapX - Institutional Digital Asset Investment Management”
انتحال Ethereum: ccx.capital — المحتوى غير متوفر. ملخص الأدلة: VirusTotal 1/93 (SOCRadar); PhishDestroy score 55/100. مسجّل النطاق: Hostinger.
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
1 / 93 engine detections
فتح التقريرchecked — no detections recorded
فتح التقريرno community references
فتح التقريرprovider verdict: clean
فتح التقريرNo threat flag
فتح التقريرPage capture
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
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.
ns1.dns-parking.comns2.dns-parking.comLocation describes the IP network.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
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
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
https://radar.cloudflare.com/scan/e8e98058-b5c6-41e1-aed1-80a46773522a
Page captured
View sourceNo threat flag
View source1/93 engine detections
View sourceccx.capital
View sourcePD-20260202-B72523
٥٢ نطاقًا متشابهًا محفوظًا
أبلغ عنه عضو واحد في المجتمع؛ شوهد أول مرة في 02/02/2026
PD-20260202-B72523 Recipient: abuse@hostinger.com Registrar: Hostinger Operations UAB (Lithuania (EU)) Policy Violations: AUP prohibits illegal activity including fraud, phishing, malware hosting; Hostinger may suspend/terminate services and domains Applicable Laws: Lithuanian Criminal Code (Ch. XXX, §§196–198 data/system crimes; §§214–215 electronic fraud); EU Directive 2013/40/EU
إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
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 ↗
ccx.capital)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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
تحليل التهديدات باستخدام قائمة الحظر المخزنة، وWHOIS، وDNS، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب
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.