Analysis indicates that the domain gfhn435.christmas was registered on July 23, 2026 through Spaceship, Inc. and is currently active. The domain is delegated to the nameservers launch1.spaceship.net and launch2.spaceship.net, and resolves to the IPv4 address 47.242.217.10. Infrastructure profiling shows that the domain appears on one public security blocklist and has been actively blocked by the PhishDestroy service, confirming that threat‑mitigation tools are already flagging it.
VirusTotal scans report that eight of ninety‑one security vendors have marked the domain as malicious, providing additional corroboration of its risk profile. No public Safe Browsing, Open Threat Exchange, SSL certificate, or HTTP status information is available in the current intelligence set, and the page title or any brand‑specific references have not been disclosed. Given the limited but consistent evidence—registration timing, resolver IP, blocklist presence, and multiple vendor detections—defenders should treat gfhn435.christmas as a high‑risk phishing vector.
Recommended mitigation steps include adding the domain and its resolving IP to local and network‑level blocklists, monitoring outbound DNS queries for the domain, and updating intrusion‑detection signatures to incorporate the observed indicator set. Continuous re‑evaluation is advised, as further reconnaissance may reveal additional payload or hosting characteristics that could refine detection rules.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='gfhn435.christmas', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
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:30:27 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:58 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: 15 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
SOCRadar
Sophos
VIPRE
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Threat First Observed2026-07-28 00:24:25 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 47.242.217.10.
威胁响应 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)
