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.
تصيد: jkuis.christmas — لم يتم التحقق منها. ملخص الأدلة: VirusTotal 15/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 1 alert…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
15 / 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 | jkuis.christmas |
malicious | Sinkholed |
PhishDestroy threat report
Analysis of the domain jkuis.christmas, created on July 15, 2026, indicates active malicious infrastructure supporting a generic phishing campaign. The domain is registered through Spaceship, Inc. and resolves to the IP address 47.242.217.10. DNS resolution is served by launch1.spaceship.net and launch2.spaceship.net, both of which belong to the same registrar and suggest a rapid provisioning workflow typical of short‑lived phishing sites. The domain has been flagged by the PhishDestroy blocklist and appears on one additional security blocklist, confirming that at least one external threat‑intel source has observed malicious activity associated with this hostname.
VirusTotal records show that the domain was scanned by 95 antivirus and URL‑reputation engines; none of the engines returned a detection, but the absence of a positive result does not constitute a safety assurance, especially given the confirmed blocklist presence. No public page title, SSL certificate details, HTTP response codes, or Safe Browsing verdicts are currently available for jkuis.christmas, and no brand or specific scam kit identifiers have been disclosed. Consequently, the precise phishing vector—such as credential harvesting, credential‑only login pages, or credential‑plus‑malware delivery—remains uncertain. Defenders should treat the domain as hostile until further forensic evidence clarifies the payload.
Recommended mitigation steps include adding the domain and its resolving IP address to network‑level deny lists, updating DNS filtering policies to block queries to launch1.spaceship.net and launch2.spaceship.net when associated with this hostname, and monitoring inbound traffic for connections to 47.242.217.10. Continuous re‑evaluation of VirusTotal and other sandbox analyses is advised, as future scans may reveal malicious payloads that were not present at the time of the initial assessment.
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.
jkuis.christmas
15/91 engine detections
View source4 community references
View sourcePD-20260722-3C0911
No threat flag
View sourcejkuis.christmas
View sourcePage captured
View sourcePD-20260722-3C0911 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 ↗
jkuis.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.