On 24 July 2026 investigators examined the domain com-en-uk.support, which was registered on 6 March 2026 through Spaceship, Inc. The domain resolves to the Amazon Web Services address 34.216.117.25, ASN 16509, located in the United States. No TLS certificate is presented; HTTP requests return a generic “Parking Page” title. The nameservers launch1.spaceship.net and launch2.spaceship.net are consistent with the registrar’s infrastructure. Threat intelligence categorises the site as a tech-support phishing operation.
VirusTotal scans show that two of ninety-four AV engines flagged the domain, and three independent blocklists (PhishDestroy, MetaMask, SEAL) have already listed it. The domain’s current status is offline, indicating that the hosting content has been removed or the site is otherwise inaccessible. The evidence points to a short-lived infrastructure typical of opportunistic phishing campaigns: a recent registration, use of a cloud provider without SSL, and rapid blocklist inclusion.
Because the domain is already taken offline, immediate mitigation actions focus on ensuring that existing blocklists remain active and that any residual DNS or IP-based indicators are added to local deny lists. Continuous monitoring of the 34.216.117.25 address and the associated nameservers is recommended, as the attacker may repurpose the same resources for future campaigns. Defenders should also watch for new domains registered through Spaceship, Inc. that share the same naming pattern, as this registrar has been used in related incidents.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='com-en-uk.support', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
DOM Analysisanalyzed 2026年7月29日score 63/1001 brand signal
Submitted URLhttp://com-en-uk.support/
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:16:18 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:53 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.
12 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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)
