Before You Register a Domain, Ask Yourself This…
Most people choose a domain based on availability, price, and purpose. But there’s a more critical question: Can you truly trust your registrar and registry to protect your digital property? My experience with the unexpected loss of malaysia.build has forced me to confront this question directly — and it’s one that may be worth every domain owner’s attention.
According to the records and communications I have received, a series of actions involving Namecheap, Enom (Upstream Provider), and the .BUILD Registry coincided with the unexpected removal of my domain malaysia.build. The result was significant disruption and financial impact for me as a registrant.
This website, https://loss.co documents the facts of my experience to create a public record. It is not just about one domain; it is about the principles of security and fairness for every domain owner.
Explore the evidence and decide for yourself!
The Incident: A Removal Without My Request or Consent
On Dec 5, 2023, the domain malaysia.build was removed from my Namecheap account without my request or consent. This discovery was made when attempting to connect the nearly completed real estate platform – a project designed for Malaysia with a paid premium real estate listing feature, developed with significant investment – to its hosting.
The circumstances of this removal are critical:
- Nearly a Decade of Ownership: I registered malaysia.build and maintained active control of the domain for almost ten years, with continuous development and investment throughout that period.
- Active and Paid: Auto-renewal enabled. The domain was fully paid for and valid through April 29, 2024, meaning it still had nearly 5 months before it reached its expiry date, clearly indicating my intent for continuous ownership.
- No EPP Code (per registrar records): Namecheap confirmed in writing (Date: Mon, Jul 14, 2025 at 3:20 PM): “No, according to our logs, the EPP code was not requested.” Under ICANN Transfer Policy §2.1.1, an EPP code is normally part of the transfer process. From my perspective, I was not able to identify evidence that this step occurred in my case
- No Prior Notice (from my perspective): I first learned of the domain transfer after it had already occurred. To the best of my knowledge, I did not receive advance notification from Namecheap, Enom (upstream provider), or the .BUILD Registry about any impending action, such as a restriction, policy violation, or reservation status.
I have owned the malaysia.build domain since 2014 (Whois History).
Below is a screenshot of the renewal receipt (March 30 2023) for the domain malaysia.build.
Active Auto-renewal:
Auto-renewal was active. Please find below a screenshot confirming that Namecheap notified me of a successful auto-renewal (March 30 2021) for malaysia.build.
I have also included a copy of my credit card ending in 0593, which remains active and in regular use.
Below is a screenshot from PayNet confirming that I have been approved to go live with FPX payments on my website.
Proof of Developer Access: Android and iOS Developer Accounts
(Screenshot showing verified access to both Android and iOS developer platforms)
Android
iOS
Since filing my first complaint on June 11, 2025, I have not received a clear resolution from Namecheap, Enom, the .BUILD Registry, or any related party.
According to Namecheap’s response, malaysia.build was described as being in a ‘reserved’ status by the .BUILD Registry (June 21, 2025).
Enom’s email conveyed that the removal was attributed to an ICANN request, creating a conflicting account compared to other communications I received (July 14, 2025).
To the best of my knowledge, I have not received a direct response from the .BUILD Registry, despite being copied on multiple communications.
The differing explanations I received have left me uncertain about the procedural basis for the domain’s removal, particularly given its nearly decade-long period of active registration, auto-renewal enabled and use.
See Responses From Namecheap, Enom, And The .BUILD Registry
The evidence is cataloged here. The structural solution is THE WONG CLAUSE, and it is being institutionalized.
Disclaimer: This website reflects the author’s personal account and opinions regarding the loss of access to the domain *malaysia.build*. The information presented is based on direct experience, contemporaneous records, and a good-faith belief in its accuracy at the time of publication. Mentions of companies, registrars, registries, or other organizations are included only to factually describe events and circumstances relevant to this case. These references are provided solely to factually describe documented events and communications. They should not be read as allegations of misconduct, negligence, or liability of any individual, company, or organization. The content is provided solely for informational and documentary purposes. It does not constitute legal, financial, or professional advice, and should not be relied upon as a definitive statement of fact or legal conclusion.
Corrections Policy: If any party believes that information contained on this website is inaccurate, incomplete, or misleading, they are invited to contact the author at [email protected]. All requests will be reviewed promptly and in good faith. Verified corrections, clarifications, or updates will be published transparently.
Right of Reply: Any registrar, registry, upstream provider, or organization referenced in this website is welcome to submit a written response. Such responses will be published in full, unedited, to ensure fairness and balance.
© 2025 WONG TAI CHIEW. All Rights Reserved.