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; 13 days 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.
mefnex.sbs is an impersonation phishing site on a throwaway .sbs domain. It is built to pass itself off as a legitimate service and harvest what visitors type into it. PhishDestroy first flagged it on 2026-10-06. As of 2026-10-19 the domain was still live, but its DNS was inactive, so it was not serving content. It can be repointed to a working page at any time.
How the scam works
Impersonation pages copy the look of a service the victim already trusts, then ask for a login, recovery details or wallet secrets under a plausible pretext such as verification or account recovery. Anything submitted goes straight to the operators, who use it to take over accounts or empty funds. The page title showed only "Loading", while we classified the site as impersonation phishing.
Evidence
On 2026-10-13, 13 of 92 VirusTotal engines marked the domain as malicious. They include alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a broad spread of independent vendors for a domain this young. Spamhaus lists it in its Domain Block List under the spam category, so mail filters relying on that feed will treat it as hostile. It also appears in four AlienVault OTX threat pulses, and it is listed on the PhishDestroy blocklist.
Infrastructure
The domain was registered through Spaceship, Inc. on 2026-08-05, roughly two months before we detected it. That gap fits a domain bought and held in reserve before being put to use. It resolved to 46.29.26.38 on a network announced by M/S Robi Traders, a Bangladeshi operator, with the address located in Finland. A cheap .sbs name on far-flung hosting is typical of disposable phishing setups that are easy to abandon and replace.
What to do
If you entered a password on this site, change it immediately on the real service and anywhere you reused it. Then turn on app-based two-factor authentication and sign out other active sessions. If you typed a seed phrase or private key, treat that wallet as compromised and move the remaining funds to a new wallet created on a clean device. Watch for follow-up messages that reference your visit, since operators often return with fake support offers. Security teams should block mefnex.sbs at DNS and the mail gateway, and search proxy logs for earlier visits. Keep the block in place even while the DNS is inactive, because the domain is still registered and can come back.
DOM Analysisanalyzed 2026年10月9日score 98/1004 brand signals
Submitted URLhttps://mefnex.sbs/
Favicon Hash
ケース ID
SHORTDOTゾーン · 公開証拠.sbs
ShortDot zone evidence
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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:06:39 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-09 10:07:09 UTClast content: 2026-10-09 10:07:09 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 10:07:09 UTC → 2026-10-09 20:20:42 UTC · 10.23hmidpoint estimate ≈ 2026-10-09 15:13:55 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)
