Analysis indicates that cxvsdg.christmas resolves to the IPv4 address 47.242.217.10, which geolocates to Hong Kong. The domain is hosted on nameservers launch1.spaceship.net and launch2.spaceship.net, both associated with the registrar Spaceship, Inc. An HTTP GET returns status code 200, confirming that a web service is actively responding. The domain appears on one public blocklist and is actively blocked by the PhishDestroy feed, which classifies it as a phishing vector. VirusTotal scans have resulted in nine of ninety‑one security vendors flagging the domain as malicious, reinforcing the suspicion of malicious activity. The threat is catalogued as generic phishing with a high risk rating and remains active as of the report date. No additional technical artifacts such as malware hashes, command‑and‑control endpoints, or phishing page content have been released, leaving the exact lure and credential‑harvesting methodology unknown. Defenders should block DNS resolution to cxvsdg.christmas, add the IP address 47.242.217.10 to network‑level deny lists, and ensure that any inbound or outbound traffic to the associated nameservers is inspected or dropped. Continuous monitoring of the IP reputation and periodic rescans on VirusTotal are advised to capture potential changes in detection status.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='cxvsdg.christmas', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-14 10:29:14 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:54 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed First positive detection Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
SOCRadar
Sophos
威胁响应 Pipeline
发现
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(US)
