ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
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.
Analysis indicates that the domain xcb342d.christmas was registered on July 25, 2026 through Spaceship, Inc. and is currently active. The domain resolves to the IPv4 address 47.242.217.10, which is the sole hosting indicator available. DNS resolution is provided by launch1.spaceship.net and launch2.spaceship.net, confirming the use of the registrar’s default nameservers.
The domain has been blocked by the PhishDestroy service and appears on one external security blocklist, demonstrating that at least one third‑party threat feed has identified it as malicious. VirusTotal scans show that seven of ninety‑one security vendors have flagged the domain, providing modest but notable detection consensus across multiple engines. No public SSL certificate details, HTTP status codes, or page title information have been disclosed, leaving the web‑layer characteristics unverified.
The limited visibility into the site’s content means that the exact phishing lure or target brand cannot be confirmed at this time. Defenders should prioritize immediate containment by adding xcb342d.christmas to local blocklists, configuring firewalls to deny traffic to 47.242.217.10, and monitoring DNS queries for the associated nameservers. Continuous re‑evaluation is advised, as additional intelligence such as page title, content hashes, or further vendor detections may emerge, refining the risk posture of this newly created infrastructure.
DOM Analysisanalyzed 2026年7月28日score 98/1001 brand signal
Submitted URLhttp://xcb342d.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.
