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.
DOM Analysisanalyzed 2026年7月28日score 98/1001 brand signal
Submitted URLhttp://yftul.christmas/
Favicon Hash
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
