VirusTotal
16 / 89 engine detections
فتح التقرير“cxvb325d.christmas”
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.
تصيد: cxvb325d.christmas — لم يتم التحقق منها. ملخص الأدلة: VirusTotal 16/89 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLQuery 1 alert; URLScan…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
16 / 89 engine detections
فتح التقرير1 threat-system alert
فتح التقريرضار
فتح التقريرضار
فتح التقرير4 community references
فتح التقرير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 | cxvb325d.christmas |
malicious | Sinkholed |
PhishDestroy threat report
Analysis indicates that the domain cxvb325d.christmas was registered through Spaceship, Inc. on July 18 2026 and is currently active. The authoritative nameservers launch1.spaceship.net and launch2.spaceship.net resolve the domain to the IPv4 address 47.242.217.10. The domain has been flagged by the PhishDestroy mitigation service and appears on a single external security blocklist, suggesting that at least one threat‑intelligence feed has identified malicious use.
VirusTotal reports that the domain has been scanned by 91 antivirus and URL‑reputation engines, none of which returned a detection at the time of the scan; this absence of detections does not constitute evidence of benign behavior. No public Safe Browsing, Open Threat Exchange, SSL certificate, HTTP status code, or page‑title information is currently available, and no additional evidence links have been published. The limited telemetry points to a classic phishing infrastructure: a recently created domain, dedicated nameservers, and a single IP address that can be easily reassigned.
Defenders should assume that the domain is being used to host credential‑harvesting or other fraudulent pages, even though the exact content has not been observed. Recommended mitigations include adding cxvb325d.christmas to network‑level blocklists, monitoring traffic to 47.242.217.10 for anomalous patterns, and enforcing strict outbound filtering for URLs that resolve to the identified nameservers. Continuous re‑evaluation is advised, as future scans or threat‑intel feeds may provide additional indicators such as malicious payload hashes, SSL anomalies, or observed phishing landing pages.
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.
cxvb325d.christmas
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
يمكن الوصول إليه
4 community references
View source16/89 engine detections
View sourcePD-20260728-5550EA
No threat flag
View sourcePage captured
View sourcecxvb325d.christmas
View sourcePD-20260728-5550EA 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 ↗
cxvb325d.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.