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.
Security analysis of yftul.christmas covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
15 / 91 engine detections
보고서 열기1 threat-system alert
보고서 열기악성
보고서 열기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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | yftul.christmas |
malicious | Sinkholed |
AI-assisted evidence review
Analysis of yftul.christmas as of July 28 2026 shows a newly created domain (registered 5 June 2026) hosted by Spaceship, Inc. The authoritative nameservers launch1.spaceship.net and launch2.spaceship.net resolve the domain to the single IPv4 address 47.242.217.10. VirusTotal has recorded eight detections out of ninety‑one scanned vendors, indicating that multiple security products have flagged the domain as malicious. The domain is currently listed as active and has been added to at least one public security blocklist; it is also blocked by the PhishDestroy mitigation service, which suggests that defensive communities have observed phishing‑related activity originating from this host.
No public SSL certificate information, HTTP response codes, Safe Browsing verdicts, or Open Threat Exchange (OTX) reports are available for the domain at this time, and the page title has not been disclosed. Consequently, the precise phishing landing page content and any credential‑harvesting mechanisms remain unknown. Defenders should continue to enforce network‑level blocks for the IP address 47.242.217.10 and add yftul.christmas to local deny lists.
Monitoring of DNS queries for the two launch*.spaceship.net nameservers is advised, as any sudden changes could indicate infrastructure shifts. Because the domain is already flagged by multiple vendors and appears on blocklists, intrusion‑detection signatures that reference the domain name or its IP should be deployed. Ongoing telemetry collection from endpoint agents and web proxies will help capture any future payloads or URLs that may be associated with this campaign.
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.
접속 가능
15/91 engine detections
View source4 community references
View sourcePage captured
View sourcePD-20260728-A4F724
No threat flag
View sourceyftul.christmas
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
yftul.christmas
PD-20260728-A4F724 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 ↗
yftul.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
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.