VirusTotal
14 / 91 engine detections
فتح التقرير“首页”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 2 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
تصيد: cxvdfu.christmas — لم يتم التحقق منها. ملخص الأدلة: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLQuery 1 alert; URLScan…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
14 / 91 engine detections
فتح التقرير1 threat-system alert
فتح التقريرضار
فتح التقرير4 community references
فتح التقريرprovider verdict: clean
فتح التقريرNo threat flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | cxvdfu.christmas |
malicious | Sinkholed |
PhishDestroy threat report
Analysis indicates that the domain cxvdfu.christmas was registered on July 15, 2026 through the registrar Spaceship, Inc. The authoritative name servers launch1.spaceship.net and launch2.spaceship.net resolve the zone to the single IPv4 address 47.242.217.10. The address is currently associated with an active hosting service; no additional infrastructure such as CDN or cloud provider identifiers have been disclosed. The domain has been added to one public security blocklist and is actively blocked by the PhishDestroy sinkhole, confirming that it is recognized as malicious by at least one mitigation platform. VirusTotal reports that the domain was examined by 95 scanning engines, none of which returned a detection.
The absence of detections does not constitute evidence of benign behavior and should be interpreted as a lack of current signatures rather than confirmation of safety. The threat classification is listed as generic phishing, but no further detail about the targeted brand, page title, or phishing kit has been released. Consequently, the exact lure, credential‑capture mechanism, and victim profile remain unknown. The short interval between domain creation (July 15) and the first observed blocklist entry suggests rapid deployment typical of opportunistic phishing campaigns.
Defenders should consider adding cxvdfu.christmas to local URL filtering rules, enforce DNS sinkholing where possible, and monitor outbound traffic for connections to 47.242.217.10. Because the domain is active and the hosting IP is reachable, intrusion‑detection signatures that trigger on HTTP requests to this address can help prevent user exposure. Continuous re‑evaluation is recommended; additional indicators such as HTTP response headers, SSL certificate details, or page content should be collected when the site becomes reachable to refine detection and response measures.
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.
launch1.spaceship.netlaunch2.spaceship.netLocation 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.
cxvdfu.christmas
14/91 engine detections
View source4 community references
View sourcePD-20260722-AB9604
No threat flag
View sourcecxvdfu.christmas
View sourcePage captured
View sourcePD-20260722-AB9604 Recipient: abuse@spaceship.com إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
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 ↗
cxvdfu.christmas)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.