PILLAR A — KNOWLEDGE, VALIDATION, AND INDUCED RELIANCE
(Findings showing Namecheap knowingly accepted, validated, monetized, and allowed reliance on the domain.)
Finding 1: Acceptance and Validation of a Prohibited Asset (2016 Transfer)
What happened:
In 2016, Namecheap accepted the inter-registrar transfer of malaysia.build into its system. Transfer acceptance requires active validation and eligibility checks. Namecheap did not flag, reject, or reserve the domain at that time.
Why it matters:
If the domain was truly prohibited under Specification 5, Namecheap had a duty to reject it. Accepting the transfer is an affirmative act of validation, not passive custody. This undermines any later claim that the domain should never have existed.
Finding 2: Continuous Monetization Despite Alleged Ineligibility
What happened:
From 2016 through 2023, Namecheap billed and collected renewal fees eight times, including auto-renewals tied to an active payment method.
Why it matters:
A registrar cannot lawfully profit from an asset for years and later claim it was invalid all along. This establishes knowing monetization and long-term reliance, incompatible with good-faith compliance.
Finding 3: Allowing Nearly Eight Years of Reliance Without Warning
What happened:
For almost eight years, Namecheap provided standard registrar services with no warnings, no reservation notices, and no indication that the domain was at risk.
Why it matters:
This conduct created legitimate, vested reliance. Silent acceptance over many years forecloses the argument that the registrant bore the risk of sudden deletion.
Finding 4: Deletion of a Paid, Active Domain Without Notice
What happened:
In December 2023, Namecheap removed malaysia.build despite it being fully paid through April 29, 2024. No prior notice or opportunity to respond was provided.
Namecheap stated on July 13, 2025: “Yes, the transfer out was processed from our database on 12/4/2023.”
Why it matters:
Removing a paid digital asset without notice constitutes unauthorized deprivation, not routine compliance enforcement.
Finding 5: Admission of No EPP Code With No Follow-Up
What happened:
On July 14, 2025 (3:20 PM), Namecheap confirmed: “According to our logs, the EPP code was not requested.”
No explanation, audit, or remediation followed.
Why it matters:
Under ICANN policy, a transfer cannot occur without an authorization code. An active domain leaving an account without one signals a core security breakdown, which Namecheap never investigated.
PILLAR B — AWARENESS OF HARM FOLLOWED BY CONSCIOUS INDIFFERENCE
(Findings showing Namecheap recognized harm and risk, then disengaged.)
Finding 6: Acknowledgment of Harm Followed by Immediate Abandonment
What happened:
On July 13, 2025 (10:29 PM), Namecheap stated: “We completely agree that this may cause losses to your company.”
On July 15, 2025 (11:09 PM), the support ticket was closed without resolution or mitigation.
Why it matters:
Acknowledging foreseeable harm creates a duty to act responsibly. Closing the case immediately afterward reflects conscious indifference, not customer support.
Finding 7: Prolonged Delay Attributed to “Upstream” That Proved Untrue
What happened:
From June 11 to July 14, Namecheap repeatedly claimed it was “waiting for updates from upstream providers (eNom).”
I politely suggested faster alternatives (phone call, Zoom, WhatsApp) on July 12, 2025 — ignored.
On July 14, 2025 (10:19 PM), I contacted eNom directly.
At July 14, 2025 (10:49 PM), eNom responded in just 30 minutes, provided the December 1, 2023 registry directive.
Why it matters:
Namecheap treated a 15-year whale customer with open contempt for the customer’s intelligence with their fabricated ‘waiting for upstream’ stall tactic. While they wasted 35 days claiming eNom hadn’t responded, I contacted eNom directly and received the critical registry directive in just 30 minutes — proving the information was always readily available. Their entire delay narrative was demonstrably false and unsupported by the facts: either Namecheap failed to make any meaningful effort to contact eNom, or it withheld readily available information in a manner that predictably frustrated and exhausted the registrant.
Finding 8: Inconsistent and Shifting Technical Explanations
What happened:
• July 12: “Investigating how and why the domain was transferred”
• July 14: “Most likely transferred” / “No EPP code requested”
• July 15 (Shift Lead): The responsible party in this case is the .Build Registry. Only the Registry can provide answers to your questions…
• July 15 (Legal): “Executed at registry level”
Why it matters:
These are contradictions on a core fact, not clarifications. They indicate either no coherent investigation or explanations tailored to deflect responsibility.
PILLAR C — PROCEDURAL ABDICATION, MISREPRESENTATION, AND STONEWALLING
(Findings showing abandonment of registrar duties and systemic disengagement.)
Finding 9: Refusal to Escalate to ICANN Despite Clear Grounds
What happened:
When asked to escalate the registry action to ICANN, Namecheap replied: “We are not considering this option at the moment.”
Why it matters:
Registrars are the registrant’s contractual intermediary. Refusing escalation in a case involving asset removal and procedural irregularities constitutes abdication of registrar responsibility.
Finding 10: Misleading Progression on Compensation
What happened:
• July 13: Acknowledged potential losses
• July 14: Suggested compensation depended on outcome
• July 15: Declared total non-responsibility
Why it matters:
This sequence creates false reliance, delays escalation, and then withdraws accountability—a classic placation-then-denial pattern.
Finding 11: Legal Department’s Contractual Abdication
What happened:
On July 15, Namecheap Legal stated it had “no involvement” and redirected responsibility solely to the .BUILD Registry.
Why it matters:
Under the ICANN RAA, the registrar is the registrant’s single point of accountability:
Specifically Section 3.3.3, it is clearly stipulated:
“Registrar may subcontract its obligation… provided that Registrar shall remain fully responsible for the proper provision of the access and updating.”
Redirecting blame contradicts the entire ICANN accountability framework.
Finding 12: Strategic Silence After Formal Final Demand
What happened:
After July 15, 2025—particularly following my detailed September 26, 2025 demand—Namecheap ceased responding entirely, despite clear questions and deadlines, to date Jun 6, 2026, these questions remain unanswered.
- Did Namecheap formally contact Enom and the .build Registry regarding my domain loss? If YES, provide the complete email chain, including Enom’s and the Registry’s replies. If NO, explain why Namecheap repeatedly stated it was awaiting Enom’s and Registry’s response.
- What proactive steps did Namecheap take to notify me as registrant before the domain was removed? Please provide records of such attempts.
- Why was my complaint closed prematurely without explanation? Who authorized this closure, and under what grounds?
- Given that the domain was paid for, active, and under Namecheap’s safeguard, what does Namecheap accept as its responsibility in this failure?
- How does Namecheap justify profiting from my payment while failing to safeguard the domain? From my perspective, this constitutes a breach of trust and contractual obligation.
Why it matters:
Extended silence in the face of documented allegations functions as tacit admission that no defensible explanation exists.
Finding 13: Administrative Closure Without Resolution
What happened:
The support thread was closed while core issues—loss of asset, security failure, financial harm—remained unresolved. Subsequent communications were ignored.
Why it matters:
Closing a case without resolution reflects a corporate decision to disengage, not a completed investigation.
PILLAR D — SYSTEMIC ACCOUNTABILITY AND REGULATORY ESCALATION
(Findings showing systemic corporate failure and the involvement of external regulatory bodies.)
Finding 14: Dismal Public Trust and Ignored Consumer Feedback
-
What happened: Namecheap maintains a D- rating with the BBB, driven by over 150 ignored complaints.
-
Why it matters: This establishes a pattern of systemic neglect. The loss of malaysia.build is not an isolated incident but part of a documented corporate culture that deprioritizes consumer rights and complaint resolution.
Finding 15: Formal Intake by State and Federal Regulators
-
What happened: The Arizona Attorney General (Complaint: CIC# 25-020223) and the FTC (Report #195289817) have formally logged the malaysia.build matter.
-
Why it matters: This elevates the case from a private contract dispute to an active investigation into unfair and deceptive business practices under state and federal law.
Finding 16: Misrepresentation During Ownership Transition
-
What happened: While undergoing a majority-ownership transition with CVC Capital Partners, Namecheap has allowed a major unresolved liability to persist for over 200 days.
-
Why it matters: Failing to resolve significant claims during an acquisition can be interpreted as a failure of corporate transparency, potentially affecting the valuation and terms of the transition.
Finding 17: Official Acknowledgment of Governance Collapse
-
What happened: The Malaysian Government (MCMC/GAC) officially stated that the domain’s removal was a result of an “ICANN system failure.”
-
Why it matters: This confirms that the registrant (WONG TAI CHIEW) did nothing wrong. The fault lies entirely within the system Namecheap is contracted to manage, yet they have refused to represent their customer’s interests to ICANN.
Consolidated Conclusion
Namecheap validated, monetized, renewed, and retained malaysia.build for nearly eight years, removed it while still paid without notice or required security safeguards, acknowledged foreseeable harm, then disengaged entirely.
This pattern is incompatible with good-faith registrar conduct and establishes systemic failure at the registrar level, resulting in direct financial loss, operational disruption, and long-term reliance harm to the registrant.
Taken as a whole, this conduct meets the definition of unfair and deceptive practices under consumer protection standards.
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.