The following sections detail the proven, documented breaches by each entity involved in the unauthorized deletion of malaysia.build. These are not allegations. They are factual conclusions drawn from email correspondence, official statements, and procedural records. Together, they illustrate a coordinated systemic failure where every accountability mechanism designed to protect registrants collapsed.
Namecheap’s Documented Failures: A Summary of Proven Breaches
Introduction:
The following points are not allegations. They are conclusions drawn from Namecheap’s own email correspondence, timestamps, and internal contradictions. Each represents a breach of their contractual, fiduciary, or ethical duty to the registrant.
The Documented Failures:
-
Payment Without Disclosure: Accepted renewal payments for years while allegedly knowing the domain violated policy, without ever notifying the registrant.
-
Deletion Without Due Process: Removed the domain 5 months before expiry without providing any of the ICANN-mandated expiration or redemption notices (ERRP violation).
-
No Safeguards Followed: Confirmed no EPP code was issued, no warnings given, and no redemption path offered—voiding all standard registrar safeguards.
-
Contradictory Explanations: Provided irreconcilable statements—claiming a “transfer out” while admitting no EPP was used and later denying any involvement.
-
Refusal to Escalate: Explicitly refused to escalate the issue to ICANN Compliance, abandoning its duty as the registrar of record to challenge the registry.
-
Premature Abandonment: Issued a final denial from its Legal Department and then unilaterally closed all communication, abandoning the customer.
-
Systematic Deflection: Consistently shifted all responsibility to upstream providers and the registry, denying its own role as the accountable contractual partner.
-
Acknowledgment Without Remedy: Admitted the registrant “may [have] losses” while refusing to confirm any financial responsibility, demonstrating bad faith.
-
Withholding of Evidence: Failed to produce a single piece of corroborating evidence (audit notice, internal logs, policy citation) after nearly 6 months of requests.
Conclusion:
These nine points, documented from Namecheap’s own communications, form a clear pattern of institutional failure. They demonstrate that the loss of malaysia.build was not an isolated error, but the result of a systemic breach of trust and contract by the registrar.
Call to Action:
For the complete email record and timeline supporting each point above, see the full evidence page: Namecheap’s Complete Response Record.
eNom’s Documented Failures: The Passive Conduit
Introduction:
eNom’s actions, as documented in its sole communication and subsequent silence, demonstrate a failure to fulfill its role as a responsible intermediary in the domain service chain.
The Documented Failures:
-
Provision of a Contradictory Justification: eNom’s only response forwarded an unverified registry email claiming “ICANN requested” the deletion, creating the core contradiction that ICANN later denied having the authority to do.
-
Total Communication Blackout: After its one email on July 14, 2025, eNom ceased all communication, ignoring multiple follow-ups including a formal 48-hour deadline, thereby abandoning the case.
-
Failure to Verify or Challenge: As an experienced reseller, eNom acted as a passive conduit, failing to independently validate the registry’s serious claim before passing it to the registrant.
-
Abrogation of Responsibility: By instructing the registrant to “contact the registry directly,” eNom attempted to offload its investigative duty, violating its position in the service hierarchy.
Conclusion:
eNom’s conduct transformed it from a service provider into a mere passer of unsubstantiated information, followed by complete withdrawal, exacerbating the opacity and unaccountability of the process.
Call to Action:
See the direct communication record showcasing eNom’s singular response and subsequent silence: eNom’s Communication Record.
.BUILD Registry’s Documented Failures: The Silent Judge
Introduction:
The .BUILD Registry, as the entity that executed the deletion, has maintained absolute silence. Its documented actions and inactions represent the most direct and unaccountable exercise of power in this case.
The Documented Failures:
-
Complete and Unbroken Silence: Despite being the alleged author of the deletion and copied on all communications, the Registry has never responded to any inquiry, email, or online form submission.
-
Failure to Produce Evidence: The Registry has never provided the alleged 2023 audit report, violation notice, or specific policy citation that justified deleting a 9-year-old asset.
-
Provision of a Contradictory Reason: The Registry’s email to eNom claimed ICANN requested the removal—a statement that created the central contradiction of the case and has never been clarified.
-
Total Lack of Due Process: The Registry acted as judge, jury, and executioner, deleting the domain without prior notice, opportunity to contest, or any defined appeal mechanism for the registrant.
Conclusion:
The .BUILD Registry’s silence is not passive; it is an active refusal to be accountable. It executed a final, harmful action and then insulated itself from all questioning, embodying absolute, unanswerable authority.
Call to Action:
Review the registry’s only known statement and the record of its silence: .BUILD Registry’s Role.
ICANN Contractual Compliance’s Documented Failures: The Bureaucratic Facade
Introduction:
ICANN Compliance, tasked with enforcing policy and ensuring fair process, delivered 131 days of contradictions, procedural obstruction, and an admission of a system without remedy. Its ultimate “detailed response” was an evidence-free conclusion that validated institutional power over registrant rights.
The Documented Failures:
-
Issuing Logically Contradictory Statements: Compliance stated ICANN has “no authority” to order a deletion, directly contradicting the Registry’s claim that it was “requested by ICANN,” and dismissed this as a semantic issue.
-
Providing Inconsistent Key Facts: Compliance gave contradictory dates for the alleged audit (October 2023 vs. August 2023), undermining its own narrative.
-
Engaging in Procedural Obstruction: It employed “Catch-22” tactics, rejecting evidence on format while defining scope to exclude the registrant’s core complaints about notice and due process.
-
Admitting Systemic Failure Without Remedy: Its final response admitted the domain was deleted due to a Registry “error” and that there is “no appeal mechanism” for registrants, acknowledging a framework where victims bear 100% of the loss.
-
Responding Only to External Pressure: After 117 days of delay and ignored deadlines, Compliance issued a substantive response only within 9 hours of the registrant launching a public campaign and GAC complaint.
-
Issuing an Evidentiary Vacuum as a “Detailed Response”: The long-awaited substantive reply contained zero case-specific evidence—no audit excerpts, notifications, or logs for
malaysia.build—making it a conclusory assertion, not an investigative finding. -
Substituting Generic Policy Links for Case-Specific Proof: The response directed the registrant to generic audit reports, deliberately omitting the specific documents that would substantiate the claims against the domain, a tactic of obfuscation.
-
Withholding the Central Document to Perpetuate Contradiction: Compliance has refused to provide the communication where the Registry claims it was “requested by ICANN,” thereby maintaining the core, unresolved contradiction that it is contractually obligated to investigate.
-
Failing Its Basic Investigative Mandate: Presented with a direct contradiction between contracted parties, Compliance abdicated its duty to determine non-compliance, instead dismissing the issue to avoid holding either the Registry or its own organization accountable.
Conclusion:
ICANN Compliance functioned not as a protector of policy and fairness, but as a bureaucratic shield for the contracted parties. It used procedure to avoid substance, admitted its framework offers no justice, and ultimately provided a “resolution” devoid of the evidence required to make it credible. Its conduct represents the total failure of ICANN’s primary enforcement mechanism.
Call to Action:
Examine the 131-day timeline of delays, contradictions, and Catch-22s: ICANN Compliance Complete Timeline.
ICANN Ombudsman’s Documented Failures: The Guardian Who Stood Down
Introduction:
The ICANN Ombudsman’s office, designed as an independent fairness check, became ensnared in and enforced the very procedural barriers it should have broken, failing to act in the face of a 117-day institutional stall.
The Documented Failures:
-
Enforcing a Procedural “Catch-22”: The Ombudsman refused to investigate, citing a rule requiring a “conclusion” from Compliance first—making it impossible to address the core complaint of Compliance’s refusal to conclude.
-
Prescribing Delay as a Cure for Delay: In response to a 119-day delay complaint, the office proposed its own 120-day SLA timeline, weaponizing procedure to avoid substantive action.
-
Violating Its Own Service Standards: The office repeatedly missed its published 3-5 business day response deadline following escalations.
-
Failing to Act as an Independent Check: It adopted a passive “waiting for Compliance” stance instead of proactively challenging the delay or contradictions.
-
Failing to Answer Direct Questions: It did not answer a list of 10 direct, procedural questions regarding its own conduct and the process failures.
-
Issuing Empty Acknowledgments in Lieu of Action: Following a November 20, 2025 escalation, the Ombudsman’s only action was a November 22 acknowledgment email—a procedural formality not followed by any investigation. The stated 3-5 business day SLA expired on November 28 and was silently ignored, constituting a documented refusal to investigate the deletion of a G20 sovereign-name domain.
-
The “26-Minute Miracle”: Proof the System Responds Only to Reputation, Not Justice: After 161 days of the Ombudsman and Compliance ignoring detailed evidence, the registrant escalated to the global press on November 18 at 11:32 PM. The Ombudsman responded at 11:58 PM—just 26 minutes later. This irrefutably proves ICANN’s accountability mechanisms are not designed to solve problems based on evidence, but to silence them when the organization’s public image is threatened.
Conclusion:
The Ombudsman’s office proved to be a structurally weakened component, its own rules preventing it from acting when needed. The “26-Minute Miracle” is the definitive evidence that internal accountability is a facade. The system is calibrated to respond to external pressure, not internal fairness—validating the central thesis of this dispute.
Call to Action:
See the documented 49-day deadlock, procedural Catch-22s, breached SLA and the timestamped proof of the “26-Minute Miracle”: ICANN Ombudsman Email Trail.
ICANN Board of Directors’ Documented Failures: The Ultimate Accountability Vacuum
Introduction:
The ICANN Board of Directors, vested by its Bylaws with “ultimate responsibility” for ICANN’s mission and oversight, was directly and repeatedly notified of the 131-day systemic failure in the malaysia.build case. Its documented response—total silence—represents not a neutral position, but an active endorsement of the institutional collapse occurring beneath it.
The Documented Failures:
-
Complete Silence Despite Direct Escalation: The Board maintained total, unbroken silence despite receiving detailed escalations on October 28, November 1, November 3, November 4, and November 5, 2025, which documented the failure of all subordinate accountability mechanisms.
-
Violation of Its Own Bylaws on Oversight: The Board’s Bylaws charge it with the “oversight of the performance of the IANA functions and ICANN’s operations.” Its inaction in the face of a 131-day operational failure by Contractual Compliance and the Ombudsman constitutes a direct failure to execute this mandated duty.
-
Passive Complicity via Inaction: The Board’s only discernible action was to forward correspondence back to the very departments (Compliance, Ombudsman) that had already demonstrably failed. This passive shuffling deepened the procedural Catch-22s rather than resolving them.
-
Endorsement of a Broken Accountability Framework: By taking no action while copied on the Ombudsman’s “Catch-22” and Compliance’s contradictory statements, the Board signaled that such systemic dysfunction is acceptable within ICANN’s governance model.
-
Failure to Protect DNS Stability and Trust: The Board’s mission includes promoting the stability and reliability of the Internet’s identifier systems. Its silence in a case that sets a precedent for the unannounced, retroactive deletion of long-held domains directly undermines that stability and the trust of all registrants.
Conclusion:
The ICANN Board’s profound silence is the capstone of the accountability collapse. It demonstrates that ultimate governance authority is rendered meaningless when those in charge refuse to exercise it, opting instead for institutional self-preservation over the stewardship of a fair and stable system.
Call to Action:
Review the timeline of escalations and the Board’s documented non-response: ICANN Board Escalation Timeline.
Final Synthesis: A Coordinated System-Wide Collapse
This comprehensive documentation reveals a system not of isolated failures, but of orchestrated dysfunction. Each party’s action or inaction—Namecheap’s deflection, eNom’s passivity, the Registry’s silence, Compliance’s contradictions, the Ombudsman’s powerlessness, and the Board’s abdication—complemented the others to create an impenetrable barrier to accountability. The result is a precedent where the registrant, acting in good faith for a decade, bears the total cost for institutional errors, without due process, without evidence, and without remedy.
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.