According to this post, it has been confirmed that their server was forcibly shut down without any notice due to a complaint ticket filed with 1984 Hosting. It’s both funny and saddening, because it highlights how easy it is to destroy any service hosted by a provider that claims to prioritize privacy and security—no need to bypass their DDoS firewall, no hacking skills required. Simply opening an 'abuse ticket' is enough to force an immediate shutdown without warning or accountability. This is far more efficient than a DDoS attack, which only causes disruption for hours or, at most, days.
What’s even more ironic is that, on XMRBazaar’s own forum, I recall a user suggesting just days ago that the current XMRBazaar setup was risky. They proposed migrating the domain to a more protective provider like njal.la while keeping the hosting with 1984 to prevent the entire site from being taken in one go. This way, attackers would have to target both the domain registrar and the server to shut down the service. Little did we know, it would all happen so soon—possibly exactly as the user warned, leaving us unable to reclaim the domain and server.
Additionally, XMRBazaar’s server setup wasn’t robust enough—it relied too heavily on a single point of failure without proper backups or redundancy. If they had followed a model like Mail2Tor, where the service operates a complete setup within the Onion network, the situation would have been different. Even if their domain (mail2tor.com) was canceled by Namecheap, the service wouldn’t have become completely inaccessible. The server behind the .onion address would still allow users to access emails. Later, they simply launched a new domain (mail2tor.email), and everything was resolved.
If XMRBazaar returns, or if the market sees a replacement emerge, I think we really need to prioritize reliability. Monero’s developers are incredibly creative, so any tech miracles aren’t out of the question. What’s needed now is a long-term, robust future.
