Read And Share

WONG TAI CHIEW (Case #01448650) (You) 05:35 PM

Good afternoon. My name is Wong Tai Chiew, a Malaysian citizen with Case #01448650—a matter now viewed by over 15,400 people in the NamePros community.

My case involves a 10-year registry breach of Specification 5, which the Malaysian Communications and Multimedia Commission (MCMC) has confirmed in writing: no approval was ever given for ‘Malaysia’ under the .BUILD gTLD.

Madam Chair, given ICANN85’s theme of ‘Transparency, Trust, and Strengthening Visibility,’ I would be grateful to know what specific oversight the Board has provided on this case, and whether the Board has discussed it at all during this summit.

To ICANN Compliance: My complaint has been with your team for over 240+ days. The government has confirmed the breach. I respectfully ask: what is the current status of your investigation, and when might I expect a substantive response?

To the Ombudsman: Your office previously informed me that you could not intervene because the Compliance process was ongoing. Since that process has not concluded

Liana Teo – ICANN Org 05:50 PM

ICANN Contractual Compliance operates an Audit Program designed to regularly assess whether registrars and registries adhere to all ICANN policies and agreements. A 2023 ICANN Registry Audit found that a registry operator had improperly released a domain name. ICANN Compliance notified the registry operator, which acknowledged the error, deleted the name, returned it to the reserved list, and implemented safeguards to prevent similar issues in the future.

The former registrant contacted ICANN Compliance in July 2025. Through multiple communications, ICANN Compliance explained the Specification 5 requirements, the audit findings, and the corrective steps the Registry Operator took to remediate its noncompliance. ICANN also provided the public link to the 2023 Registry Audit Report.

ICANN Compliance engaged extensively to respond to the complainant’s questions. This engagement should not be understood as an ongoing investigation. The complainant was informed that there were no indications of noncompliance regar

WONG TAI CHIEW (Case #01448650) (You) 05:39 PM

Good afternoon. My name is Wong Tai Chiew, a Malaysian citizen with Case #01448650—a matter now viewed by over 15,420 people in the NamePros community.

My case involves a 10-year registry breach of Specification 5, which the Malaysian Communications and Multimedia Commission (MCMC) has confirmed in writing: no approval was ever given for ‘Malaysia’ under the .BUILD gTLD.

Madam Chair, given ICANN85’s theme of ‘Transparency, Trust, and Strengthening Visibility,’ I would be grateful to know what specific oversight the Board has provided on this case, and whether the Board has discussed it at all during this summit.

To ICANN Compliance: My complaint has been with your team for over 241+ days. The government has confirmed the breach. I respectfully ask: what is the current status of your investigation, and when might I expect a substantive response?

To the Ombudsman: Your office previously informed me that you could not intervene because the Compliance process was ongoing. Since that process has not concluded

Liana Teo – ICANN Org 05:50 PM

The complainant was informed that there were no indications of noncompliance regarding the actions taken by the Registry Operator to ensure the domain was reserved following its improper release and that there was no enforcement action available under ICANN’s contractual authority.

The government of the relevant country also confirmed that it had never issued approval for use of the country name and supported its deletion under Specification 5, as stated in a letter sent to ICANN in December 2025.

ICANN understands that the former registrant held the domain for many years and feels they were not at fault for its loss, and ICANN is sympathetic to those concerns. However, Specification 5 requires certain country and territory names to remain reserved unless government approval for their release has been granted. ICANN Compliance cannot unilaterally waive obligations under the Registry Agreement, nor can it decline to enforce Specification 5, which is intended to protect the interests of the relevant countries

Mary Wong – ICANN Org 05:53 PM

Regarding the Ombuds, we encourage you to take up the matter directly with the Ombuds as it is a matter for her office.

Please also direct questions for the Board to the Board; among other opportunities, this Community Forum will host the Public Forum later this week.

Thank you (on behalf of the ICANN Executive Team)

WONG TAI CHIEW (Case #01448650) (You) 05:52 PM  Dismissed by host

Dear Liana, tq for your reply but you didn’t answer my questions

WONG TAI CHIEW (Case #01448650) (You) 05:52 PM  Dismissed by host

Pleaase forward my questions to the speakers and answer my questions publicly

WONG TAI CHIEW (Case #01448650) (You) 05:53 PM  Dismissed by host

Please answer these questions too. To the Ombudsman: Your office previously informed me that you could not intervene because the Compliance process was ongoing. Since that process has not concluded after 241+ days, I would appreciate guidance on what options remain for a registrant when no process ever seems to reach a resolution.

And finally, regarding the Facebook post: During ICANN85, I left a polite comment on the Board Chair’s post referencing my case. That comment is visible to me but not to the public—a shadow ban I have documented with screenshots and video. I would be grateful for any clarification on how this practice aligns with the transparency theme of this summit.

WONG TAI CHIEW (Case #01448650) (You) 05:54 PM  Dismissed by host

Dear all, all parties keep silence to date

WONG TAI CHIEW (Case #01448650) (You) 05:54 PM  Dismissed by host

please, talk my case in public now

WONG TAI CHIEW (Case #01448650) (You) 05:55 PM  Dismissed by host

Please let the experts on stage talk about my case

WONG TAI CHIEW (Case #01448650) (You) 05:55 PM  Dismissed by host

i have been waiting for the answers for over 271+ days

WONG TAI CHIEW (Case #01448650) (You) 05:56 PM  Dismissed by host

please do not say again the party should be blame. to date all levels failed

WONG TAI CHIEW (Case #01448650) (You) 05:57 PM  Dismissed by host

https://loss.co/#failed

WONG TAI CHIEW (Case #01448650) (You) 05:57 PM  Dismissed by host

please vsit the url above

WONG TAI CHIEW (Case #01448650) (You) 05:58 PM  Dismissed by host

please talk my case in public, on icann85 stage

WONG TAI CHIEW (Case #01448650) (You) 05:58 PM  Dismissed by host

please forward my questions to the experts on stage now

WONG TAI CHIEW (Case #01448650) (You) 05:58 PM  Dismissed by host

nope. Compliance has provided answers to all of your questions directed to Compliance. Thank you.

WONG TAI CHIEW (Case #01448650) (You) 05:59 PM  Dismissed by host

visit the url i gave you, all i got is just inconsistancies, contractions, catch-22s, non-logic substances

WONG TAI CHIEW (Case #01448650) (You) 05:59 PM  Dismissed by host

please do not hide anymore behind the stage

WONG TAI CHIEW (Case #01448650) (You) 06:00 PM  Dismissed by host

if you think those are the answers, then please ask the expects on stage say it in public

WONG TAI CHIEW (Case #01448650) (You) 06:01 PM  Dismissed by host

there is no need to argue here whose’s fault is it in the chat

WONG TAI CHIEW (Case #01448650) (You) 06:01 PM  Dismissed by host

let the expects on stage talk about my case

WONG TAI CHIEW (Case #01448650) (You) 06:01 PM  Dismissed by host

that is all i ask

WONG TAI CHIEW (Case #01448650) (You) 06:03 PM  Dismissed by host

Good afternoon. My name is Wong Tai Chiew, a Malaysian citizen with Case #01448650—a matter now viewed by over 15,420 people in the NamePros community.

My case involves a 10-year registry breach of Specification 5, which the Malaysian Communications and Multimedia Commission (MCMC) has confirmed in writing: no approval was ever given for ‘Malaysia’ under the .BUILD gTLD.

Given ICANN85’s theme of ‘Transparency, Trust, and Strengthening Visibility,’ I would be grateful to know what specific oversight the Board has provided on this case, and whether the Board has discussed it at all during this summit.

WONG TAI CHIEW (Case #01448650) (You) 06:03 PM  Dismissed by host

To ICANN Compliance: My complaint has been with your team for over 241+ days. The government has confirmed the breach. I respectfully ask: what is the current status of your investigation, and when might I expect a substantive response?

To the Ombudsman: Your office previously informed me that you could not intervene because the Compliance process was ongoing. Since that process has not concluded after 241+ days, I would appreciate guidance on what options remain for a registrant when no process ever seems to reach a resolution.

And finally, regarding the Facebook post: During ICANN85, I left a polite comment on the Board Chair’s post referencing my case. That comment is visible to me but not to the public—a shadow ban I have documented with screenshots and video. I would be grateful for any clarification on how this practice aligns with the transparency theme of this summit.

WONG TAI CHIEW (Case #01448650) (You) 06:03 PM  Dismissed by host

please forward all my questions to the experts on stage

WONG TAI CHIEW (Case #01448650) (You) 06:04 PM  Dismissed by host

i would like to hear the answers from the experts in icann85, in public.

WONG TAI CHIEW (Case #01448650) (You) 06:06 PM  Dismissed by host

for your reference, this online session is being recorded as video that i might release in youtube

Olabimpe Adeloro (fNSIG) 06:06 PM

Good morning from my part of the world

please, I will like to ask my question verbally

Andrea Glandon – ICANN Org 06:06 PM

Please raise your hand to ask your question.

WONG TAI CHIEW (Case #01448650) (You) 06:06 PM  Dismissed by host

thus, please forward my questions to the experts on stage and answer my questions publicly. thank you

WONG TAI CHIEW (Case #01448650) (You) 06:07 PM  Dismissed by host

that is not the answer

WONG TAI CHIEW (Case #01448650) (You) 06:08 PM  Dismissed by host

i raised my hand already. next?

WONG TAI CHIEW (Case #01448650) (You) 06:09 PM  Dismissed by host

can you at least confirm that these questions have been heard, and that the registrant in Case #01448650 will finally receive a substantive response?

WONG TAI CHIEW (Case #01448650) (You) 06:15 PM  Dismissed by host

no

WONG TAI CHIEW (Case #01448650) (You) 06:16 PM  Dismissed by host

what i got is just the contractions, catch-22s and inconsistansies

WONG TAI CHIEW (Case #01448650) (You) 06:17 PM  Dismissed by host

please forward my questions to the on stage experts

WONG TAI CHIEW (Case #01448650) (You) 06:17 PM  Dismissed by host

to date, icann provides zero resolutions.

WONG TAI CHIEW (Case #01448650) (You) 06:18 PM  Dismissed by host

explain the catch-s-22s, contractions…

WONG TAI CHIEW (Case #01448650) (You) 06:18 PM  Dismissed by host

no explanation and you want to close the case?

WONG TAI CHIEW (Case #01448650) (You) 06:19 PM

is this how you definate the “transparency, trust and visibility”?

Balazs Nemethi 06:19 PM

Has the board considered whether the existing namespace structure is sufficient for machine-to-machine agent discovery, or whether AI systems may need their own scoped namespace as the agentic web scales?

Mary Wong – ICANN Org 06:23 PM

Thank you for your question. As it is addressed to the ICANN Board, please raise it in the appropiate forums where the Board engages with the community. This includes the Public Forum at this meeting, later this week.

WONG TAI CHIEW (Case #01448650) (You) 06:24 PM

just explain my questions

WONG TAI CHIEW (Case #01448650) (You) 06:25 PM

Case #01448650 | Domain: malaysia.build | Timeline: July 11 – Mar 9, 2026

ICANN Contractual Compliance was responsible for investigating the unauthorized deletion of malaysia.build on December 5, 2023—despite 10 years of lawful ownership, active auto-renewal, and paid status through April 2024. Instead of fair investigation, Compliance delivered 241 days of templated evasions, contradictory statements, ignored deadlines, and blame-shifting to the Registry’s “error” while denying authority to act. Compliance issues a document riddled with contradictions, wrong audit dates, and errors response came only after public pressure (namepros.com) and GAC complaint.

The institutional failure extends beyond the Registry to ICANN itself. My formal complaint with ICANN’s Contractual Compliance department (opened July 11, 2025) has remained in a state of deliberate, unresolved limbo for 241 days. The department appears unable to deliver a resolution yet equally unwilling to formally close the case without one, resulting

WONG TAI CHIEW (Case #01448650) (You) 06:25 PM

partial record from https://loss.co/responses/#icann

WONG TAI CHIEW (Case #01448650) (You) 06:25 PM

can you explain?

WONG TAI CHIEW (Case #01448650) (You) 06:26 PM

please, tell me the answer on stage

WONG TAI CHIEW (Case #01448650) (You) 06:27 PM

maybe just a simple question. why 241+ days?

WONG TAI CHIEW (Case #01448650) (You) 06:27 PM

the whole is being recorded

WONG TAI CHIEW (Case #01448650) (You) 06:28 PM

is that is the icann’s answer, avoid to answer my questions even though i have tried hard asking the questions

WONG TAI CHIEW (Case #01448650) (You) 06:28 PM

i would consider the silence of icann continues

WONG TAI CHIEW (Case #01448650) (You) 06:29 PM

silence = admission

WONG TAI CHIEW (Case #01448650) (You) 06:31 PM

hello, i raised my hand for a long time

Jamie Hedlund – ICANN Org 06:32 PM 

The action to delete the name took place in 2023 as a result of the registry audit at that time. You submitted your complaint in 2025. While we have not closed your complaint in order to explain why the registry was in compliance with the registry agreement (which we have done several times through your case), we can close it now. The facts and the requirements of the RA are clear. The registration of the domain name at issue violated the Registry Agreement. The registry operator’s deletion of the name was in compliance with the Registry Agreement. To seek additional relief, you might consider seeking advice from legal counsel.

WONG TAI CHIEW (Case #01448650) (You) 06:34 PM

did you really read my record? domain is auto renew enabled, zero prior notice

WONG TAI CHIEW (Case #01448650) (You) 06:34 PM

does auto renew enabled mean something to you?

WONG TAI CHIEW (Case #01448650) (You) 06:35 PM

i did nothing wrong for 10 years, why should i bear all the losses?

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.