VirusTotal
15 / 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.
تصيد: cvdf34d.christmas — لم يتم التحقق منها. ملخص الأدلة: VirusTotal 15/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLScan malicious…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
15 / 91 engine detections
فتح التقريرضار
فتح التقريرضار
فتح التقريرchecked — no detections recorded
فتح التقرير4 community references
فتح التقريرNo threat flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis of cvdf34d.christmas shows an active malicious infrastructure that was registered on July 22, 2026 through Spaceship, Inc. The domain resolves to the IPv4 address 47.242.217.10 and is served by the authoritative name servers launch1.spaceship.net and launch2.spaceship.net. VirusTotal records indicate that 2 of 91 scanned security vendors have flagged the domain as malicious, and the domain appears on a single external security blocklist. PhishDestroy has already listed the domain as blocked, confirming that defensive feeds are actively mitigating traffic to this host.
No public information on SSL certificates, HTTP response codes, or page titles is currently available, and the site’s content has not been captured in open‑source intelligence. The limited detection footprint suggests a newly deployed phishing campaign that relies on rapid domain turnover; the short registration window (one day before the report) aligns with typical fast‑flux tactics used to evade reputation accrual. Defenders should immediately add 47.242.217.10 to network deny lists, enforce DNS‑level blocking of cvdf34d.christmas, and monitor for any additional domains registered by Spaceship, Inc. that resolve to the same name servers.
Continuous re‑scanning on VirusTotal and integration of blocklist updates are recommended to capture any future vendor detections. Given the high‑risk classification and active status, organizations are advised to treat any communications referencing this domain as hostile and to educate users about the potential phishing attempt.
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.
cvdf34d.christmas
15/91 engine detections
View source4 community references
View sourcePD-20260723-8C3A0F
No threat flag
View sourcecvdf34d.christmas
View sourcePage captured
View sourcePD-20260723-8C3A0F 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 ↗
cvdf34d.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.