VirusTotal
13 / 91 engine detections
فتح التقرير“yurft.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.
تصيد: yurft.christmas — لم يتم التحقق منها. ملخص الأدلة: VirusTotal 13/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); URLQuery 2…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
13 / 91 engine detections
فتح التقرير2 threat-system alerts
فتح التقريرضار
فتح التقرير4 community references
فتح التقريرprovider verdict: clean
فتح التقرير80/100
فتح التقرير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 indicates that the domain yurft.christmas was registered on 19 May 2026 through Spaceship, Inc. 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 infrastructure has been observed on a single security blocklist and is actively blocked by the PhishDestroy feed. VirusTotal scans show that seven of ninety‑one participating security vendors have flagged the domain as malicious, reinforcing the classification of generic phishing.
The high risk rating aligns with the observed detection activity and the fact that the domain is still resolvable. Available intelligence does not include SSL certificate details, HTTP response codes, page title, or any observed payload. Consequently, the precise phishing vector, targeted brand, or credential‑capture mechanism remains undocumented. Defenders should treat the domain as hostile and block network traffic to the associated IP address and DNS name.
Updating perimeter firewalls, DNS filtering solutions, and endpoint protection with the indicator of compromise (IOC) – domain name and IP – is recommended. Continuous monitoring of the IP reputation and any emerging detections on additional blocklists will help to capture potential expansion of the campaign. Organizations using PhishDestroy or similar threat‑intel feeds should ensure the feed is applied to email gateways and web proxies to prevent user exposure. Given the recent registration date, the domain may be part of a fast‑flux or short‑lived phishing operation; therefore, periodic re‑assessment of the domain’s status is advisable.
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.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
يمكن الوصول إليه
13/91 engine detections
View source4 community references
View sourcePD-20260728-A0B60D
Page captured
View sourceNo threat flag
View sourceyurft.christmas
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
yurft.christmas
PD-20260728-A0B60D 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 ↗
yurft.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.