What happens when a domain disappears, the explanations conflict, and years of complaints fail to produce a satisfactory resolution?

Domain: malaysia.build
Domain removal: December 5, 2023 (MYT)
Loss discovered: June 11, 2025
Published: Oct 27, 2026

I am a Malaysian citizen who registered and paid for malaysia.build for 10 years, from 2014 to 2024. After transferring the domain to Namecheap in 2016, I continued paying for it for eight years and developed a real estate platform around it.

The following documented facts raise questions that I believe deserve public scrutiny.

What Happened?

• Ten years of payments: The domain was paid through April 29, 2024, with auto-renewal enabled.
• Unexpected removal: The domain disappeared from my Namecheap account on December 5, 2023. Why was I not notified?
• No EPP code request: On July 14, 2025, Namecheap confirmed in writing: “No, according to our logs, the EPP code was not requested.” How was the domain transferred or removed without such a request?
• A delayed discovery: I discovered the loss only on June 11, 2025, more than 18 months after the removal. How can a registrant reasonably protect an asset when its disappearance goes unnoticed by the registrant for so long?
• ICANN’s audit: On May 19, 2026, ICANN confirmed that the .BUILD registry operator had improperly released malaysia.build in violation of Specification 5, Section 4 of the Base Registry Agreement. The registry acknowledged the error and deleted the name. What safeguards should prevent such errors from occurring?
• Government approval: In December 2025, MCMC confirmed that no written non-objection had been issued for malaysia.build and concurred with its deletion. What process should apply when a country-name domain is released without the required approval?
• Conflicting accounts: The .BUILD Registry reportedly told eNom on December 1, 2023, that ICANN had “requested” the removal. ICANN later stated that it lacked contractual authority to instruct a registry to release or reserve a name. Who initiated the action, and can the complete decision trail be disclosed?
• A developed platform at stake: The domain was the foundation of a real estate platform built through substantial investment and development work. What recourse is available when a registrant loses a domain and the associated business opportunity?

What Happened After I Complained?

• ICANN Compliance Case #01448650: Filed July 11, 2025. Why has the complaint failed to deliver a satisfactory resolution despite the evidence and repeated escalation?
• Ombudsman escalation: Filed October 1, 2025, and dismissed as “out of scope” after approximately 70 days, despite a stated 3–5-day service level. What effective accountability mechanism remains when an escalation is dismissed?
• No clear compensation route: ICANN stated that its agreements contain no appeal mechanism for registrants in this type of corrective action and no provisions requiring refunds or reimbursement for losses. Where can an affected registrant seek a meaningful remedy?
• Unanswered questions: Despite extensive correspondence and supporting evidence, I have yet to receive a satisfactory, consistent explanation that resolves the central questions.

The 503-Day Wall of ZERO Resolution

For 503 days, I have pursued answers through Namecheap, eNom, the .BUILD Registry, and ICANN’s accountability mechanisms.

How should the public interpret a case in which a domain was removed without notification, a registry violation was subsequently confirmed, the parties’ accounts appear inconsistent, and the registrant remains without a satisfactory resolution?

Does this case demonstrate that existing safeguards are sufficient—or does it reveal gaps in transparency, accountability, and remedies for domain registrants?

Should a registrant who has paid for a domain and invested in developing a business around it have access to a clear explanation, an independent review, and a fair process for seeking compensation?

I present these documented events and questions for readers to examine and assess for themselves.

The question is not simply what happened to malaysia.build. It is whether the domain-name system provides adequate transparency, accountability, and meaningful recourse when something goes wrong.

The 503-Day Accountability Breakdown

The following timeline demonstrates a coordinated institutional failure across every level of domain governance.

• 503 Days of Deflection from Namecheap, Enom & .BUILD Registry, has chosen deflection and procedural evasion over a single, substantive answer

• 473 Days since the ICANN Compliance case was opened

• 391 Days of ICANN Ombudsman involvement resulting in zero investigation

• 364 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

The 26-Minute Miracle: Institutional Silence Broken Only By Press Exposure

For 473 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 → ]

See all 22 Catch-22s here.

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 – 473 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 364 days and counting.

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.”