VirusTotal
14 / 89 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.
انتحال Google: cxvdf45df.christmas — لم يتم التحقق منها. ملخص الأدلة: VirusTotal 14/89 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLQuery 1 alert…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
14 / 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 | cxvdf45df.christmas |
malicious | Sinkholed |
PhishDestroy threat report
Analysis as of July 28 2026 indicates that cxvdf45df.christmas is an active domain that has been identified as a phishing site. The domain was registered on July 23 2026 through Spaceship, Inc., and its authoritative nameservers are launch1.spaceship.net and launch2.spaceship.net. DNS resolution points to IP address 47.242.217.10. The domain appears on a single security blocklist and is blocked by PhishDestroy.
VirusTotal scanning shows that 1 of 91 security vendors flagged the domain, providing independent detection evidence. No additional public threat‑intel sources such as OTX or Google Safe Browsing are listed in the supplied data, and no SSL certificate, HTTP response codes, or page title information have been disclosed, leaving those aspects unverified. The limited detection footprint suggests a newly created infrastructure that may be used in targeted phishing campaigns, but the scarcity of observations also limits confidence in the scope of the operation. Defenders should add the domain to internal blocklists, monitor DNS queries to 47.242.217.10, and enforce outbound filtering for traffic to the identified nameservers.
Continuous re‑scanning with VirusTotal and other sandbox services is recommended to capture any evolution in the payload. Because the registration date is only five days prior to the report, rapid domain turnover is likely, so automation that expires or quarantines newly observed domains after a short dwell time can mitigate exposure. Until further intelligence on the hosted content or SSL fingerprint becomes available, the precautionary stance should treat the domain as high‑risk.
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.
cxvdf45df.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 source14/89 engine detections
View sourcePD-20260728-2C22F8
Page captured
View sourceNo threat flag
View sourcecxvdf45df.christmas
View sourcePD-20260728-2C22F8 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 ↗
cxvdf45df.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.