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.
On July 28, 2026, analysis of the domain cv34f3d.christmas identified an active generic phishing infrastructure. The domain was registered on July 18, 2026 through Spaceship, Inc., using the authoritative name servers launch1.spaceship.net and launch2.spaceship.net. DNS resolution points to the IPv4 address 47.242.217.10, which remains reachable as of the report date. The domain is listed on one public security blocklist and has been blocked by the PhishDestroy sinkhole, indicating that at least one defensive platform has observed malicious traffic associated with the host.
VirusTotal records show that the domain was scanned by 91 antivirus and URL‑analysis engines, none of which have raised a detection at the time of scanning. While the lack of detections does not imply benign intent, it confirms that the domain has not yet triggered automated signatures in the examined vendor set. No additional intelligence such as Safe Browsing verdicts, Open Threat Exchange references, SSL certificate details, HTTP response codes, or trust‑score metrics were available for this host. Given the recent creation date, the presence on a blocklist, and active resolution to a public IP, the infrastructure is likely being used to host phishing pages or to relay malicious traffic.
Defenders should add cv34f3d.christmas to URL filtering rules, monitor DNS queries for the two launch*.spaceship.net name servers, and consider network‑level blocking of the associated IP address. Continuous re‑scanning with multi‑engine services is recommended to capture any future changes in detection status. Incident response teams should treat any communications originating from this domain as suspicious and verify user credentials through out‑of‑band channels before proceeding.
DOM Analysisanalyzed 2026年7月28日score 98/1001 brand signal
Submitted URLhttp://cv34f3d.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.
