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.
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.
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.
(US)
