TOTAL TIME OF ZERO RESOLUTION
Since My First Complaint to Namecheap
Live Forensic Audit: Started June 11, 2025, at 15:48:00
December 2025 Update:
- Public reporting indicates Namecheap is undergoing a majority-ownership transition involving CVC Capital Partners. The matter documented on this site remains unresolved as of Day 359.
Sources:
- I’ve received formal acknowledgment from the Arizona Attorney General’s Office confirming receipt and intake of my consumer complaint regarding the malaysia.build domain matter (Complaint Reference: CIC# 25-020223).
- In addition to the previously noted filings, my report to the U.S. Federal Trade Commission has been formally logged under Consumer Sentinel (Report #195289817).
- As part of my complaint, I called attention to Namecheap’s dismal D- rating with the BBB. This rating is a direct consequence of the company ignoring over 150 previous complaints. The evidence is publicly available on their BBB profile: https://www.bbb.org/us/az/phoenix/profile/web-hosting/namecheap-1126-1000045547. Screenshot: https://loss.co/images/bbb-rating-against-namecheap.png
- Malaysia Government Confirms “malaysia.build should never have been registered in the first place”
Malaysia’s official regulator (MCMC / GAC) has spoken — and placed 100 % of the fault on ICANN’s system failure.
This is no longer a dispute. This is an officially acknowledged governance collapse.
[ LEARN MORE → ]
The Case of malaysia.build: A Documented Systemic Failure
A domain lawfully registered and developed for over nine years was taken without warning, without due process, and without a single accountable party providing a resolution or a clear explanation.
Domain: malaysia.build
Status: Unauthorized removal in December 2023 (No EPP code, no prior notice)
The 359-Day Wall of Silence: For 359 days, through complaints, evidence, and escalation, the response from Namecheap, eNom, the .BUILD Registry, and ICANN’s own accountability mechanisms has been one consistent, unwavering message: complete and total silence. This coordinated silence from all parties is not an absence of response—it is the systemic answer. It means accountability is a facade, and registrants have no recourse when the very system designed to protect them fails. The silence itself is the verdict.
Result: Complete Systemic Failure of ICANN’s accountability framework.
Published: Jun 6, 2026

The Namecheap Failure That Proves My 15-Year Loyalty Meant Nothing
As the registrar of record and direct recipient of payment, Namecheap bears fundamental responsibility for the loss of the domain. Their core function was to ensure the domain remained secured in the account, particularly with auto-renewal enabled and payment collected. This duty of care included providing standard safeguards such as an EPP code for transfers, advance notification of any changes, and a clear explanation of any alleged violation—none of which were fulfilled. The registrant was left to discover the deletion independently. It is unequivocally NOT the registrant’s responsibility to navigate complex upstream provider relationships or contact various internet governance bodies; that duty falls squarely on the registrar, who serves as the customer’s sole point of contact. The comprehensive failure to fulfill these basic service obligations, while retaining payment, constitutes a fundamental breach of their contractual and fiduciary duty, placing the largest share of accountability for damages directly on Namecheap.
For nearly 15 years (Sep 1, 2010 – Jun 11, 2025), I entrusted Namecheap with my digital infrastructure. At its peak, my account held a portfolio of nearly 600 domain names. I was not a novice user or a one-time customer; I was a bedrock of their business, a testament to the trust I placed in their service.
This long-term partnership and significant revenue stream make their subsequent actions not just a service failure, but a profound betrayal. They did not merely fail a random customer; they systematically failed a loyal asset, demonstrating that no one, regardless of tenure or value, is safe from their negligence and abandonment.
15 Years of Business History — Now Publicly Verified
To demonstrate my longstanding reliance on Namecheap, I have published verifiable proof of our 15-year transaction history and the size of my past portfolio. The video is live and accessible to regulators, press, and governance bodies:
See https://youtu.be/_fR9ETHZiSM
(With English auto-translated subtitles)
The $15,000-a-Year Question Namecheap Won’t Answer
Why would a company systematically dismantle a 15-year client relationship worth an estimated $15,000 per year? The documented transaction history and renewal math reveal the staggering financial miscalculation behind Namecheap’s negligence. This was not a simple error; it was a catastrophic business decision.
Ironically, the Thanksgiving weekend (Black Friday and Cyber Monday) I once anticipated ACTIVELY for Namecheap’s biggest promotions has now become a permanent memorial to their betrayal, transforming me from a loyal “whale” customer into someone who will never again look at their offers.
See the Verifiable Financial Breakdown and Evidence Here
This demonstrates that the impact on me is not theoretical — it is quantifiable, documented, and ongoing.
* While this analysis focuses on Namecheap’s primary responsibility, this does not absolve other parties of their failures. The complete breakdown across the entire ecosystem – including Enom’s communication blackout, the .BUILD Registry’s silence, and ICANN’s procedural failures – is documented in detail on the respective case pages. However, as the registrar of record and the party that accepted direct payment, Namecheap bears the ultimate responsibility to the customer for managing these relationships and ensuring service delivery.
The 359-Day Accountability Breakdown
The following timeline demonstrates a coordinated institutional failure across every level of domain governance.
-
359 Days of Deflection from Namecheap, Enom & .BUILD Registry, has chosen deflection and procedural evasion over a single, substantive answer
-
329 Days since the ICANN Compliance case was opened
-
247 Days of ICANN Ombudsman involvement resulting in zero investigation
-
220 Days since escalation to the ICANN Board of Directors with zero response
-
15+ Formal Deadlines set by the registrant, all ignored
-
0 substantive responses received after providing comprehensive evidence
From Institutional Silence to Global Scrutiny
On Nov 18 2025, simultaneous dual-track escalation to both international governance bodies and global media:
International Bodies Escalation
-
Formal notifications sent to ASEAN, APEC, OECD, ITU, UN IGF, INTERPOL Cybercrime, G20 Digital Economy Working Group
-
Complete escalation details: https://loss.co/international-escalation/
Global Press Notification
-
Comprehensive press kit distributed to 80+ international media outlets including Bloomberg, Reuters, Associated Press, TechCrunch, and major Malaysian press
-
Full press notification record: https://loss.co/global-press-notification/
This global notification is a key maneuver in an ongoing campaign that will not cease until this systemic failure is rectified.
The 26-Minute Miracle: Institutional Silence Broken Only By Press Exposure
For 329 days, ICANN Compliance and the Ombudsman ignored detailed evidence of contradictory deletion policies.
On Nov 18 at 11:32 PM, I escalated the case to the Global Press.
On Nov 18 at 11:58 PM—exactly 26 minutes later—the Ombudsman reached out.
This confirms the central thesis of this dispute: ICANN’s accountability mechanisms function only when the organization’s reputation is threatened. The system is not designed to solve problems; it is designed to silence them.
See my Nov 20 at 8:23PM reply.
Another Broken Deadline (SLA 3-5): Ombudsman’s Empty Response
Following my November 20th escalation, the Ombudsman’s only action was a November 22nd acknowledgment email—a procedural formality that has not been followed by any meaningful investigation or response.
SLA 3-5 business days (expired 28 Nov) → SLA extension silently ignored repeatedly. This is no longer delay; it is an official, documented refusal to investigate a G20 sovereign-name deletion.
Driving the Final Nail – ICANN Ombudsman “Out of Scope” Finding Double Confirms Systemic Collapse
Full email from the ICANN Ombudsman (9 Dec 2025) and entire correspondence thread:
See https://loss.co/ombudsman-board-complete-email-trail/#9121249
[ LEARN MORE → ]
Direct Comparison of Quotes from MCMC and Ombudsman Emails
Why the Ombudsman’s “Out of Scope” Decision Is Incorrect and Contradictory
[ LEARN MORE → ]
Additional Catch-22 #23 found after Ombudsman’s email dated Dec 15, 2025.
Catch-22 #23 — Endless Redirection Loop. This latest referral adds a new one to the list: the complainant is sent in perpetual circles to mechanisms that explicitly cannot help, creating the appearance of options while ensuring no actual review ever occurs.
Note on Confidentiality:
On November 7, 2025, I explicitly waived all confidentiality regarding this case in writing to the Ombudsman’s office. This email was received subsequent to that waiver. As this dispute involves the unauthorized deletion of a G20 sovereign nation’s domain name and systemic governance failures, there is no expectation of privacy. All correspondence is maintained as part of the public record.
Why Every Party Failed
Every single accountability mechanism designed to protect registrants failed completely.
→ For the detailed evidence of each failure, visit the dedicated case pages:
-
Why Namecheap Failed – Engaged in a circular blame game, claiming to be ‘waiting for upstream providers and .build registry’. When this failed, they escalated the case to their legal department, which issued a final denial of all responsibility and prematurely closed the case, severing all communication without providing a resolution.
-
Why Enom Failed – Provided one email, then total communication blackout.
-
Why .BUILD Registry Failed – Absolute silence; never responded to a single communication.
-
Why ICANN Compliance Failed – 329 days of delays, contradictory statements, Catch-22s and eventual silence.
-
Why the Ombudsman Failed – Trapped by a procedural Catch-22s, enabling the delay instead of investigating it.
-
Why the ICANN Board Failed – Ultimate authority, yet complete silence for 220 days and counting.
Fundamental Due Process Was Ignored
| What Should Have Happened | What Actually Happened |
|---|---|
| Prior notification of violation | ZERO notification |
| Opportunity to contest deletion | ZERO opportunity |
| An explained appeal process | ZERO process provided |
| Evidence of violation presented | ZERO evidence shown |
| EPP code for transfer | No EPP code was issued |
| Grace period before deletion | Deleted 5 months before expiry |
This isn’t a policy dispute—it’s a complete absence of natural justice.
A Real Project, Real Investment, Real Loss
malaysia.build was an active, advanced real estate platform, not an abandoned domain.
-
30+ months of full-time development
-
Progressive Web App (PWA) & mobile applications
-
Integrated FPX Payment Gateway (PayNet approved)
-
Live Demo: https://malaysia.sibu.design
-
Video Demonstrations: https://loss.co/videos
Documented damages include the loss of a 9-year+ digital asset, 30+ months of development work, lost revenue, and severed business partnerships.
Why This Matters to You
If this precedent stands, no domain is safe.
A domain you have owned for a decade can be deleted based on a retroactive “audit” without:
-
Prior Notice
-
Due Process
-
Evidence
-
Appeal Rights
-
Any Accountability
This case proves the entire system is structured to protect institutions at the complete expense of the registrant.
The Escalation Precedent: This case has now been elevated to the highest levels of international internet governance and global media scrutiny. The complete documentation of both the institutional failures and the escalation process serves as a blueprint for other registrants facing similar systemic abandonment. When accountability mechanisms fail, public transparency and international pressure become the only remaining recourse.
“WHEN EVERY PARTY IN THE ACCOUNTABILITY CHAIN FAILS SIMULTANEOUSLY, IT’S NOT COINCIDENCE — IT’S SYSTEMIC INSTITUTIONAL FAILURE.”
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.