ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
fortcrown.top is an impersonation phishing site built to pass itself off as a legitimate service and harvest whatever its visitors trust it with. PhishDestroy first flagged it on 2026-09-16. As of 2026-10-19 the domain still responded, but the phishing content was no longer being served because its DNS had gone inactive.
How the scam works
Impersonation pages copy the look, wording and flow of a real brand so closely that a visitor arriving from an ad, a direct message or a search result does not notice the swap. The page then asks for something valuable, such as a login, a verification code, personal details or a wallet recovery phrase, and sends it straight to the operators. Visitors lose account access, and in crypto cases the funds behind the stolen credentials. The page title read only "Loading", a generic placeholder that does not name any brand, while we classify the site as impersonation phishing.
Evidence
Six of 91 VirusTotal engines flagged the domain as of 2026-09-29: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, SOCRadar and VIPRE. That is a modest count, but the six are independent vendors from different parts of the security industry. Spamhaus lists the domain in its DBL under the spam category, so mail and DNS filters that use that list will block it. It also appears in four AlienVault OTX threat pulses, which means other researchers have tied it to malicious activity, and it is on the PhishDestroy blocklist.
Infrastructure
The domain was registered through Spaceship, Inc. on 2026-06-06, roughly three months before we detected it. A gap like that often means the domain was held in reserve before use. It was hosted on the M/S ROBI TRADERS network in Turkey. Its Let's Encrypt certificate gave it a padlock in the browser, which proves only that the connection was encrypted, not that the site was genuine.
What to do
If you typed a password on this site, change it immediately on the real service and on any other account that uses the same password. Then enable app-based two-factor authentication and sign out of all active sessions. If you entered a wallet recovery phrase, treat that wallet as compromised and move any remaining assets to a new wallet created on a clean device. Watch for follow-up messages pretending to be support, because operators often contact victims a second time. Defenders should block fortcrown.top at the DNS and mail gateway, search logs for any internal visits since 2026-09-16, and reset credentials for affected users.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-20 10:12:11 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-09 10:20:30 UTClast content: 2026-10-09 10:20:30 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 10:20:30 UTC → 2026-10-09 20:20:42 UTC · 10.00hmidpoint estimate ≈ 2026-10-09 15:20:36 UTC · precision medium · basis bounded
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.
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)
