Analysis of www.sdfdsgdsh.christmas indicates the domain was registered on 26 February 2026 through Spaceship, Inc. The authoritative nameservers launch1.spaceship.net and launch2.spaceship.net resolve the host to the IPv4 address 47.242.217.10. The same IP is currently listed on one public security blocklist and the domain is explicitly blocked by the PhishDestroy feed. VirusTotal has recorded detections from two of ninety‑one scanning engines, confirming that the domain has triggered at least minimal malicious indicators. The domain remains active as of the report date, 2 August 2026, and is classified as a high‑risk generic phishing campaign.
No additional intelligence such as page title, SSL certificate details, or observed HTTP response codes is available, so the precise content and targeted brand cannot be confirmed. The lack of publicly disclosed page metadata limits the ability to attribute a specific victim narrative, but the presence on a dedicated phishing blocklist and the detection by multiple security vendors suggest an operational credential‑harvesting infrastructure. Defenders should add the IPv4 address 47.242.217.10 to network‑level deny lists, enforce DNS filtering for the domain, and monitor outbound traffic for connections to the listed nameservers.
Continuous re‑scanning of the host on multi‑engine platforms is advised to capture any evolution of the payload. Organizations using generic phishing detection rules should treat any request to www.sdfdsgdsh.christmas as malicious and block it at the perimeter. Further investigation of the hosting environment and any associated URLs is recommended to fully map the campaign’s scope.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-373948.invalid', port=80): Max retries exceeded with url: / (Caused by
DOM Analysisanalyzed 2026年8月2日score 83/1001 brand signal
Submitted URLhttp://www.sdfdsgdsh.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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:31:44 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:18:17 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-25 01:31:11 UTC
Domain state transitioned from alive to dead.
威胁响应 Pipeline
发现
Analysis
Monitoring
13 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)
