Namecheap, Enom And .Build Registry Complete Email Trail

Subject: Domain Transferred out: malaysia.build

From: NameCheap.com Support <support@namecheap.com>
Date: Tue, Dec 5, 2023 at 8:00 PM
To: WONG TAI CHIEW <dotconame@gmail.com>

———————————————————————-
Namecheap.com
Domain transferred out: malaysia.build
Date: 12/5/2023 7:00:02 AM
———————————————————————-

Dear WONG TAI CHIEW,

This notice is to inform you that your domain has been transferred out of Namecheap.

Domain Name: malaysia.build
Transferred Date : 12/4/2023 7:18:54 AM

Sincerely,
Namecheap Team
http://www.namecheap.com/

From: DotCoName <dotconame@gmail.com>
Date: Wed, Jun 11, 2025 at 3:48 PM
To: <security@namecheap.com>

Sir,

Kindly resolve the issue as outlined in the chat record.

Thank you.

Regards,

TC Wong

malaysia.build
11 Jun 2025, 3:35 PM

Hello! Thank you for contacting our Namecheap support team. How can I assist you with “malaysia.build” today? Are you experiencing any issues or do you have a specific question regarding this domain?
11 Jun 2025, 3:35 PM

Domain Transferred out: malaysia.build
Inbox

NameCheap.com Support <support@namecheap.com>
Dec 5, 2023, 8:00 PM
to meShow All
11 Jun 2025, 3:35 PM

Thank you for providing the details about your domain, malaysia.build. I see that you received a notification confirming the transfer of this domain out of Namecheap on December 4, 2023.

Could you please clarify what assistance you need regarding this domain transfer? Are you looking for more information about the transfer process, have concerns about the transfer, or need help with something else related to malaysia.build?
11 Jun 2025, 3:36 PM

Transferred Date : 12/4/2023 7:18:54 AM
11 Jun 2025, 3:37 PM

Thank you for confirming the transfer date for malaysia.build. Could you please let me know what specific assistance you need regarding this domain transfer? For example, are you inquiring about the status, have concerns about the transfer, or need help with a related issue? This will help me provide the most relevant information or guidance.
11 Jun 2025, 3:37 PM

Domain transferred out: malaysia.build
Date: 12/5/2023 7:00:02 AM
i checked all the record. i didn’t do the transfer
no record found in my paypal
11 Jun 2025, 3:37 PM

Thank you for sharing these details and your concern. I understand that you did not authorize the transfer of your domain malaysia.build and did not find any related transaction in your PayPal records.

To assist you further, could you please clarify if you have noticed any unusual activity in your Namecheap account, such as unauthorized logins or changes to your account information? This information will help us understand if there may have been unauthorized access to your account.

Once you provide this information, I will transfer your case to a live agent who can investigate this matter further for you.

Hide
11 Jun 2025, 3:38 PM

while i register account at spaceship in dec 2023
11 Jun 2025, 3:38 PM

Thank you for letting me know that you registered an account at Spaceship in December 2023. To clarify, are you saying that you did not initiate the transfer of malaysia.build to another registrar, and you only registered a new account at Spaceship?

If you did not authorize the transfer and only created a Spaceship account, please confirm so I can pass this information to a live agent for further investigation.

Thank you for your cooperation. Please stand by, I will find an appropriate person.

Show All
11 Jun 2025, 3:38 PM

Maksym Z.

joined the chat

11 Jun 2025, 3:38 PM

Suzy Q left the chat
11 Jun 2025, 3:38 PM

Hello, my name is Maksym, and I will assist you further. Please allow me about 5 minutes to look through your previous conversation, review the necessary details, and look into your request.
11 Jun 2025, 3:39 PM

please check all my transfer out records
it won’t take a month to transfer out my domain names
11 Jun 2025, 3:39 PM

paypal
.png
just sent you the paypal record
11 Jun 2025, 3:42 PM

Thank you for waiting. In order to escalate this issue, please reach out to our Risk Management department at security@namecheap.com

When reaching out to them, please make sure to provide as many details regarding the case as possible, as well as your username and Support PIN.
11 Jun 2025, 3:42 PM

can i talk to them right now?
i checked my emails. there is no even the reminder to renew the domain name
only one email stating the domain name had been transferred out
11 Jun 2025, 3:43 PM

Risk Management is only available via email and cannot be contact via live chat.
11 Jun 2025, 3:43 PM

namesilo.com does not support .build registration

From: Namecheap Risk Management Team <security@namecheap.com>
Date: Wed, Jun 11, 2025 at 3:48 PM
To: DotCoName <dotconame@gmail.com>

Hello,

Thank you for contacting us. This is an automated response confirming the receipt of your request. Our team will get back to you as soon as possible. When replying, please make sure that the engagement ID is kept in the subject so that we can track your replies.

Best regards,
Namecheap Team

From: Namecheap Risk Management Team <security@namecheap.com>
Date: Wed, Jun 11, 2025 at 5:18 PM
To: <dotconame@gmail.com>

Hello,

Thank you for contacting us!

We will be happy to help you, but we need some additional information. In order for us to verify your account ownership and check the services associated with your account, please provide us with:

1) Your Namecheap account username;

2) The Support PIN. You can find it here: https://ap.www.namecheap.com/Profile/Security

Also, please let us know if you have contacted us via Live Chat or Email System. If so, please provide us with the corresponding Chat/Email ID.

We are looking forward to hearing from you.

From: DotCoName <dotconame@gmail.com>
Date: Wed, Jun 11, 2025 at 6:41 PM
To: Namecheap Risk Management Team <security@namecheap.com>

1. terrytkh
2. 8201 

Hello,

Thank you for getting back to us and for the details provided.

Regrettably, we find ourselves in need of additional time to thoroughly review your case. Please rest assured that we are diligently working on it, and we are committed to keeping you informed as soon as we have any updates to share.

We apologize for any inconvenience this might cause.

Your understanding is highly appreciated.

From: DotCoName <dotconame@gmail.com>
Date: Fri, Jun 13, 2025 at 2:34 PM
To: Namecheap Risk Management Team <transferdisputes@namecheap.com>

Sir,

I checked the domain history for malaysia.build. You can view it here: https://whoisfreaks.com/tools/whois/history/lookup/malaysia.build.

I have owned malaysia.build since 2014, and there is absolutely no reason I would ever discard it. Additionally, as someone from Malaysia, I fully understand the value and potential of this domain name.

However, it appears that my domain has been transferred to Enom, LLC—even though I do not have an account with Enom.

Please investigate and resolve this issue as soon as possible.

Thank you.

Regards,

TC Wong

From: Namecheap Risk Management Team <security@namecheap.com>
Date: Fri, Jun 13, 2025 at 3:42 PM
To: <dotconame@gmail.com>

Hello,

Thank you for your email.

We need some more time for additional investigation.

Please rest assured that we will contact you as soon as we get the needed updates.

Your patience and understanding will be highly appreciated.

From: DotCoName <dotconame@gmail.com>
Date: Tue, Jun 17, 2025 at 2:59 PM
To: Namecheap Risk Management Team <security@namecheap.com>

Dear Sir,

I filed a complaint six days ago, but as of today, the issue remains unresolved. I am certain that I did not initiate the transfer of malaysia.build.

I respectfully request a clear explanation regarding this matter and the immediate return of my domain name.

Sincerely,

TC Wong

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Tue, Jun 17, 2025 at 5:13 PM
To: <dotconame@gmail.com>

Hello,

Thank you for your response!

Currently, we have a higher number of support requests than usual. Please accept our apologies for the delayed reply.

To our deepest regret, we are still investigating this issue and will update you as soon as possible.

Your understanding is highly appreciated.

Should you have any other questions, contact us again.

From: DotCoName <dotconame@gmail.com>
Date: Thu, Jun 19, 2025 at 2:21 PM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>

Dear Sir,

I am writing to follow up on the complaint I submitted eight days ago regarding the unauthorized transfer of my domain name, malaysia.build. To date, I have not received any resolution or clear explanation regarding this serious matter.

As previously stated, I am confident that I did not initiate the transfer. Given the circumstances and the time that has passed, I respectfully urge your team to treat this issue with the urgency it deserves. I kindly request an update on the status of the investigation and the immediate return of my domain name.

Your prompt attention and assistance would be greatly appreciated.

Sincerely,
TC Wong

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Thu, Jun 19, 2025 at 3:26 PM
To: <dotconame@gmail.com>

Hello!

We fully understand your frustration regarding this matter and realize how inconvenient it is.

We are still working on the issue. We are monitoring the case and will contact you as soon as we have any information.

Your patience is appreciated.

From: DotCoName <dotconame@gmail.com>
Date: Sat, Jun 21, 2025 at 2:34 PM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>

Subject: Urgent Follow-up: Domain malaysia.build Unresolved After 11 Days

Dear Sir/Madam,

I am writing to follow up once again regarding the unauthorized transfer of my domain name, malaysia.build, for which I submitted a formal complaint 11 days ago. Despite several follow-up emails, I have yet to receive any response, explanation, or update from Namecheap regarding this matter.

I began developing malaysia.build in 2022, as shown in the attached screenshot from my testing environment. Since then, I have invested substantial time and resources into building out the platform, including integrating Progressive Web App (PWA) functionality and preparing to publish mobile apps for both Android and iOS using hybrid webview technology.

I only discovered the domain was missing from my account when I attempted to connect it to my hosting platform, as all the major development work was nearly complete — thanks in part to AI tools that helped me resolve various technical challenges. The project is designed specifically for real estate listings in Malaysia, with a paid premium listing feature for users.

I can’t remember the exact time I signed up with Namecheap, but my best estimate is that it has been over 20 years. I would also like to emphasize that I have been a Namecheap customer for over 20 years, and during that time I have managed hundreds of domain names through your platform. Given my longstanding loyalty and commitment, I believe I deserve better service than the continued silence and delay in resolving this serious issue.

At the very least, I respectfully request that you provide me with information on which registrar the domain was transferred to.

The ongoing delay is causing me significant financial loss and is damaging my credibility with early users who were already engaged with the platform. I strongly urge your team to treat this matter with the urgency and seriousness it deserves and provide a prompt resolution.

Thank you for your attention, and I look forward to hearing from you soon.

Sincerely,

Sincerely,
TC Wong

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Sat, Jun 21, 2025 at 3:42 PM
To: <dotconame@gmail.com>

Hello,

Thank you for getting back to us.

We understand how frustrating the whole situation can be, please rest assured that we’re doing everything possible from our side to investigate what happened with the domain and see if it is possible to somehow restore it.

We are currently in contact with our upstream provider and Registry and waiting for further updates from them.

While we do not have exact information at the moment, we can say that malaysia.build is not registered at all at the moment. But, its registration is restricted by the .BUILD Registry – it has “reserved” status and cannot be registered at the moment, unfortunately. Registry is a company that operates all the domains of this TLD (.BUILD) regardless of what registrar they are registered with. Our assumption is that the issue might be related to its name as usually Registries do not allow registering domains consisting of country names.

Let us mention that the “Domain transferred out: malaysia.build” notice received by you does not necessarily mean that it indeed was transferred. Sometimes, the system can send such notices if the domain for some reason is deleted/removed from the system (transfer is just one of the reasons why domains can be deleted/removed from the system).

Please allow us more time for investigating the issue and check if anything can be done. To our regret, being a Registrar company we are unable to register/restore a domain restricted by the Registry. Thus, we are currently investigating the issue and will get back to you once there is more information.

Your patience is highly appreciated.

In the meantime, if any questions appear or you need our help, please do not hesitate to contact us.

From: DotCoName <dotconame@gmail.com>
Date: Thu, Jul 3, 2025 at 1:44 AM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>

Subject: URGENT: Follow-Up Request – Domain malaysia.build (Pending Since 11 June 2025)

Dear Namecheap Support Team,

I am writing to urgently follow up on the unauthorized removal of my domain malaysia.build, which I formally reported on 11 June 2025. It has now been over three weeks since my initial complaint, and I have yet to receive a meaningful update — despite the mounting financial and operational consequences.

As a 20-year loyal Namecheap customer managing hundreds of domains through your platform, I have always valued our relationship. However, the continued silence on this critical issue is now resulting in:

• Severe business disruption: My nearly completed real estate platform at testing website, featuring PWA, FPX integration, mobile apps webview ready, and agent dashboards, remains on hold.
• Monetization delays: I’m currently unable to generate expected revenue from premium listings.
• Reputational damage: Early users and partnering agencies are left uncertain, awaiting platform launch.

I respectfully request clarity on the following points:

1. What concrete actions is Namecheap currently taking in coordination with the .BUILD registry?
2. When can I expect a clear resolution timeline?
3. If restoration is ultimately not possible, what compensation framework does Namecheap intend to offer?

As previously shared, I have provided comprehensive evidence of my ownership and development efforts dating back to 2014.

Given the registry’s statement that malaysia.build is now in a “reserved” status, I also request:

• Full disclosure of the .BUILD registry’s contact information
• The specific policy or regulation that prohibits use of “malaysia.build”
• An explanation of why no prior violation notice was issued before the domain was removed (I owned malaysia.build for nearly 10 years before it was transferred out without my authorization!)

Thank you for your prompt attention.

Sincerely,
TC Wong

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Thu, Jul 3, 2025 at 4:21 AM
To: <dotconame@gmail.com>

Greetings,

Thank you for your response. We apologize for the delay in reply.

We completely understand how frustrating this must be for you. Please know that we are fully committed to investigating the issue with the domain and exploring options to recover it.

Unfortunately, we do not yet have exact details regarding why the domain was removed. Once we receive concrete information, we will consider further steps to be taken.

Right now, we are still waiting for updates from our upstream provider and the Registry. To our regret, this Registry does not usually correspond with registrants directly.

Should you have any questions or require further assistance in the meantime, please feel free to reach out to us at any time.

From: DotCoName <dotconame@gmail.com>
Date: Sun, Jul 6, 2025 at 10:45 PM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>, <richardk@namecheap.com>, <winston@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, <escalations@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>

Subject: Follow-Up Regarding Domain malaysia.build  (URGENT)

Dear Namecheap Support Team,

I am writing to express my significant concern regarding the ongoing situation with my domain name, malaysia.build. My initial report was filed on June 11, 2025. Despite multiple follow-up emails, your last communication on July 3, 2025, merely reiterated that you were “waiting for updates from our upstream provider and the Registry.” As of today, July 6, 2025, it has been nearly a month since my initial report, and 3 days since your last update. Every reply I have received so far has simply asked me to give more time for your team to investigate, offering no specific progress, no timeline, and no concrete explanation to date.

This prolonged delay is particularly concerning given a critical detail: the domain malaysia.build was transferred out of my account on December 5, 2023, despite its paid-for expiry date being April 29, 2024 — meaning it was still valid for nearly five months at the time of the transfer. (Reference: https://whoisfreaks.com/tools/whois/history/lookup/malaysia.build). This transfer of an actively registered and paid-for domain raises significant questions about the circumstances surrounding its removal and Namecheap’s domain management protocols.

Please find the attached receipt named namecheap-order-116083446-malaysia-build-03-30-2023.pdf as evidence of the domain’s renewal and validity through April 29, 2024. In addition, I have uploaded a video to YouTube as supporting evidence of my ownership of malaysia.build dating back to 2014. The video is in Mandarin with subtitles, but by viewing the description and content, it should be clear that I am demonstrating long-standing ownership and usage of the domain. You may view it at: https://malaysia.sibu.design/proof-of-malaysia-build-ownership-since-2014/.

To underscore the immense importance of this domain, I had even set malaysia.build to auto-renew, linked directly to my credit card ending in 0593. This proactive measure was specifically put in place to prevent any accidental incidents, such as forgetting to renew, highlighting how critically important this domain is to me. Please find the attached screenshot (auto-renewal-2021.png) confirming that Namecheap sent me a notification that the auto-renewal had been successfully processed. This domain is truly priceless to me.

The domain malaysia.build was actively held and used for other purposes until 2020. During that time, it was not used as a real estate listings website. However, since December 2022, I have dedicated substantial time and effort to develop this project specifically into a comprehensive real estate listings platform. This involved significant investment in the core platform, mobile app (for both Android and iOS platforms), PWA framework, and a suite of advanced features for a market-ready ecosystem. My decision was made at a high level to exclusively develop and launch this platform under malaysia.build, recognizing it as the perfect and most valuable choice due to its direct relevance to the real estate sector and its strong potential to achieve high rankings in Google search with keywords like “Malaysia” and “build.” The inclusion of “Malaysia” in the domain name is paramount for geo-targeting and local SEO, ensuring high visibility for users searching for real estate within Malaysia. The .build extension directly relates to construction, development, and real estate, instantly signaling the website’s purpose and establishing a professional, industry-specific perception, which is critical for user engagement, conversion, and long-term value.

Crucially, malaysia.build is designed to serve a global audience. Unlike country-specific domains like .com.my or .my, the .build gTLD (generic Top-Level Domain) has no geographical limitation, allowing me to connect with property seekers and investors worldwide. To support international visitors, especially those exploring programs like the Malaysia My Second Home (MM2H) program (official URL: https://www.imi.gov.my/index.php/en/main-services/malaysia-my-second-home-mmh2-en/), I’ve integrated a global language translator and a built-in language selector (default: English) to ensure a seamless and accessible property search experience for everyone.

Beyond the technical development, I also invested significant time in extensive research into the Malaysian real estate market. This research meticulously determined all the necessary fields for property submission forms and the comprehensive details to be displayed on each single property page. I even considered crucial cultural factors, such as the importance of Feng Shui for most Malaysians (especially the Chinese community), which led me to deliberately include a “direction” field in both the submission and details display sections. This demonstrates the deep understanding and tailored approach taken to ensure the platform’s relevance and appeal to the target market.

A fully functional demo of this project, showcasing nearly 90% of all its key features and functions, is available at my demo website: https://malaysia.sibu.design. You can navigate to the “Features” section in the menu.

To experience the PWA on your mobile device, please visit https://malaysia.sibu.design/pwa/ and follow the instructions.

To try the Android mobile app, please download it from https://malaysia.sibu.design/android/malaysia-build.apk, install it on your phone, and explore all the available features.

To see the FPX Payment Gateway features, please visit https://malaysia.sibu.design/fpx/. There, you’ll find a YouTube video demonstrating the entire transaction process, showing that it fully supports real online payments.

I’ve created two trial accounts on Namecheap to test the platform—one with an Agent role and the other with an Agency role:

• Agent Account:Username: agent, Password: return-my-domain-name
• Agency Account:Username: tcwong, Password: return-my-domain-name

These accounts are for demonstration purposes.

I am suffering tremendous loss due to this unauthorized transfer, encompassing:

• Significant Time and Effort & Development Costs:Substantial investment in the core platform, mobile app (for both Android and iOS), PWA framework, and a comprehensive suite of advanced features (including Google Maps/Street View, very complicated search functions within the system that allow users to search over 50 fields and narrow down results to easily find what they are looking for, automatic mortgage calculation, preset messages via WhatsApp, email forms, printable formats, saved favorites, property comparison, social sharing, image galleries, downloadable brochures, floor plans, embedded videos, nearby places, visitor reviews, related properties, photo watermarking, etc).
• Lost Revenue and Monetization Delays:Inability to generate expected income from premium listings (The integrated FPX Payment Gateway is fully functional in real-time, meaning I am losing real potential transaction revenue every day the website is unavailable.), featured properties, broker lead fees, ad space, data analytics, transaction commissions, commission on bank loans, third-party advertising, property valuation reports, exclusive content/market insights, and agent subscriptions.
• Business Disruption:The entire project, which was weeks from launch, is on hold, causing severe operational setbacks. This includes ongoing operational costs for maintaining the stalled project.
• Reputational Damage:Credibility with early users and partnering agencies is being undermined by the inability to launch.
• Loss of Strategic Market Position:Forfeiting a unique and unreplicable advantage in the Malaysian real estate market, particularly concerning mobile users, cross-language accessibility, and financial integration. This includes loss of first-mover advantage in a competitive market.
• Loss of Marketing and Branding Investment:Resources already invested in promoting the malaysia.build brand or preparing launch campaigns that are now compromised or wasted.
• Opportunity Cost:The missed potential to pursue other valuable business initiatives while resources are diverted to resolving this dispute.
• Costs of Dispute Resolution:The time, effort, and potential future expenses associated with pursuing this complex dispute.
• Potential Punitive Damages:Arising from the serious nature of an unauthorized transfer of a paid-for domain.

Your previous communication indicated that the malaysia.build domain is currently in a “reserved” status by the .BUILD Registry, with an assumption that this relates to the domain name consisting of a country name. However, I owned and actively developed this domain for nearly a decade before this “reserved” status was apparently enforced or before it was “transferred out” without my authorization. I received no prior notice of any policy violation. My long-standing and substantial development creates a clear, legitimate interest in the domain that should override any belated or ambiguous reservation policy. Furthermore, Namecheap’s role in the “transferred out” notification and your current inability to provide clear reasons or solutions indicates a potential breach of your contractual obligations to me as my registrar.

As a loyal Namecheap customer, I kindly ask you to recognize the URGENCY of this matter and the direct responsibility Namecheap holds for the removal of my domain prior to its expiry. I respectfully request a comprehensive explanation for the pre-expiry transfer of my domain and a definitive outline of the immediate steps Namecheap will take to rectify this situation within 48 hours of this email.

Please understand that if a satisfactory explanation and the return of my domain name are not provided within this 48-hour timeframe, I will unfortunately need to proceed with filing formal complaints with:

• The .BUILD Registry directly.
• ICANN’s Contractual Compliance Departmentregarding Namecheap’s apparent failure to protect my domain and adhere to transfer policies.
• An ICANN-approved dispute resolution service provider(such as WIPO or ADNDRC) to pursue the recovery of the domain based on my prior rights and your inability to restore it.

Thank you for your prompt and serious attention to this critical matter.

Sincerely,

WONG TAI CHIEW

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Mon, Jul 7, 2025 at 12:52 AM
To: <dotconame@gmail.com>

Hello,

Thank you for getting back to us.

Please accept our apologies for the delay in replying. We are doing our best to process the support tickets in a timely manner.

We sincerely understand how frustrating and stressful this ongoing delay must be, especially when you’ve done everything on your part to move the process forward.

Please rest assured that as soon as we received your request, we submitted it to our upstream provider. Since then, we’ve been closely monitoring the progress, which, unfortunately, is still pending on their end. They have acknowledged our request and assured us they will make every effort to expedite the process. While this is somewhat encouraging, we do recognise that this delay is far from ideal and deeply inconvenient for you.

We truly wish we had more direct control over this stage of the process. That said, we are committed to staying proactive on your behalf, and we will continue to follow up regularly until the matter is resolved.

We know this has been time-consuming and emotionally taxing, and we’re genuinely sorry that you’re having to go through this. Please know that your concerns are being taken seriously, and we’ll notify you immediately the moment we receive any update.

Your patience is highly appreciated.

From: DotCoName <dotconame@gmail.com>
Date: Wed, Jul 9, 2025 at 8:59 PM
To: <support@domain.build>, <abuse@domain.build>, <support@nic.build>, <abuse@nic.build>, <compliance@nic.build>
Cc: <compliance@icann.org>, <arbiter.mail@wipo.int>, <info@adndrc.org>

Subject: FORMAL COMPLAINT: Unauthorized Transfer of Domain malaysia.build – Urgent Action Required (Namecheap Ticket Number – [NC-UWS-6390])

To Whom It May Concern at The .BUILD Registry, ICANN Contractual Compliance, WIPO/ADNDRC, and Namecheap Management,

I am filing this formal complaint regarding the unlawful transfer and improper reservation of my domain, malaysia.build (Registrar: Namecheap, Inc.). This escalation targets:

1. The .BUILD Registryfor reserving my domain without justification despite nearly 10 years of ownership.
2. Namecheap, Inc.for violating ICANN transfer policies and failing to protect my domain.
3. ICANN Compliancefor inadequate registrar oversight.

Critical Facts:

1. Unauthorized Transfer:
   • The domain was transferred out of my account on December 5, 2023, despite being valid until April 29, 2024(Whois History – https://whoisfreaks.com/tools/whois/history/lookup/malaysia.build). Please find the attached receipt named namecheap-order-116083446-malaysia-build-03-30-2023.pdf.
2. Active Auto-renewal:
   • Auto-renewal was active with no authorization for transfer. Please find the attached screenshot (auto-renewal-2021.png) confirming that Namecheap notified me of a successful auto-renewal. I have also included a copy of my credit card ending in 0593. The card is still active, and I continue to use it.
3. Substantial Prior Rights:
   • I have owned and developed buildsince 2014 (Video proof: Ownership Evidence – You may view it at: https://malaysia.sibu.design/proof-of-malaysia-build-ownership-since-2014/).
   • My development efforts since December 2022 represent a value of over $500,000+ USD, encompassing multi-platform development including:
     • A functional demo of this project, showcasing nearly 90% of all its key features and functions, a complex backend with 50+ search filters, mortgage calculators, multi-language support, etc., is available at my demo website: https://malaysia.sibu.design. You can navigate to the “Features” section in the menu.
     • To experience the PWA on your mobile device, please visit https://malaysia.sdesign/pwa/and follow the instructions.
     • To try the Android mobile app, please download it from https://malaysia.sibu.design/android/malaysia-build.apk, install it on your phone, and explore all the available features.
     • iOS-ready WebView implementation (App Store developer account accessible via video proof).
     • To see the FPX Payment Gateway features, please visit https://malaysia.sibu.design/fpx/. There, you’ll find a YouTube video demonstrating the entire transaction process, showing that it fully supports real online payments.
   • Losing the malaysia.build domain name makes all my significant multi-platform development efforts effectively wasted.
4. Namecheap’s Gross Negligence:
   • There have been 28+ days of unresolved escalation(First report: June 11, 2025) with zero accountability.
   • No explanation has been provided for transferring a paid domain 5 months pre-expiry.
5. .BUILD Registry’s Unlawful Reservation:
   • The domain was reserved retroactively despite my prior ownership and extensive development.

Demonstrated Losses (Conservatively $1,000,000+ USD):

• Development Costs:
  • Developer cost of $500,000 – 30+ months of full-time work.
  • Includes platform, Android/iOS apps, PWA, Google Maps/Street View, advanced 50+ field search, mortgage calculator, WhatsApp messaging, email forms, printable formats, saved favorites, property comparison, social sharing, photo watermarking, floor plans, brochures, embedded videos, nearby places, reviews, related listings, etc.
• Revenue Loss:
  • $15,000+ per month.
  • Lost income from FPX payment transactions, premium listings, ad revenue, lead generation, third-party advertising, agent subscriptions, valuation reports, and market insights.
• Business Damage:
  • Project stalled just weeks before launch.
  • Reputational harm with early users and agency partners.
  • Operational costs ongoing despite halted progress.
• Opportunity Cost:
  • Loss of strategic first-mover advantage in Malaysian real estate tech.
  • Unique market position forfeited—mobile-first, multilingual, fully integrated with financial systems.
• Branding & Marketing Loss:
  • Resources spent on building and promoting the “build” brand are now wasted.
  • Launch campaign efforts compromised.
• Dispute Costs:
  • Significant time and effort required to resolve the dispute.
  • Ongoing and potential legal/administrative expenses.
• Potential Legal Risk:
  • Risk of punitive damages due to the unauthorized and unlawful transfer of a paid domain asset.

Policy Violations:

• ICANN Transfer Policy (Section II.E.7):Unauthorized transfer of an active domain.
• Registration Data Accuracy (ICANN 3.7.7):Failure to validate transfer requests.
• .BUILD Registry Abuse:Retroactive application of reservation policies.

Demands:

1. Immediate restorationof build to my Namecheap account.
2. Formal ICANN investigationinto Namecheap’s transfer protocols.
3. .BUILD Registry interventionto release the domain within 48 hours.
4. Initiation of UDRP proceedings(WIPO/ADNDRC) to enforce my rights under Paragraph 4(a) of the UDRP Policy.

Evidence Attached:

1. Domain renewal receipt (valid until 2024).
2. Auto-renewal confirmation.
3. Video proofs (ownership, FPX transactions, app developer accounts).

I kindly request written confirmation of the actions taken within 24 hours. If the issue remains unresolved, I may be compelled to pursue further action through appropriate international legal and regulatory channels.

Sincerely,

WONG TAI CHIEW

Mobile#: +60198280131

Address: 21, Lane 9, Rejang Park, 96000 Sibu, Sarawak, Malaysia

From: DotCoName <dotconame@gmail.com>
Date: Fri, Jul 11, 2025 at 10:57 PM
To: <support@domain.build>, <support@nic.build>, <compliance@nic.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: URGENT: Final Resolution Request – Unauthorized Transfer of malaysia.build (Ticket NC-UWS-6390)

Dear Namecheap Support and .BUILD Registry Team,

As a long-standing Namecheap customer, I value our relationship and write seeking urgent resolution to the unresolved status of my domain malaysia.build. It has now been over 30 days (since June 11, 2025) without substantive clarification or action regarding:

1. The December 5, 2023 transferof a domain paid through April 29, 2024.
2. The .BUILD Registry’s reservation of a domain I owned since 2014.
3. My filed ICANN complaint (Ref: [ 01448650]).

 Documented Facts

• Active Registration: Renewal receipt confirms validity until April 2024.
• Auto-Renewal Enabled: Namecheap notifications confirm active status (screenshots available).
• Prior Development: Functional platform (https://malaysia.sibu.design) and ownership proof since 2014.

 Policy Concerns

Per ICANN requirements:

Transfer Policy I.A.2.1: No evidence of FOA authorization obtained.
Registration Data Accuracy 3.7.7: Unvalidated transfer request.
Registry Agreement 2.8: Retroactive reservation of established domains.

Final Request

Within 48 hours (by July 13, 2025):

1. Restore build to my Namecheap account.
2. Provide written clarification:

• Circumstances of transfer (Namecheap)
• Basis for reservation (.BUILD Registry)

3. Initiate dialogue on incurred losses.

Transparency Measure

To demonstrate my commitment to resolution:

I’ve prepared https://loss.co documenting this case.

While currently a placeholder, it will publish on July 14, 2025:

• Full email/case timelines
• Policy violation analysis
• Evidence archives (receipts, videos, development proofs)

I encourage you to preview it now – this is your opportunity to resolve before public disclosure.

 Next Steps

Failure to resolve will necessitate:

• Full activation of https://loss.co (globally indexed)
• Escalation to ICANN Compliance + data protection authorities (GDPR/CCPA)
• UDRP filing with WIPO/ADNDRC

I trust you recognize the gravity of this situation and will act promptly.

Respectfully,
WONG TAI CHIEW
dotconame@gmail.com | +6019-8280131
21, Lane 9, Rejang Park, 96000 Sibu, Sarawak, Malaysia

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Fri, Jul 11, 2025 at 11:59 PM
To: <dotconame@gmail.com>

Hello!

Thank you very much for getting back to us.

Thank you for your continued patience, and we genuinely understand how upsetting and damaging this prolonged issue has been for you. Please know that we take your concerns seriously, and we want to assure you that we are pinging and monitoring the case accordingly.

To our regret, there are still no updates regarding the domain.

Please rest assured that we remember about your issue and will update you as soon as will receive any information.

We are sincerely sorry for the difficulties you’re facing and appreciate your patience as we work through a resolution. If there’s anything else we can clarify or assist you with in the meantime, please don’t hesitate to let us know.

From: DotCoName <dotconame@gmail.com>
Date: Sat, Jul 12, 2025 at 1:06 AM
To: <support@domain.build>, <support@nic.build>, <compliance@nic.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: RE: Ongoing Issue – malaysia.build Unauthorized Transfer

Dear Namecheap Support Team,

Thank you for your continued communication and for acknowledging the ongoing issue with my domain, malaysia.build.

I genuinely appreciate the efforts of your support team and your attention to my previous messages. However, as we now pass the one-month mark since my initial report on June 11, 2025, I hope you understand that the lack of a clear resolution or explanation has become increasingly difficult and concerning on my end.

To date, I have yet to receive:

• A detailed explanation of how the domain was transferred while it was active, paid, and set to auto-renew;
• A defined action plan to resolve the situation;
• Any substantial update from your upstream provider or the .BUILD Registry, despite my consistent follow-ups and supporting documentation.

Throughout this process, I have remained cooperative, patient, and respectful, trusting that this matter would be handled with urgency. I’ve also shared comprehensive evidence of my long-standing ownership, including financial and development commitments tied to this domain — which total over $1 million USD in value.

As a final step, I would like to respectfully reiterate the 48-hour timeframe previously mentioned.

Unless a clear response is provided addressing:

1. The reason for the transfer of the domain without my authorization,
2. The current status and any steps being taken, and
3. A timeline for restoring malaysia.build to my account,

I may have no other choice but to publish the full background and documentation of this issue on a dedicated site at https://loss.co.

The intent of the website is not to criticize, but to clearly document the timeline, evidence, and impact of this unresolved case, in order to seek transparency and inform others who may be affected by similar circumstances.

Please understand that I remain hopeful for a fair and professional resolution and would much prefer to resolve this matter immediately, through continued collaboration. I kindly request that this matter be escalated within your team as soon as possible.

Thank you again for your time and understanding. I look forward to your prompt response.

Warm regards,

WONG TAI CHIEW
Email: dotconame@gmail.com
Phone: +6019 8280131
Sibu, Sarawak, Malaysia

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Sat, Jul 12, 2025 at 2:09 AM
To: <dotconame@gmail.com>

Hello,

Thank you for getting back to us.

1. We are currently investigating how and why the malaysia.build domain was transfered with our Upstream provider, currently we do not know how the transfer occurred in this case.
2. We have escalated this case with our upstream provider via appropriate channels and are actively contacting them to check the current status of the investigation.
3. Unfortunately, a time estimate cannot be provided, but as soon as there are any news we will let you know.

Your patience and understanding is greatly appreciated.

If you have any other questions or requests, please do not hesitate to contact us.

From: DotCoName <dotconame@gmail.com>
Date: Sat, Jul 12, 2025 at 1:51 PM
To: <support@domain.build>, <support@nic.build>, <compliance@nic.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: RE: malaysia.build – Request for Urgent and Direct Resolution

Dear Namecheap Support Team,

Thank you for your latest update.

While I appreciate your honesty in acknowledging that the investigation is ongoing, I must express how extremely difficult this situation has become — especially after more than a full month with no meaningful progress, despite my repeated follow-ups and detailed supporting documents.

I am a long-standing customer of Namecheap. But in this case, I feel completely helpless, especially considering that I paid for the renewal of malaysia.build, and yet the domain was transferred out without my knowledge or authorization. This is not just about a technical issue — this is about the severe impact on a project I’ve dedicated more than a decade to, with over $1 million USD in development and real-world business value.

I’ve now received similar responses multiple times, including the latest statement:

“We have escalated this case with our upstream provider via appropriate channels and are actively contacting them to check the current status of the investigation.”

With all due respect — may I ask if there is a more direct way to follow up with the upstream provider? A simple phone call, Zoom meeting, or even WhatsApp might be far more effective than relying solely on tickets or emails. This isn’t a minor delay — it’s a time-sensitive issue affecting real people, real work, and real business.

Another part that’s particularly troubling is this:

“We are currently investigating how and why the malaysia.build domain was transferred… currently we do not know how the transfer occurred in this case.”

Honestly, this is hard to accept. I paid Namecheap directly for this domain, and it was renewed and auto-renewal was active. From a registrant’s perspective, the registrar — Namecheap — is responsible for ensuring that the domain remains safely in my account, especially if there were no requests from my side to transfer or cancel it.

Also, regarding this statement:

“Unfortunately, a time estimate cannot be provided…”

I understand that some matters are beyond your immediate control. But if the .BUILD Registry remains silent or unresponsive — what is Namecheap’s next move? Will you escalate further? Or am I left to escalate this matter on my own, even after relying on your platform and trusting your system for years?

The longer this issue remains unresolved, the more damage I suffer. Every day adds to development waste, lost revenue, brand risk, and credibility damage — not to mention the emotional toll. Am I to assume that either Namecheap or the .BUILD Registry will be taking responsibility for the financial losses caused by this situation?

I am still hopeful that we can resolve this professionally. I kindly request:

1. A formal status update from your upstream provideror the .BUILD Registry;
2. A clear and actionable plan for the next steps;
3. Clarification on what Namecheap will doif the registry does not respond in a reasonable time.

Please escalate this case with the urgency and seriousness it deserves. I would very much prefer to avoid making this matter public — but after one month of inaction, I feel cornered and with no real alternative.

Thank you again for your time and continued attention. I look forward to your prompt response.

Sincerely,
WONG TAI CHIEW
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Sat, Jul 12, 2025 at 2:39 PM
To: <dotconame@gmail.com>

Hello,

Thank you for getting back to Namecheap support!

We completely understand your frustration, and we truly regret the inconvenience this situation has caused.

Please rest assured that we’re actively monitoring your case and remain in close contact with our upstream provider regarding the issue.

As soon as we receive any updates or further information from them, we will let you know immediately.

Your patience is very much appreciated, and we’re here if you have any additional questions in the meantime.

From: DotCoName <dotconame@gmail.com>
Date: Sat, Jul 12, 2025 at 3:22 PM
To: <support@domain.build>, <support@nic.build>, <compliance@nic.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Request for Answers Regarding malaysia.build Domain Issue

Dear Namecheap Support Team,

Thank you for your latest reply.

I appreciate your continued communication, but I kindly ask that you address the key questions I raised in my previous email, as they remain unanswered and are central to resolving this issue.

To reiterate, could you please provide clear answers to the following:

1. How was the domain malaysia.build transferred out of my account despite being active, paid, and set to auto-renew?
2. Has your team received any communication or explanation from your upstream provider or the .BUILD Registry?
3. If not, can Namecheap directly contact them (via call, Zoom, etc.) to escalate the matter?
4. What will Namecheap do if the upstream provider or registry continues to remain unresponsive?
5. Who will be held responsible for the ongoing financial and business losses this delay is causing?

These are not rhetorical questions — I respectfully request direct, written responses to each.

Thank you again for your attention to this matter. I am still hopeful we can reach a fair and professional resolution soon.

Sincerely,
WONG TAI CHIEW
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Sat, Jul 12, 2025 at 4:16 PM
To: <dotconame@gmail.com>

Hello,

Thank you for getting back to Namecheap support!

We sincerely understand how frustrating this situation must be and truly apologize for the inconvenience it has caused.

Please know that we’re closely monitoring your case and are in ongoing communication with our upstream provider to resolve the issue. The case has already been escalated via the available communication channels on our side, but the investigation may take some time.

We’ll share any updates or new information with you as soon as we receive it.

Thank you for your continued patience, and feel free to reach out if you have any further questions in the meantime.

From: DotCoName <dotconame@gmail.com>
Date: Sat, Jul 12, 2025 at 10:14 PM
To: <support@domain.build>, <support@nic.build>, <compliance@nic.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Clarification Required Regarding Namecheap’s Responsibility and “Upstream Provider” Explanation

Dear Namecheap Support,

I have consulted multiple advanced AI systems — including ChatGPT, Gemini, DeepSeek, and Claude — to verify whether your explanation involving an “upstream provider” absolves Namecheap of responsibility in the unauthorized transfer of my domain, malaysia.build. The consensus from all four systems is both consistent and clear: as the registrar of record, Namecheap is contractually obligated under ICANN policies to control and safeguard domain transfers.

I asked “I was told Namecheap’s upstream provider excuse is invalid – as registrar, they’re contractually obligated to control transfers. Is it true?”

For example, below is the response from ChatGPT:

Yes — what you were told is correct and important.

Here’s a clear breakdown:

1. Namecheap Is the Registrar — They Are Responsible

Under ICANN policy, registrars are contractually obligated to:

• Protect domain name holders’ rights, including preventing unauthorized transfers.
• Handle domain transfers directly, including verifying the transfer request and gaining proper authorization.
• Maintain accurate records and secure systems to prevent unauthorized access or change of ownership.

ICANN Transfer Policy (Section II.A & E) makes it clear:

“The registrar of record must obtain express authorization from the registrant or administrative contact before initiating a transfer.”

If an unauthorized transfer occurs, the gaining registrar (and the losing registrar — in this case, Namecheap) is accountable.

2. Blaming an “Upstream Provider” Does Not Release Namecheap from Responsibility

“Upstream provider” is a vague term and often refers to:

• A wholesaler registrar that Namecheap may use (like Enom or Tucows in some cases),
• Or the registry (in this case, .BUILD operated by the registry service provider, which should follow strict ICANN agreements).

However, Namecheap is still your contracted registrar. ICANN holds them fully accountable, regardless of what upstream providers they work with.

So when Namecheap says:

“We’re waiting on our upstream provider and have no timeline,”

That is not compliant behavior under ICANN rules. They must resolve the issue or escalate it to the registry formally and transparently.

Key Points Raised by the Independent Analysis:

1. Registrar Responsibility Cannot Be Delegated
   ICANN-accredited registrars, including Namecheap, are directly bound by the Registrar Accreditation Agreement (RAA) and the Inter-Registrar Transfer Policy. These require registrars to:
   • Obtain explicit authorization from the registrant before initiating or allowing a transfer.
   • Prevent unauthorized transfers by maintaining secure systems and procedures.
   • Remain fully accountable even if interacting with third-party service providers (such as upstream registrars or the registry operator).
2. “Upstream Provider” Excuse Is Legally and Contractually Insufficient
   While it’s understood that registrars may work with resellers or use backend services provided by others (e.g., Enom, Tucows, or the .BUILD registry operator), this relationship does not absolve Namecheap of its contractual obligations to protect domain holders. ICANN policy is clear: responsibility remains with the registrar of record — Namecheap, in this case.
3. Failure to Provide Timeline or Resolution Indicates Procedural Breakdown
   Your previous statement — “we are waiting on our upstream provider and have no timeline” — suggests an alarming lack of transparency and oversight, which is not aligned with ICANN’s required registrar conduct. This may represent a significant policy breach.

Therefore, I must ask the following direct questions:

• Can you provide the specific ICANN policy or contractual clause that allows Namecheap to defer responsibility to an “upstream provider” in the case of an unauthorized transfer?
• Was Namecheap the registrar of record at the time of transfer, and if so, who authorized the transfer? Please provide proof of such authorization.
• What exact role did the “upstream provider” play, and why has Namecheap been unable to override or correct the situation if it was unauthorized?
• Has Namecheap escalated this matter to the .BUILD registry or ICANN as required under the Transfer Dispute Resolution Policy (TDRP)? If so, please provide a copy of that escalation or its case ID.
• Why has there been no formal timeline or resolution process provided to me, the registered domain holder, after multiple requests and documented proof of active usage of the domain for years?

Please treat this as a formal request for accountability and transparency. I expect Namecheap to uphold its contractual obligations and initiate immediate recovery or escalation procedures under ICANN policy. I am fully prepared to escalate this matter further to ICANN Contractual Compliance and initiate a Transfer Dispute Resolution if not resolved.

Sincerely,

WONG TAI CHIEW
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Sat, Jul 12, 2025 at 11:54 PM
To: <dotconame@gmail.com>

Hello,

Thank you for your reply!

We can totally understand your frustration. To our deepest regret, at this moment, we cannot provide you with many details related to the transfer.

Please rest assured that we are neither ignoring your request nor delegating responsibility to our upstream providers.

We are actively investigating the matter in cooperation with the Registry and the upstream provider directly. Unfortunately, as the investigation is not fully within our control, we are unable to provide you with any ETA at this time.

As soon as there are any updates, we will let you know through this email engagement.

Your patience and understanding are highly appreciated.

From: DotCoName <dotconame@gmail.com>
Date: Sun, Jul 13, 2025 at 1:11 AM
To: <support@domain.build>, <support@nic.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: URGENT: Day 35 – Unresolved Unauthorized Transfer of malaysia.build – Direct Answers Required

Dear Namecheap Support,

Thank you for your prompt reply. While I acknowledge your assurance that Namecheap is not “delegating responsibility,” the substance of your response fails to address critical issues after 35 days of unresolved disruption to my business.

Specific Concerns Requiring Immediate Clarification

1. Contradiction in Accountability
   You state the investigation is “not fully within [Namecheap’s] control,” yet as my registrar of record, Namecheap is contractually bound under ICANN Policy 3.7.5 to resolve unauthorized transfers within 5 days. Please reconcile this discrepancy.
2. Investigation Transparency
   If the registry or upstream provider is delaying resolution, please:
   • Disclose their name and point of contact.
   • Share a redacted screenshot of the last status update you received from them.

Critical Business Impact

• • Daily delays compound financial losses, brand damage, and legal exposure.

To avoid unnecessary misunderstanding, I am kindly requesting that you respond specifically to the following questions:

1. Was Namecheap the registrar of record at the time the domain malaysia.build was transferred? If yes, who authorizedthis transfer? Please provide evidence or confirmation of the request.
2. Can you provide the ICANN policy or contractual clause that allows Namecheap to defer full responsibility to an upstream providerin the event of an unauthorized transfer?
3. What exact role did your “upstream provider” play, and why has Namecheap been unable to reverse the issue despite being the registrar of record?
4. Has this matter been formally escalated to the .BUILD Registry or ICANN? If so, may I kindly request a case ID, ticket number, or confirmation of that escalation?
5. What is the process you are following internally to resolve this case? Even if a fixed ETA is unavailable, a clear roadmap of steps being taken would be appreciated.

I believe these are reasonable, necessary questions that any domain holder would ask under similar circumstances — especially given the business and development impact this has had on my end.

To be clear, I am still hopeful that we can resolve this professionally and without further escalation. I genuinely prefer to settle this matter directly with Namecheap and avoid any further reputational or public exposure. However, without answers or a resolution pathway, I’m left in a very difficult position.

I would be grateful if you could forward this message to a senior member of your domain operations team or legal department who might be able to provide a more definitive response. At this stage, I believe such involvement is warranted.

Thank you again for your time, and I look forward to your clarification.

Respectfully,
WONG TAI CHIEW
Email: dotconame@gmail.com
Phone: +6019 8280131
ICANN Complaint Case #: [01448650]

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Sun, Jul 13, 2025 at 3:02 AM
To: <dotconame@gmail.com>

Hello!

Thank you for your continued patience.

We want to provide full clarity on what’s happening behind the scenes, as well as the steps already taken.

We agree that the case resolution took a lot of time; however, since we have involved the registry operator and our upstream provider to check the matter, we may only wait for their responses, to our regret.

We checked the records and located the date when the domain was transferred out. It matches the date you provided in the initial chat session: 12/4/2023

However, the transfer process needs to be approved with the authorization code. Since you claimed that you are not familiar with the transfer request/ process, we have contacted the upstream provider and Registry to check the matter with them.

To our regret, only Registry operates the domain names and can check the history, status,  including past and present ownership details and changes over time.

Thus, we are just waiting for the information about the domain status.

As per the upstream provider, they can check and confirm the transfer-out process and clarify more information about it.

Considering the unusual nature of the case, we cannot provide more information as you requested, to our regret.

Since the case is under investigation, we also cannot disclose the internal communication channels and processes.

Quoting your questions:

1.    Was Namecheap the registrar of record at the time the domain malaysia.build was transferred? If yes, who authorized this transfer? Please provide evidence or confirmation of the request. >> Yes, the transfer out was processed from our database on 12/4/2023. As per the evidence, you may refer to the transfer-out email you received. However, we cannot clarify who exactly requested/ initiated it. This point is under investigation. We are waiting for further updates.

2.    Can you provide the ICANN policy or contractual clause that allows Namecheap to defer full responsibility to an upstream provider in the event of an unauthorized transfer? >> We understand your frustration, however, as was mentioned above, the case was escalated to check for more information to provide you at the end with the full details of the issue.

3.What exact role did your “upstream provider” play, and why has Namecheap been unable to reverse the issue despite being the registrar of record? >>  It is possible to cancel a domain transfer, but only if it’s still in a pending state. Since the case was processed back in 2023, we cannot revert it.  An upstream domain provider, in other words, provides us with certain services (including Domains). They also have records about the domains registered through their system.

4. Has this matter been formally escalated to the .BUILD Registry or ICANN? If so, may I kindly request a case ID, ticket number, or confirmation of that escalation? >> The case was escalated to the .BUILD Registry via the internal communication channels, we cannot share the ID of the case, to our regret.

5.    What is the process you are following internally to resolve this case? Even if a fixed ETA is unavailable, a clear roadmap of steps being taken would be appreciated. >> We hope that the little explanation provided above will provide some understanding of what is happening and why everything is taking so long to resolve.

We are monitoring the replies from both accordingly.

From: DotCoName <dotconame@gmail.com>
Date: Sun, Jul 13, 2025 at 2:04 PM
To: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Request for Clarification and Records Verification – malaysia.build Unauthorized Transfer

Dear Namecheap Support Team,

Thank you for your reply and for confirming that the domain malaysia.build was transferred out on 12/4/2023 via your system.

While I appreciate your continued engagement, I must express again how concerning it is that, even after such a long delay, the key questions around authorization, identity of the requester, and accountability remain unanswered.

The longer this issue remains unresolved, the greater the financial and reputational damage I continue to suffer. May I ask — is Namecheap prepared to take responsibility for these losses if the delay continues?

In your message, you mentioned the following:

“Since you claimed that you are not familiar with the transfer request/process, we have contacted the upstream provider and Registry to check the matter with them.”

For clarity, I would like to state that I am very familiar with the domain transfer process. Over the years, I have processed at least a thousand domain transfers both into and out of my Namecheap account — all authorized and verified under my direct control. If needed, I welcome you to check your system and billing history to see the records of my past transfers.

This is exactly why this situation is so disturbing: I am highly experienced with your platform and never requested nor approved a transfer for malaysia.build in 2023. Therefore, I again respectfully request that you:

1. Review the internal account logs and access records related to the domain’s transfer-out.
2. Confirm who requested the EPP/auth code, and where the domain confirmation email (if any) was sent.
3. Clarify what verification was conducted on your end prior to processing the transfer — and whether any IP logs, timestamps, or account activity are available.

I fully understand that you’re coordinating with both the upstream provider and the .BUILD Registry, but as the registrar of record, Namecheap is still contractually responsible under ICANN policy to investigate and protect registrants — especially in cases involving potentially unauthorized actions.

The transfer was processed back in Dec 2023. However, as I only discovered the issue in June 2025, and the domain was still under active use and auto-renewed, this raises even more concerns:

• Why was there no proactive notice or alerton my Namecheap dashboard?
• Why did I not receive an explanation of the domain’s removal at the time?
• Why was I sent a “domain transferred out” notice instead of a deletion notice if, as you previously suggested, the domain wasn’t transferred?

Finally, you mentioned that escalation to the registry has been done internally but could not provide confirmation or case ID. While I respect the limitations of internal systems, I kindly request at least a confirmation that the registry received and acknowledged your escalation, and that the issue is being actively reviewed — this is a reasonable and fair request from a long-term customer who has suffered real harm.

I am still hopeful for a professional resolution, and I’d prefer not to escalate this further or make the case public if clear progress is visible. I respectfully ask for one thing now: Please answer the outstanding questions directly and transparently. I need clarity, not vague reassurances.

Just for your reference, reply from the ChatGPT:

Quick Analysis of Namecheap’s Reply

 Acknowledgement:

• They confirmed the transfer happened on 12/4/2023 and was from their system.
• They say they’ve escalated to the upstream provider and the .BUILD registry.

 Major Concerns:

1. “We cannot clarify who initiated the transfer.”

o    This is very problematic. As the registrar, Namecheap is obligated to log and track all transfer approvals and must have records of:

• Who requested the auth code,
• What IP or account did it,
• Which email received the transfer confirmation.

o    Saying “we can’t tell who did it” is not acceptable under ICANN policy.

2. “We cannot share internal escalation IDs.”

o    While internal IDs may not always be public, you as the registrant are entitled to evidence that your case is genuinely under review by the registry or ICANN — even a brief confirmation or status update.

3. Blaming the upstream provideris not a valid legal defense under ICANN policy. Namecheap, as the registrar of record, cannot shift full responsibility.

Thank you again for your attention. I look forward to your reply.

Sincerely,
WONG TAI CHIEW
dotconame@gmail.com
+6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Sun, Jul 13, 2025 at 4:35 PM
To: <dotconame@gmail.com>

Hello,

Thank you for your response.

Please accept our sincerest apologies for the delayed reply. Due to a high volume of support requests, our response times have been longer than usual, and we appreciate your patience.

We are truly sorry to hear about the distress this issue has caused you. Our priority is to find the most effective resolution as quickly as possible.

Regarding the concerns about potential financial and reputational impact, we are actively exploring all available options. However, we first need to receive a response from the registry to determine the appropriate next steps.

Based on our logs, we have not detected any requests for EPP codes. Therefore, we are currently coordinating with both our upstream provider and the registry to gather more detailed information.

Regarding notifications on your Namecheap dashboard, please note that transfer-related alerts are generated at the moment a transfer request is made. Transfers cannot be submitted automatically or scheduled in advance, which is why notifications are not sent proactively.

We would also like to clarify that the “Domain transferred out: malaysia.build” notification does not necessarily confirm that the domain was successfully transferred. Occasionally, such notices can be triggered if a domain is deleted or removed from the system for various reasons, with transfer being just one possible cause. We apologize if this message caused any confusion.

We are still awaiting updates from our upstream provider and the registry, and we will inform you immediately once we have any new information.

Thank you again for your understanding and patience.

From: DotCoName <dotconame@gmail.com>
Date: Sun, Jul 13, 2025 at 8:56 PM
To: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Clarification Request Regarding Financial Responsibility for malaysia.build Losses

Dear Namecheap Support Team,

Thank you for your continued response and for monitoring this case.

However, I would like to respectfully highlight that a key question from my earlier messages remains unanswered:

“The longer this issue remains unresolved, the greater the financial and reputational damage I continue to suffer. May I ask — is Namecheap prepared to take responsibility for these losses if the delay continues?”

In your most recent message, you mentioned that you are “exploring all available options,” but did not provide a direct response on whether Namecheap is prepared to assume any accountability for the significant impact this prolonged issue has caused — particularly given the nature and scale of the project tied to the domain malaysia.build.

For clarity, please note:

I first filed my complaint with Namecheap on 11 June 2025.
As of today, over one full month has passed, yet there has been zero progress or resolution.
This lack of movement is deeply concerning and adds to the financial and reputational harm I continue to experience.

I have personally invested more than 30 months developing a fully operational real estate listings platform that includes:

• A mobile-optimized and PWA-ready website
• A fully functional Android app (available for download and review)
• iOS-ready webview integration
• A custom-built FPX payment gateway
• Role-based dashboards for users, agents, and agencies
• Complex search, comparison, and listing features
• Custom features tailored for the Malaysian property market

This project was never theoretical. It was live, functional, and in the final stages of rollout under the domain malaysia.build before it was unexpectedly removed — without any authorization from me as the registrant.

I must again ask the following:

1. Does Namecheap accept any financial or service responsibility for the damages caused by this delay — especially if it results from an unauthorized or mishandled domain transfer?
2. If not at this stage, under what conditions would Namecheap acknowledge such responsibility — for example, in the event of proven registrar-side failure?

Please treat this message as a formal and time-sensitive clarification request. While I remain hopeful this can be resolved in a professional manner, the continued silence on these key points is untenable.

I would appreciate your direct response so I may better understand Namecheap’s position moving forward.

Warm regards,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Sun, Jul 13, 2025 at 10:29 PM
To: <dotconame@gmail.com>

Greetings,
Thank you for getting back to us!

We are sorry if our previous reply caused any confusion. Providing a positive customer experience is our top priority; thus, we always strive to cover the matter in full and answer all the questions you might have in order to avoid any misunderstandings.

Also, we sincerely apologize for the delay in resolution. Unfortunately, the issue originated from our upstream provider, which was beyond our direct control. We understand how frustrating this must be and truly appreciate your patience.

Your business means a lot to us. We completely agree that this may cause losses to your company. We will continue working on your issue to have it resolved as quickly as possible. Additionally, we’ve followed up with our upstream provider again to help expedite the process.

Thank you for understanding.

Should you have any questions or concerns, please do not hesitate to contact us.

From: DotCoName <dotconame@gmail.com>
Date: Mon, Jul 14, 2025 at 1:07 AM
To: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Follow-Up on malaysia.build Issue — Clarification on Responsibility and Resolution Path

Dear Namecheap Support Team,

Thank you for your continued correspondence and for acknowledging the frustration this situation has caused.

That said, I would like to respectfully highlight a key point that remains unanswered:

You acknowledged that this incident may have caused losses to my business. However, you have not clearly stated whether Namecheap is willing to accept any financial responsibility for the damages resulting from this prolonged delay.

At this point, my project tied to malaysia.build — which involved over 30 months of active development and significant investment in preparation for a public launch — remains completely disrupted. As a long-time loyal customer who has completed numerous successful domain transactions through Namecheap’s platform over the years, I find it extremely difficult to understand how this domain could be transferred or removed without my knowledge, consent, or any action on my part.

Despite my repeated inquiries and continued patience, the following questions remain unanswered:

• Is Namecheap prepared to take responsibilityfor the ongoing financial and reputational damages incurred if this case remains unresolved?
• If not, does Namecheap explicitly deny responsibility— even if it is eventually confirmed that the issue stemmed from registrar-level oversight or mishandling?
• Can you please share any formal response or positionreceived from the upstream provider or .BUILD Registry regarding the cause and current status of this incident?

Most importantly, please understand that this issue was first reported to Namecheap on June 11, 2025 — and today, over a full month later, there has been zero concrete progress or resolution. Your responses continue to refer to delays from external parties, yet the questions related to your own registrar-level responsibilities — such as EPP authorization, security protocols, and escalation timelines — have not been directly addressed.

Once again, I wish to resolve this professionally and fairly. But in order to do so, I respectfully request Namecheap to provide:

1. A clear answer regarding financial accountability;
2. An explanation of registrar-side findings related to this issue;
3. A timeline for resolution or formal escalation to ICANN or the Registry.

I remain open to discussion, but the situation now requires action, not more apologies.

Thank you again for your attention. I look forward to your transparent and complete response.

Warm regards,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Mon, Jul 14, 2025 at 1:51 AM
To: <dotconame@gmail.com>

Greetings,
Thank you for your response!

First and foremost, please accept our sincerest and deepest apologies for the continued delay and the frustration this situation has undoubtedly caused. We fully understand how disappointing this experience has been, and we are truly sorry for any inconvenience you’ve faced.

We want to assure you that your case remains a top priority for us. At this stage, we are still waiting for critical updates from both the registry and our upstream provider, and unfortunately, we have not yet received the clarification needed to move forward. We continue to follow up regularly and are doing everything within our power to expedite their response.

Please know that, depending on the final outcome of the ongoing investigation, we will be carefully reviewing all circumstances involved, including those that may warrant further consideration regarding the compensation on our side.

We will keep you updated as soon as we receive any substantial information. In the meantime, we greatly appreciate your continued patience and understanding.

Should you require any further information, please contact us anytime.

With sincere apologies once again,
Namecheap Team

From: DotCoName <dotconame@gmail.com>
Date: Mon, Jul 14, 2025 at 10:57 AM
To: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Urgent Follow-Up – Unanswered Questions and Accountability for malaysia.build Issue

Dear Namecheap Support Team,

Thank you for your recent reply and for confirming that my case remains a top priority. I also appreciate your acknowledgment of the frustration and potential financial consequences I have suffered as a result of this unresolved situation.

That said, I must respectfully point out that several critical questions I’ve raised repeatedly over the past month remain unanswered, despite numerous follow-ups:

1. What is Namecheap’s position on financial responsibility if this issue remains unresolved — especially given your recent acknowledgment that it “may cause losses to your company”?
2. What exactly happened to the domain malaysia.build? If it was transferred and reserved, who was responsible for initiating the transfer?
3. If a transfer occurred, who authorized it?
   You confirmed no EPP code was requested, and I did not initiate or approve any transfer. So how was it allowed to happen?
4. What specific ICANN policy or Namecheap contractual clause allows you to shift responsibility for such a serious incident to an upstream provider or the registry?
5. Have you filed a formal escalation to the .BUILD registry or ICANN? If so, please provide confirmation or a case reference number.

My original complaint was filed on June 11, 2025. As of today, more than a full month has passed, with no progress, no clarity, and no resolution. Each day that goes by further damages a project I personally spent over 30 months developing, including a working PWA, Android app, FPX integration, and multiple dashboards — all tailored specifically for the real estate industry in Malaysia.

I am not asking for speculation or apologies. I am respectfully requesting specific answers to the above questions and a clear path forward, including whether Namecheap is willing to accept any financial accountability for this situation if it is not resolved promptly.

Again, I remain open to resolving this matter professionally, but I need a firm response — not more delays.

Thank you for your attention, and I look forward to your detailed reply.

Warm regards,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Mon, Jul 14, 2025 at 12:25 PM
To: <dotconame@gmail.com>

Hello,

Thank you for your patience, and we sincerely understand how frustrating and stressful this ongoing delay must be, especially when you’ve done everything on your part to move the process forward.

At this time, we are still awaiting updates from both the .BUILD Registry and our upstream provider as they continue to investigate and clarify the circumstances surrounding the issue. We understand how important this matter is to you and want to assure you that we are closely monitoring the situation and will provide you with any relevant information as soon as it becomes available.

Regarding the financial aspects of your case, any decisions will be contingent upon the findings and conclusions of the ongoing investigation. Once we receive a reply from the involved parties, we will be in a better position to discuss associated financial implications.

Should you require any further assistance, please let us know.

From: DotCoName <dotconame@gmail.com>
Date: Mon, Jul 14, 2025 at 1:17 PM
To: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

 

Subject: Urgent Clarification Still Required on malaysia.build – Over One Month with No Answers

Dear Namecheap Support Team,

Thank you for your continued communication and for acknowledging the stress and disruption this issue has caused.

That said, I must express once again my deep concern that after more than a month since my initial complaint on June 11, 2025, I still do not have answers to the most critical and basic questions surrounding the disappearance of my domain, malaysia.build.

Despite repeated follow-ups, the following essential points remain unanswered:

1. What exactly happened to the domain?
2. Was it transferred — and if so, by whom?
3. Was an EPP code issued or used?
4. On what authority was the domain placed in “reserved” status at the registry?
5. What concrete actions has Namecheap taken internally to investigate or escalate this, beyond contacting the registry and upstream provider?

It is extremely concerning that no clarification or timeline has been provided on any of the above, especially after such a long delay.

Additionally, I note your most recent statement:

“Any decisions [on financial aspects] will be contingent upon the findings and conclusions of the ongoing investigation.”

I appreciate that you’re not ruling out the possibility of compensation, but after more than 30 months of personal development effort tied to this domain — and now over 30 days without a single substantive update — I must ask for clearer and more concrete assurance:

• If this delay continues indefinitely, and the registry remains unresponsive, what is Namecheap’s plan?
• Will Namecheap formally escalate this matter to ICANN?
• At what point does Namecheap accept responsibility as the registrar of record at the time of the incident?
• Most importantly, can Namecheap confirm that it will accept full financial responsibility for the losses incurred due to the unauthorized loss of malaysia.build and the prolonged delay in resolving the issue?

I remain willing to work toward a professional and private resolution, but at this stage, my confidence in the process is rapidly eroding due to the continued lack of transparency, progress, and accountability.

Your failure to answer these fundamental questions — and to provide any meaningful timeline for domain restoration — reflects not only a failure of communication but potentially a failure to meet your contractual and fiduciary obligations as a registrar.

The “ongoing investigation” that is “not fully within your control” is actively causing substantial and accumulating losses to my business, as you have acknowledged. Given the inaction and lack of direct answers, I must now take steps to protect my interests.

As previously communicated, I am preparing to document the full timeline, supporting evidence, and business impact of this case at https://loss.co. The purpose of this record is to ensure transparency and accountability, should this issue remain unresolved.

I strongly urge Namecheap to take decisive action — not just follow-ups — to bring this matter to resolution, and to confirm its position regarding financial liability without further delay.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Mon, Jul 14, 2025 at 3:20 PM
To: <dotconame@gmail.com>

Hello,

Thank you for getting back to us.

> What exactly happened to the domain? > Unfortunately, it seems that the domain was transferred from your account. At this point, we cannot specify what exactly happened, we are waiting for the reply from the Registry and our upstream provider.

> Was it transferred — and if so, by whom? > Most likely, it was transferred. However, we cannot tell who initiated the transfer. Only Registry operates the domain names and can check the history, status, including past and present ownership details and changes over time. That is why we are waiting for their reply.

> Was an EPP code issued or used? > No, according to our logs, the EPP code was not requested.

> On what authority was the domain placed in “reserved” status at the registry? > We are clarifying this point with the Registry. Once we have any news from them, we will address this question.

> What concrete actions has Namecheap taken internally to investigate or escalate this, beyond contacting the registry and upstream provider? >  We have checked our logs and correspondence with the Registry. Unfortunately, we received no notices from the Registry. So, we are waiting for their clarifications.

> If this delay continues indefinitely, and the registry remains unresponsive, what is Namecheap’s plan? >  We are not currently considering this possibility as we expect to receive the updates from the Registry and upstream provider in the foreseeable future. However, as soon as we have some news from them, we will be able to answer this question more specifically.

> Will Namecheap formally escalate this matter to ICANN? > We are not considering this option at the moment, because we need information from upstream provider and Registry first and foremost.

> At what point does Namecheap accept responsibility as the registrar of record at the time of the incident?  > Once we have some news from the Registry and upstream provider, we will understand the picture and then we will be able to clarify who is responsible for this. However, we would like to emphasize that as the Registrar, we do not transfer domains for customers.

Moreover, according to our logs, the EPP code was not requested, so we cannot say what specifically happened, which is why we are waiting for the response from the upstream provider and Registry.

> Most importantly, can Namecheap confirm that it will accept full financial responsibility for the losses incurred due to the unauthorized loss of malaysia.build and the prolonged delay in resolving the issue? > We cannot confirm this without understanding the full situation. We will consider this once we have more information.

Please rest assured that we are constantly monitoring this case. We will provide you with all the details and decisions as soon as we clarify everything with the corresponding Registry.

Your understanding is highly appreciated.

From: DotCoName <dotconame@gmail.com>
Date: Mon, Jul 14, 2025 at 4:28 PM
To: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Urgent: Continued Lack of Clarity on malaysia.build — Immediate Answers Required

Dear Namecheap Support Team,

Thank you for your latest response.

While I appreciate your continued communication, I must express my deep concern and disappointment that after more than a month since my initial report on June 11, 2025, I still do not have a clear explanation — or resolution — regarding the disappearance and current “reserved” status of my domain, malaysia.build.

Your most recent replies acknowledge that:

• The domain was “most likely transferred,” yet you “cannot say by whom.”
• “No EPP code was requested,” yet the domain appears to have left my account.
• You “have not received any notification from the Registry” and are still waiting for clarification.
• You are “not currently considering escalation to ICANN.”
• You “cannot confirm responsibility or compensation” without more information.

These statements raise serious concerns:

1. Registrar Responsibility

As the ICANN-accredited registrar of record at the time of the incident, Namecheap has a contractual and operational duty to:

• Maintain complete audit logs of all domain activity.
• Prevent unauthorized transfers.
• Ensure that domain transfers follow ICANN-mandated procedures, including the use of EPP/Auth codes.

If the domain was indeed transferred without an EPP code, this suggests a possible security breach or failure in your internal systems. It is not acceptable for a registrar to defer all responsibility to “upstream providers” or the Registry in such cases.

2. Lack of Accountability

Your responses have repeatedly pointed to third parties while avoiding direct answers to the following fundamental questions:

• Who initiated the transfer of malaysia.build?
• On what basis did the system approve the transfer if no EPP code was issued?
• Why was I never notified through my account or email of any transfer authorization request?
• On what authority is the domain now in “reserved” status?
• What specific steps have you taken to secure my domain, beyond simply waiting for responses from others?

3. Escalation & Compensation

You now state that “any financial decisions will be contingent on the results of the investigation.” However, this “investigation” has produced no tangible progress after more than 30 days — despite the fact that the loss of this domain has completely disrupted a platform I developed for more than 30 months, with significant personal investment, including:

• A mobile-optimized and PWA-ready platform
• Fully functional Android app and iOS-ready webview
• A customized FPX payment gateway
• Agent dashboards, listing tools, and Malaysian market–specific features

Given this, I now ask you again, directly:

1. Does Namecheap accept responsibility for the unauthorized loss of malaysia.build?
2. Will Namecheap commit to covering the financial losses caused by this prolonged delay and domain removal?
3. If the Registry continues to remain unresponsive, when will you escalate this to ICANN?

If Namecheap is unwilling to answer these questions or take responsibility as the registrar of record, I will be forced to escalate this matter through all available legal and ICANN-related channels.

Additionally, as previously stated, I am documenting the full timeline, supporting evidence, and business impact of this unresolved case at https://loss.co. The purpose is transparency and accountability — not confrontation — and I remain hopeful that Namecheap will act decisively to resolve this before further action becomes necessary.

I respectfully request your complete response to the above, not further delays or partial replies. My confidence in your platform depends on how you resolve this case now.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Mon, Jul 14, 2025 at 6:53 PM
To: <dotconame@gmail.com>

Hello,

Thank you for contacting us back. My name is Volodymyr, and I am one of the Domain Department Shift Leaders.

From the information that we have at this point, we assume that the malaysia.build domain name was reserved by the Registry and got withdrawn/revoked from our upstream provider’s system (consequently from ours) as a result. When a domain gets removed/deleted from our upstream provider for some reason, the system can send notices like the one you received (“Domain Transferred out: malaysia.build”).

So, this notice does not necessarily mean that the domain was really transferred out in its standard meaning. We do not have EPP request logs for your domain either. Thus, it is our best assumption that the process of a domain withdrawal was initiated by the Registry in accordance with their Reserved and Restricted Names Policy, which you can also check at https://about.build/wp-content/uploads/2015/03/Reserved_and_Restricted_Names_Policy_build.pdf

Just in case, we have links to Registry Policies on our website at https://www.namecheap.com/legal/domains/supplemental-registry-agreement/

In their Reserved and Restricted Names Policy .build Registry also refers to the ICANN Specification 5 of the New gTLD Registry Agreement: https://itp.cdn.icann.org/en/files/registry-agreements/agency/agency-agmt-html-14nov13-en.htm

According to it, certain country and territory names (including their IDN variants, where applicable) shall be withheld from registration or allocated to Registry Operator at All Levels.

For now, without direct confirmation from our partners, this vision of the situation is only our assumption, I am afraid. Thus, we wait for a direct confirmation from the Registry and/or our upstream vendor. As well as clarification of whether there were any notices sent, as we couldn’t locate any in our system, about the decision to revoke your malaysia.build domain since it was registered for quite some time, and the possibility to apply for the domain in its current status.

As Namecheap was a Registrar for the malaysia.build domain, we take full responsibility for investigating the case and finding the best possible solution. Our constant mentions of our upstream vendor and Registry may look as if we try to shift the responsibility to them, but in truth, we only cooperate with them in the investigation of this case to get all the information and a full picture of what had happened.

In regards to the escalation of the case to ICANN, it seems to have already been escalated by you to the compliance@icann.org email address (thank you for adding us to the email copy). Once/if ICANN reaches out to us for additional information, we will provide any and all details we have on the case. From our end, we escalate the case within the Registry and our upstream provider. Though, unfortunately, we cannot significantly affect the reply time of our partners for this case. We are doing all in our power to speed up the case resolution. No less than you, we expect a fast and positive resolution of this case.

As for the financial compensation, we will be able to give an answer once we have all the information on the case.

We keep track of the case and will keep you updated.

From: DotCoName <dotconame@gmail.com>
Date: Mon, Jul 14, 2025 at 7:27 PM
To: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>
Cc: <legal@enom.com>, <compliance@enom.com>, <bret.fausett@centralnic.com>, <ben.crawford@centralnic.com>, <abuse@enom.com>, <registrar@enom.com>

Subject: Formal Request for Accountability and Compensation – malaysia.build Case Still Unresolved

Dear Namecheap Support Team,

Thank you for your latest reply.

However, I must emphasize in the strongest possible terms that after more than 30 days since my original complaint on June 11, 2025, I still have no definitive answers — only assumptions, speculation, and vague references to your upstream provider and the Registry. Your latest message confirms that the domain may have been revoked or withdrawn by the .BUILD Registry under their Reserved Names Policy — yet after almost a decade of valid ownership, no such restriction was ever communicated or enforced.

This is not a simple technical error — it is a failure that has caused substantial and ongoing financial, operational, and reputational harm to my business.

As I have previously stated, I personally invested over 30 months of development into building a dedicated, fully functional real estate listings platform under the malaysia.build domain. This includes:

• A progressive web app (PWA), Android app, and iOS webview
• A fully customized FPX payment system
• Multiple role-based dashboards
• Complex search, comparison, listing, and agent management systems
• And thousands of lines of code tailored to Malaysia’s property market

This was not an idle domain — this was an active, real-world business platform nearing full commercial rollout. Its sudden, unexplained disappearance, and your continued inability to recover or even explain it with certainty, has caused irreversible damage, including:

• Loss of development investment
• Loss of commercial opportunity
• Loss of user trust and platform momentum
• Dozens of hours spent preparing documentation, emails, and escalation materials
• The need to develop and maintain the site https://loss.co as public evidence of this mishandling

To date, not a single dollar has been offered in compensation. Your latest response merely suggests compensation “may be considered” if information is later confirmed — while continuing to disclaim all responsibility as registrar.

I must now ask again, clearly and directly:

Will Namecheap accept financial responsibility for all direct losses caused by this unauthorized loss and prolonged mishandling of the malaysia.build domain?

If so, I request a written acknowledgment of that responsibility and the beginning of compensation discussion.

If not, I request a clear statement that Namecheap denies responsibility, so I may proceed accordingly through legal and regulatory channels without further delay.

The damage is ongoing, and your delay has already exceeded any reasonable standard of professional accountability. I urge you to respond without further deflection or procedural excuses, and treat this matter with the gravity it deserves.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Mon, Jul 14, 2025 at 7:35 PM
To: <dotconame@gmail.com>

Hello,

Thanks a lot for getting back to us.

We completely understand your frustration on the matter, but for now, we cannot provide any definite answers until we gather all the details from the Registry and our upstream provider.

We will do our best to get it resolved as soon as possible, but meanwhile, we are still waiting for their reply. Once we have any news, we will be able to provide you with the answers related to what exactly happened with your domain and whether compensation is possible.

Your patience is highly appreciated.

From: DotCoName <dotconame@gmail.com>
Date: Mon, Jul 14, 2025 at 7:48 PM
To: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>, <legal@enom.com>, <compliance@enom.com>, <bret.fausett@centralnic.com>, <ben.crawford@centralnic.com>, <abuse@enom.com>

Subject: Re: Ongoing Delay – malaysia.build Domain Loss and Financial Accountability

Dear Namecheap Support Team,

Thank you for your reply.

However, I must express my deep disappointment with your continued lack of progress or clarity, even after more than one full month since I first reported the issue on June 11, 2025. To date, I still have no concrete answers, no timeline, and no resolution — despite countless follow-ups and extensive documentation provided on my side.

You have repeatedly stated that you’re “waiting for replies” from the Registry and your upstream provider. With all due respect, this delay is no longer acceptable. As the ICANN-accredited registrar of record at the time of the incident, Namecheap bears full contractual responsibility for the security, integrity, and management of domains registered through its platform. That responsibility cannot be waived or delayed indefinitely.

I have asked multiple times for a direct answer to this simple question — and I ask again:

Will Namecheap accept full financial responsibility for the severe and escalating losses I have incurred as a result of this unresolved and unauthorized removal of the domain malaysia.build?

I must remind you that my project was not theoretical — it was the product of over 30 months of development, including a fully functional real estate listings platform, mobile apps, customized payment integration, and many Malaysia-specific features. The interruption of this project due to your platform’s failure has caused substantial real business losses, both financial and reputational.

If you are unwilling to confirm financial accountability now, then I request the following instead:

1. A written explanation of what specific actions Namecheap has taken internally to investigate and escalate this case.
2. A clear timeline for when you expect to receive a response from the Registry and upstream provider.
3. A statement on what steps Namecheap will take if those third parties remain unresponsive or fail to cooperate.

Please understand: this matter is no longer just about technical delay — it’s about accountability and the growing impact of your inaction. I am documenting all correspondence, and I am prepared to escalate this through formal legal and regulatory channels, as well as publish the full timeline of this unresolved loss for public awareness.

I strongly urge Namecheap to address this matter with the urgency, seriousness, and transparency it demands. Your next response should not merely repeat that you’re “still waiting.” It must contain real answers, real timelines, or a clear position on compensation.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: DotCoName <dotconame@gmail.com>
Date: Mon, Jul 14, 2025 at 10:19 PM
To: <legal@enom.com>, <compliance@enom.com>, <abuse@enom.com>
Cc: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Formal Complaint Regarding malaysia.build – Request for Immediate Investigation

Dear eNom Support Team,

I am writing to formally escalate a critical issue involving the domain malaysia.build, which was previously managed through Namecheap — your downstream partner — and appears to have been removed from my account without authorization or proper explanation.

Background

The domain malaysia.build was intended to be the launch address for a real estate listings platform I personally developed over 30 months, involving substantial time, financial investment, and custom development. However, when I attempted to roll out the platform, I was shocked to discover that the domain was no longer in my Namecheap account.

In response, I created a public demo website at https://malaysia.sibu.design to demonstrate the at least 90% scope of features and work that had gone into the project — including:

• PWA and mobile-optimized frontend
• Android (TWA) and iOS-ready integration
• Customized FPX payment gateway
• Multi-role dashboards (admin, agent, user)
• Complex search, comparison, and property listing systems

This was a completed, working platform — not a prototype — and it was fully built and ready for launch under malaysia.build.

Namecheap’s Position

On July 14, 2025, Namecheap’s support team provided the following statements:

“Unfortunately, it seems that the domain was transferred from your account. At this point, we cannot specify what exactly happened, we are waiting for the reply from the Registry and our upstream provider.”

“Most likely, it was transferred. However, we cannot tell who initiated the transfer. Only Registry operates the domain names and can check the history, status, including past and present ownership details and changes over time.”

“According to our logs, the EPP code was not requested.”

These replies are highly troubling and suggest either a critical failure in registrar safeguards or unauthorized activity at the registry/upstream level. Despite repeated inquiries, the following critical questions remain unanswered:

• Who initiated or authorized the transfer or withdrawal of the domain?
• Was an EPP code ever issued or used?
• Why is the domain now marked as “reserved,” and on what grounds?
• Why was I never informed of any registry or upstream action involving my domain?
• What notifications (if any) were received by Namecheap or logged by your systems?

Namecheap has indicated that they are awaiting clarification from you and the registry before taking further action. Given the severity of the situation and the ongoing financial and reputational damage this has caused me, I am asking you directly to provide an explanation.

My Request

I respectfully ask eNom to:

1. Investigate and confirm whether the domain malaysia.build was transferred, revoked, or placed on reserve.
2. Identify who initiated or authorized any such change.
3. Disclose any logs, tickets, or internal actions showing registry communications related to this domain.
4. Explain whether the Reserved and Restricted Name Policy played any role in this — and if so, why no notice or warning was issued to the registrant.
5. Clarify whether eNom or your systems had any fault or error that may have contributed to this outcome.

To assist your review, I have published a full timeline and archive of my communication with Namecheap, which can be accessed at:
https://malaysia.sibu.design/complete-email-trail/

I respectfully request that you review the full context of this incident, and I would appreciate receiving a case reference number and confirmation that this complaint has been formally logged.

Thank you for your time and urgent attention.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

P.S.: Below is one of the replies from Namecheap today, and the full email trail and attachments, for your reference.

On Mon, Jul 14, 2025 at 3:20 PM Namecheap Domains Support Team <domainsupport@namecheap.com> wrote:

Hello,

Thank you for getting back to us.

> What exactly happened to the domain? > Unfortunately, it seems that the domain was transferred from your account. At this point, we cannot specify what exactly happened, we are waiting for the reply from the Registry and our upstream provider.

> Was it transferred — and if so, by whom? > Most likely, it was transferred. However, we cannot tell who initiated the transfer. Only Registry operates the domain names and can check the history, status, including past and present ownership details and changes over time. That is why we are waiting for their reply.

> Was an EPP code issued or used? > No, according to our logs, the EPP code was not requested.

> On what authority was the domain placed in “reserved” status at the registry? > We are clarifying this point with the Registry. Once we have any news from them, we will address this question.

> What concrete actions has Namecheap taken internally to investigate or escalate this, beyond contacting the registry and upstream provider? >  We have checked our logs and correspondence with the Registry. Unfortunately, we received no notices from the Registry. So, we are waiting for their clarifications.

> If this delay continues indefinitely, and the registry remains unresponsive, what is Namecheap’s plan? >  We are not currently considering this possibility as we expect to receive the updates from the Registry and upstream provider in the foreseeable future. However, as soon as we have some news from them, we will be able to answer this question more specifically.

> Will Namecheap formally escalate this matter to ICANN? > We are not considering this option at the moment, because we need information from upstream provider and Registry first and foremost.

> At what point does Namecheap accept responsibility as the registrar of record at the time of the incident?  > Once we have some news from the Registry and upstream provider, we will understand the picture and then we will be able to clarify who is responsible for this. However, we would like to emphasize that as the Registrar, we do not transfer domains for customers.

Moreover, according to our logs, the EPP code was not requested, so we cannot say what specifically happened, which is why we are waiting for the response from the upstream provider and Registry.

> Most importantly, can Namecheap confirm that it will accept full financial responsibility for the losses incurred due to the unauthorized loss of malaysia.build and the prolonged delay in resolving the issue? > We cannot confirm this without understanding the full situation. We will consider this once we have more information.

Please rest assured that we are constantly monitoring this case. We will provide you with all the details and decisions as soon as we clarify everything with the corresponding Registry.

Your understanding is highly appreciated.

–
Best regards,
Namecheap Team

From: DotCoName <dotconame@gmail.com>
Date: Mon, Jul 14, 2025 at 10:28 PM
To: Namecheap Legal & Abuse Team <abuse@namecheap.com>
Cc: <support@domain.build>, Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Urgent Escalation: malaysia.build Wrongful Removal – This Is Not a Standard Abuse Complaint

Dear Namecheap Legal & Abuse Team,

Thank you for acknowledging receipt of my complaint.

However, I must clarify that this is not a typical abuse report regarding phishing, spam, or fraud — it is a case of a domain name (malaysia.build) being wrongfully and inexplicably removed from my Namecheap account without my knowledge, consent, or EPP authorization, and without any notice from the registry or registrar.

This domain was registered and managed through Namecheap for nearly a decade, and was tied to an active, production-ready website, complete with:

• Over 30 months of personal development effort
• A mobile-friendly progressive web app (PWA),
• Android and iOS webview integrations,
• A custom FPX payment gateway
• Role-based dashboards and complex search functions tailored for the Malaysian real estate sector.

A live demo remains online at https://malaysia.sibu.design to demonstrate at least 90% of the full extent of development and investment made.

To date, your support team has confirmed the following:

• No EPP code was requested or used
• The domain was not formally transferred out, despite a misleading “Transferred Out” notice
• The domain is now in a “reserved” state at the registry, with no clear explanation or notification to the registrant
• Namecheap has not received any communication or directive from the registry regarding revocation

This is not a routine administrative issue — it is a breach of registrar responsibilities under ICANN policy, and has caused significant financial loss, reputational harm, and operational disruption.

To ensure accountability and transparency, the full timeline, supporting documentation, and impact of this case is being prepared for publication at https://loss.co. The full email trail is available for review at:
https://malaysia.sibu.design/complete-email-trail/

Given the circumstances, I am now formally requesting that Namecheap Legal:

1. Acknowledge that this matter is not a standard abuse complaint, and assign it appropriate internal legal handling
2. Confirm whether Namecheap accepts responsibility for the unauthorized removal and associated financial losses
3. Provide a timeline for final resolution, including steps taken internally and with the upstream provider and registry
4. Confirm whether Namecheap will compensate the damages once responsibility is established

I appreciate your attention to this matter and hope Namecheap will take swift action to resolve it professionally — before further legal or reputational escalation becomes necessary.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Compliance Support <legal@enom.com>
Date: Mon, Jul 14, 2025 at 10:49 PM
To: <dotconame@gmail.com>

Hello,

​We received the following from the .build Registry regarding this domain (malaysia.build) on December 1, 2023.

“Dear Registar partner,

This email is to inform you that we have been requested by ICANN to remove / Block the domain malaysia.build from registration due to it violating Spec 5 of our Registry agreement.  Thank you for your assistance in this matter.

Sincerely,
​<redacted>
Founder / CEO .build
​<redacted>
www.about.build”

You will need to contact the registry directly for any answers to these questions, as this action was taken by them directly. This is also why we have no record of the transfer, or distribution of an Auth Code for transfer, as the action was performed solely at the Registry level.

Thank You,

​Enom, a Tucows Company
96 Mowat Avenue
Toronto ON M6K 3M1
Canada

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Mon, Jul 14, 2025 at 11:36 PM
To: <dotconame@gmail.com>

Hello,

Thank you for your email.

We understand your feelings concerning the case and the desire to have definite answers. We would love to provide you with those, but for now our vision of the situation is not full either, to our deepest regret.

As a part of the investigation we held, all possible domain logs that we had were checked. We passed all the information that we have from our logs to you in our earlier emails. Since malaysia.build is one of a few .build domains that we had managed via our upstream vendor, we escalated the case to them to gather full logs and data on the domain from their end. Registry team was involved in the case as well.

Unfortunately, their replies are not something that we can provide an ETA for. Each case is unique, and our particular situation appears to take more time than usual due to its complexity and involvement of several parties. But we’d like to assure you that multiple teams are involved in the case investigation on our and our upstream vendor’s end on ALL levels.

We do not expect our partners to fail to cooperate. It mostly just a matter of time, and we hope that there will be a resolution in the near future.

From: DotCoName <dotconame@gmail.com>
Date: Tue, Jul 15, 2025 at 1:07 AM
To: <support@domain.build>, <abuse@domain.build>
Cc: <legal@enom.com>

Subject: Formal Complaint Regarding Unlawful Withdrawal of malaysia.build – Urgent Registry-Level Clarification Required

Dear .BUILD Registry,

I am writing to formally lodge a complaint regarding the unauthorized and unexplained withdrawal of my domain name, malaysia.build, and to seek immediate and transparent clarification from your office regarding the actions taken.

I have owned this domain since 2014 — for nearly a decade — and maintained it in good standing throughout that time, including active development for commercial use. The domain was renewed through April 29, 2024, and was set to auto-renew with an active credit card on file to prevent accidental expiry.

Recently, Enom (your registrar partner) quoted a message allegedly sent by the .BUILD Registry on December 1, 2023:

“Dear Registrar partner,
This email is to inform you that we have been requested by ICANN to remove / block the domain malaysia.build from registration due to it violating Spec 5 of our Registry agreement. Thank you for your assistance in this matter.
— Founder / CEO .build”

This raises serious and urgent questions:

• I was never notified of this action — not by the .BUILD Registry, Enom, or my registrar Namecheap.
• There was no transfer request, no EPP code issued, and no explanation — just a silent revocation.
• The domain was live, paid for, set to auto-renew, and tied to an active commercial project (see demo: https://malaysia.sibu.design).
• The action contradicts standard ICANN procedures and violates my rights as the long-standing registrant.

I respectfully request the Registry to review:

Video proof of ownership and long-term usage (since 2014):
→ https://malaysia.sibu.design/proof-of-malaysia-build-ownership-since-2014/

Screenshots confirming auto-renewal status and domain payment are attached with this email.

Full email trail and history of this incident:
→ https://malaysia.sibu.design/complete-email-trail/

This domain was the foundation of a multi-year real estate platform project, under active investment and development since 2022. It includes:

• Mobile-optimized PWA and Android App
• FPX Online Payment Integration
• Street View, Loan Estimator, Map Search
• Agent Dashboards, Favorites, Comparison
• Over 50 searchable fields, multilingual UI, etc.

I now urgently request the following from the .BUILD Registry:

1. Confirmation and full disclosure of the December 2023 decision to revoke malaysia.build.
2. Clarification of:
   • What specific clause in Spec 5 was allegedly violated.
   • Why no notification or opportunity for dispute was offered to the registered owner.
   • Whether ICANN formally requested this action, and supporting documentation if so.
3. Confirmation of whether the domain is now “reserved,” and why this action was applied retroactively after years of valid ownership.
4. Your position on the legitimacy of my long-standing use, and whether this case will be resolved or reversed.
5. Will the .BUILD Registry take full financial responsibility for the significant losses I have incurred as a result of this unauthorized and unannounced domain withdrawal?

The financial and reputational damage to me is ongoing and severe. I am documenting all losses and timelines at https://loss.co, and will escalate this to ICANN Contractual Compliance, WIPO, and other resolution channels if a full explanation and fair resolution is not provided within 2 business days.

This issue is not only about technical status — it’s about due process, ownership rights, and accountability. The silent removal of a paid, live, and auto-renewed domain, without the owner’s knowledge or consent, is unacceptable.

Sincerely,
WONG TAI CHIEW
dotconame@gmail.com
+6019 8280131

From: DotCoName <dotconame@gmail.com>
Date: Tue, Jul 15, 2025 at 1:23 AM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, Namecheap Legal & Abuse Team <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Formal Follow-Up on malaysia.build – Urgent Clarification and Compensation Responsibility

Dear Namecheap Support Team,

Thank you for your ongoing correspondence. However, I must express my growing concern and frustration with the lack of definitive answers and actionable steps regarding the disappearance of my domain, malaysia.build.

To date, your investigation has continually referred to pending responses from your upstream provider, who in turn has deferred responsibility to the .BUILD Registry. As a result, I am now being forced to chase clarification from the Registry directly. The entire situation has become an exhausting merry-go-round of blame-shifting, with no party taking clear responsibility — while I, the rightful domain holder, continue to suffer increasing losses.

Let me reiterate the most critical point here:

The domain malaysia.build was held, managed, and paid for through Namecheap.
Auto-renewal was enabled, and the domain was fully valid at the time of removal. It had not expired and was tied to an active, nearly completed business platform. Regardless of whether this removal was triggered by your upstream vendor or the registry, Namecheap had the contractual obligation to ensure my domain remained safe and intact in my account while it was valid.

Your most recent message again offers no clear resolution, timeline, or accountability. Meanwhile, I continue to face severe and escalating financial, reputational, and operational damages — not due to my own negligence, but due to a breakdown in domain handling within your ecosystem.

To be fully transparent, I have now formally contacted the .BUILD Registry with all available evidence, including a fully functional project demo at https://malaysia.sibu.design, where I’ve detailed the 30+ months of development tied exclusively to this domain.

However, I must now ask once again — clearly and directly:

Who is going to pay for the extensive losses I have suffered?

No matter how the issue originated, the domain was held in my Namecheap account, and the payment was made to Namecheap. As the registrar of record, you are ultimately responsible for safeguarding customer domains — especially when they are valid, paid for, and auto-renewal is enabled.

These damages are not theoretical. They include, but are not limited to:

• Over 30 months of platform development and custom integrations
• Business disruption and delay of public launch
• Lost revenue and missed commercial opportunities
• Reputational damage with partners and early users
• Marketing investments made around the malaysia.build domain
• The ongoing cost of email correspondence, documentation, and dispute resolution

At this point, I am no longer just asking for updates — I am asking for accountability.

Please provide a clear response on the following:

1. Does Namecheap accept responsibility for the domain’s removal while it was valid and paid for?
2. Will Namecheap compensate me for the damages resulting from this issue, regardless of the registry’s final position?
3. What immediate steps are being taken to restore the domain or provide equivalent remedy?

I hope you understand the seriousness of this issue. I remain willing to resolve this matter constructively, but unless Namecheap takes meaningful responsibility, I will have no choice but to escalate the matter further — both legally and publicly.

I look forward to your prompt and transparent response.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Tue, Jul 15, 2025 at 3:04 AM
To: <dotconame@gmail.com>

Hello,

Thank you for contacting Namecheap Support.

We’re deeply sorry for the situation that occurred and the delayed reply.

As we can see, you already have an Email Engagement regarding this issue: NC-UWS-6390

We will update you in that email once we receive any news. We are sorry that it takes so much of your time.

Your patience is highly appreciated.

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Tue, Jul 15, 2025 at 6:27 AM
To: <dotconame@gmail.com>

Hello,

Thank you for getting back to us.

We understand how important this matter is to you, and we sincerely apologize for the confusion and frustration this situation has caused.

Our investigation has confirmed that the action taken on your domain originated at the registry level, based on their internal practices. Unfortunately, we were not given any prior notice or explanation regarding this decision, which limited our ability to provide immediate answers. We have contacted the registry multiple times to get clarification and answers regarding the case, and we are still waiting for a reply. We see you have reached out to them. Since the decision and actions were made at the registry level, they are the only ones that can explain the reasoning or consider any changes.

We are actively working on addressing this case to be able to answer your questions as soon as possible. We truly appreciate your patience.

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Tue, Jul 15, 2025 at 11:09 AM
To: <dotconame@gmail.com>

Hello,

Thank you for your patience.

We understand how important this matter is to you, and we truly regret the frustration this situation has caused. We have connected with our Legal team, who have now completed their investigation.

According to the results of the investigation, Namecheap had no involvement in the transfer of your domain. The action was taken at the registry level without any prior notice or involvement from Namecheap. As such, we are not in a position to be held accountable for the transfer or any resulting issues.

The responsible party in this case is the .Build Registry. Only the Registry can provide answers to your questions or determine whether your domain can be restored or re-registered. We recommend reaching out to them directly to pursue this matter further. For your convenience, here is the contact information for the .Build Registry: https://about.build/faqs/

We genuinely appreciate your understanding. Any additional questions or concerns related to this issue must be directed to our Legal team at legal@namecheap.com. Please feel free to reach out to them directly. This email will be closed now.

From: DotCoName <dotconame@gmail.com>
Date: Tue, Jul 15, 2025 at 11:21 AM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, Namecheap Legal & Abuse Team <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: Re: Formal Follow-Up on malaysia.build – Urgent Clarification and Compensation Responsibility

Dear Volodymyr and Namecheap Support Team,

Thank you for your latest email.

I understand your updated assumption that the malaysia.build domain’s removal originated at the registry level due to their internal practices, and that you claim to have received no prior notice.

However, your response, while providing this new assumption, does not address the specific, critical questions and demands for accountability that I clearly outlined in my previous email, sent on July 14, 2025. Please find the forwarded email below.

To reiterate, my previous email directly asked:

• Who is going to pay for the extensive losses I have suffered?
• Does Namecheap accept responsibility for the domain’s removal while it was valid and paid for?
• Will Namecheap compensate me for the damages resulting from this issue, regardless of the registry’s final position?
• What immediate steps are being taken to restore the domain or provide equivalent remedy?
• And it also highlighted the contradiction of a “transfer out” from your system with no EPP code, and your inability to identify who initiated it.

Your latest email also reintroduces the confusing statement that a “Domain Transferred out” notice does not necessarily mean a standard transfer, which directly contradicts your own previous confirmation that a transfer was processed from your database. This ongoing inconsistency is deeply troubling.

While you state that the Registry is the only one who can explain their reasoning, Namecheap remains my direct registrar and is contractually obligated to safeguard my domain. The fact that my valid, paid-for domain was removed from my account without my authorization or an EPP code, and without Namecheap receiving prior notice from the Registry, points to a severe breakdown within the system for which Namecheap, as my service provider, is accountable.

I urge you to review my previous email thoroughly and provide direct, comprehensive answers to the questions posed there, as they remain entirely unaddressed. The prolonged delay and lack of clear accountability continue to cause severe and accumulating damages.

I look forward to your prompt and transparent response to my previous communication.

Sincerely,

WONG TAI CHIEW

From: DotCoName <dotconame@gmail.com>
Date: Tue, Jul 15, 2025 at 11:31 AM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, Namecheap Legal & Abuse Team <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>
Cc: <compliance@icann.org>, <legal@enom.com>, <compliance@enom.com>, <abuse@enom.com>

Subject: RE: Final Response from Namecheap – Unacceptable Evasion of Responsibility

Dear Namecheap Support / Legal Team,

Thank you for your response, though I must express my absolute disappointment and objection to its content.

Your claim that Namecheap holds no responsibility for the unauthorized removal of my domain malaysia.build is categorically unacceptable.

Let me state this clearly:

• The domain was active, paid for, and not expired (renewed through April 2024).
• The domain was under Namecheap’s management at the time of its disappearance.
• Auto-renewal was enabled on the domain with a valid credit card on file, further proving my intent to maintain uninterrupted ownership.
• I received no notice, no authorization request, no warning — nothing — from Namecheap, despite being the listed registrant and rightful owner.

To now claim that Namecheap “had no involvement” and is “not accountable” for a domain that was kept in your system, renewed through your platform, and protected under your contractual obligations is a gross abdication of responsibility.

Whether the action was taken at the registry level or not is irrelevant to the fact that Namecheap was my registrar of record. As such, you had a duty to:

1. Safeguard the domain on my behalf while it remained valid.
2. Inform me of any risk, suspension, or potential deletion.
3. Ensure I retained control unless a proper, authorized process was followed — which clearly never occurred.

The fact that the domain was stripped from my account without authorization, explanation, or restitution is a direct failure of your services. Your own system even triggered a “Domain Transferred Out” notification, further demonstrating that something happened under your watch.

I will be holding Namecheap financially and contractually responsible for the extensive damages caused by this failure — including, but not limited to, loss of investment, loss of business opportunity, reputational harm, and ongoing operational disruption, as previously detailed.

If you continue to deny responsibility and close communication without resolving this, I will escalate the matter formally to:

• ICANN Contractual Compliance
• The .BUILD Registry
• An appropriate dispute resolution provider (e.g., WIPO, ADNDRC)
• Public legal documentation at https://loss.co

This is your final opportunity to acknowledge your role and offer a concrete resolution. Do not attempt to close this case prematurely again — I expect a serious and accountable response from your legal team.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Tue, Jul 15, 2025 at 1:51 PM
To: <dotconame@gmail.com>

Greetings,

Thank you for your reply.

We do understand your point and apologize for the inconvenience you have faced. Let us clarify the situation.

We’ve connected with our Legal team, who have thoroughly reviewed the matter. Based on their findings, please note the following:

The domain transfer in question was executed at the .Build Registry (the Operating company that manages this TLD) level without any prior notice to Namecheap. As such, Namecheap was not involved in and is not responsible for the transfer.

All questions regarding the circumstances of the transfer — including any potential restoration — can only be addressed by the Registry. We recommend directing any further inquiries to them via https://about.build/faqs/

If you have any further questions, please do not hesitate to contact our Legal team directly at legal@namecheap.com.

Thank you for your understanding.

From: DotCoName <dotconame@gmail.com>
Date: Tue, Jul 15, 2025 at 2:09 PM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, Namecheap Legal & Abuse Team <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>
Cc: <compliance@icann.org>

Subject: Re: Ongoing Failure to Accept Responsibility for Loss of malaysia.build

Dear Namecheap Support Team,

Thank you for your continued responses, but I must state — in the clearest terms possible — that your repeated attempts to deny responsibility are completely unacceptable.

Let me reiterate the facts that cannot be ignored:

• The domain malaysia.build was kept under Namecheap’s management at the time of removal.
• It was valid, paid for through April 29, 2024, and auto-renewal was enabled — a clear sign of my intention to maintain continuous control.
• I did not request any transfer, nor was I informed in advance of any registry-level actions, which your team now conveniently claims to have occurred without notice.
• The domain was not idle — it was tied to a fully developed, monetizable real estate platform that had been in development for over 30 months. A working demo remains publicly available at: https://malaysia.sibu.design.

You continue to shift the blame onto the .BUILD Registry and close the matter from your end — but I did not deal with the registry directly. I entrusted Namecheap with the domain, and you were the registrar of record at the time of its unauthorized removal.

As such, Namecheap had a clear obligation to safeguard the domain while it was under your management and validly registered. Whether the registry initiated the removal or not, your failure to detect, prevent, or notify me of this action represents a serious breach of your duty of care.

The financial damage I’ve sustained is real, substantial, and directly tied to this breakdown. Development costs, lost revenue, business disruption, and reputational harm are all consequences of this incident — and I hold Namecheap responsible for ensuring accountability, not deflection.

Therefore, I am requesting again — directly and formally:

1. Does Namecheap accept financial liability for the losses incurred due to the removal of my domain while it was under your management and validly paid for?
2. What exact steps did Namecheap take, if any, to prevent or challenge this action at the registry level?
3. Why was I never notified of any pending restriction, reservation, or violation before the domain was removed — despite your systems having full visibility into the domain’s active, auto-renewed status?
4. And most importantly: I paid the renewal fee to Namecheap — what exactly was I paying for if you cannot ensure that the domain stays protected under your care?

Let me be absolutely clear: I do not accept that this matter is closed, and I will continue pursuing every available option to obtain a fair resolution — including formal escalation to ICANN, legal consultation, and full public documentation of your handling of this case at https://loss.co.

I await your formal reply — not more evasion — but a serious, specific, and accountable response to the above.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: DotCoName <dotconame@gmail.com>
Date: Tue, Jul 15, 2025 at 2:51 PM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, Namecheap Legal & Abuse Team <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>, <support@domain.build>, <abuse@domain.build>, <legal@enom.com>, <compliance@enom.com>, <abuse@enom.com>
Cc: <compliance@icann.org>

Subject: Final 24-Hour Notice Before Full Public Disclosure of malaysia.build Domain Dispute

Dear Namecheap, Enom, and .BUILD Registry Teams,

This is a final, good-faith attempt to resolve the ongoing and highly damaging issue regarding the unauthorized removal of my domain name, malaysia.build — which was active, paid for, set to auto-renew, and securely kept under Namecheap’s management at the time of its sudden disappearance.

As of today, I have received no concrete solution, no accountability, and no compensation from any party involved, despite providing extensive documentation of ownership, proof of payment, and the considerable investment poured into the development of the malaysia.build platform.

The facts are clear:

• The domain was valid until April 29, 2024, with auto-renewal enabled, demonstrating my clear intent to maintain control.
• I received no prior notice from Namecheap, Enom, or the .BUILD Registry regarding any restriction, violation, or reservation status.
• The domain was linked to a functioning, monetizable real estate platform, visible at https://malaysia.sibu.design.
• The resulting financial, operational, and reputational losses are extensive and still ongoing.

All three parties — Namecheap, Enom, and the .BUILD Registry — have repeatedly shifted responsibility to one another, creating a loop of deflection with no resolution. I have exercised every reasonable and professional means to settle this matter privately. However, my patience and goodwill are now exhausted.

If no formal resolution is offered within the next 24 hours, I will move forward with publishing the full record of this dispute, including:

• A complete public chronology of events
• Supporting evidence of domain ownership, renewal, and auto-renewal setup
• A breakdown of damages (development costs, lost revenue, business interruption, and reputational harm)
• Correspondence from all three parties involved

This documentation will be published not only at https://loss.co, but also on every major available public channel, including:

• Facebook, Twitter (X), Instagram, LinkedIn, YouTube, etc
• Domain-related forums and groups (e.g., NamePros, Reddit’s r/domain, WebHostingTalk)
• Complaint and consumer review platforms (e.g., Trustpilot, Better Business Bureau, SiteJabber)
• Blogs, independent web publications, and search-indexed complaint boards

This is not intended as a threat or to defame any party. It will be a factual, evidence-based account of how a paid-for, active domain was lost without warning — and how no involved party has taken responsibility. However, once published, this action is final and irreversible.

I remain open to resolving this dispute within the next 24 hours, professionally and privately. Please treat this with the urgency and seriousness it deserves.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: DotCoName <dotconame@gmail.com>
Date: Tue, Jul 15, 2025 at 3:49 PM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, Namecheap Legal & Abuse Team <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>, <support@domain.build>, <abuse@domain.build>, <legal@enom.com>, <compliance@enom.com>, <abuse@enom.com>
Cc: <compliance@icann.org>

Subject: Clarification Regarding Responsibility for malaysia.build Domain Removal

Dear Namecheap, Enom, and .BUILD Registry,

I am writing to issue a brief clarification concerning my prior emails regarding the removal of my domain, malaysia.build.

In earlier correspondence, I stated that all three parties — Namecheap, Enom, and the .BUILD Registry — have repeatedly shifted responsibility to one another. Upon review, I wish to correct and clarify that:

• Namecheap has, in multiple responses, attributed the incident to its upstream provider (Enom) and the .BUILD Registry;
• Enom has provided one reply, indicating that the removal action was performed by the .BUILD Registry directly;
• The .BUILD Registry, despite being copied in every email, has not responded at all.

I maintain that the situation remains unresolved, and the pattern of deflection — intentional or not — has left me without answers or restitution. However, I believe it is important to be factually accurate in all statements made in this matter.

Thank you for noting this correction. I continue to await a substantive response from the namecheap, enom, .BUILD Registry and reiterate my request for accountability and resolution from all parties involved.

Sincerely,
Wong Tai Chiew
Email: dotconame@gmail.com
Phone: +6019 8280131

From: Namecheap Domains Support Team <domainsupport@namecheap.com>
Date: Tue, Jul 15, 2025 at 3:57 PM
To: <dotconame@gmail.com>

Hello,

Thank you for your reply.

We would like to apologize for all the inconveniences and difficulties you have experienced.

We do understand your concerns related to this issue. However, it should be evaluated by our Legal team directly via legal@namecheap.com from your end in order for you to receive answers to your questions/concerns.

Please send an email to them via legal@namecheap.com directly.

Thank you for your cooperation!

From: DotCoName <dotconame@gmail.com>
Date: Wed, Jul 16, 2025 at 1:51 AM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, Namecheap Legal & Abuse Team <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>
Cc: <support@domain.build>, <abuse@domain.build>, <legal@enom.com>, <compliance@enom.com>, <abuse@enom.com>

Subject: URGENT: REFUTING NAMECHEAP’S DENIAL OF RESPONSIBILITY & DEMAND FOR IMMEDIATE RESOLUTION – malaysia.build

Dear Namecheap Legal Team (legal@namecheap.com) and Support Management,

I acknowledge receipt of your latest communication, including the notification that your Legal team has concluded its investigation and that this email thread will be closed. I am writing to you directly, as instructed, to unequivocally refute your findings and reiterate my demands for immediate resolution and compensation.

As a long-standing Namecheap customer, I have always valued the trust and reliability in our registrar–registrant relationship. It has been my intention to maintain a long-term, positive collaboration. However, the current unresolved issue of the unauthorized loss of my domain, malaysia.build, has eroded this confidence entirely.

Let me be absolutely clear: Namecheap, as the ICANN-accredited registrar of record for malaysia.build, bears direct and non-delegable responsibility for the unauthorized loss of my domain.

It has now been over one full month since my initial complaint on June 11, 2025. Despite submitting multiple follow-ups, detailed supporting evidence, and filing a formal complaint through ICANN.org, there has been no clear explanation or resolution from Namecheap or the .BUILD Registry.

Your repeated attempts to shift blame to an “upstream provider” or the .BUILD Registry, claiming the issue “originated at the registry level” and was “beyond our direct control,” fundamentally contradict your obligations as my service provider. My contract is with Namecheap. ICANN’s Registrar Accreditation Agreement (RAA) and Inter-Registrar Transfer Policy (IRTP) establish that registrars are ultimately accountable for the security and proper management of domains under their sponsorship, regardless of any third-party relationships.

The most damning fact, confirmed by your own logs, is that the domain malaysia.build was removed from my account, yet “no EPP code was requested.” This is not a matter for the Registry to clarify; this is a catastrophic security failure within Namecheap’s own system or processes. An authorized transfer requires an EPP code. If the domain left your control without one, it represents a profound breach of security protocols and a direct violation of ICANN’s IRTP. Your inability to explain how this occurred or who initiated such an action from your internal systems is a severe dereliction of your duty.

This domain was:

• Fully paid and valid through April 29, 2024.
• Set to auto-renew, with notifications confirmed.
• Linked to a functioning, monetizable real estate platform, visible at https://malaysia.sibu.design, which includes a live demo, PWA, Android/iOS apps, and a functioning payment gateway.

I received no prior notice from Namecheap, Enom, or the .BUILD Registry regarding any restriction, violation, or reservation status. All supporting documentation — including receipts, WHOIS history, screenshots, and app demos — has been shared. Furthermore, I have recorded a YouTube video (currently unlisted) demonstrating my ownership and development dating back to 2014, which will be made public if this matter is not resolved.

The resulting financial, operational, and reputational losses are extensive and still ongoing. These are not theoretical losses; they are tangible harms that grow with every day this issue remains unresolved.

Your continued refusal to provide direct answers, a clear timeline for domain restoration, or a concrete plan for compensation, is no longer merely frustrating – it is actively contributing to my losses. Your latest response offers nothing but further delay and a reiteration of the same unhelpful explanations.

Therefore, I demand immediate and decisive action:

1. Namecheap must accept full and direct responsibilityfor the unauthorized loss of malaysia.build from my account while it was valid and under your management. As per your own Domain Registration Agreement (https://www.namecheap.com/legal/domains/registration-agreement/):

o    Under “Cancellations, Transfers, and Changes,” it states: “We will cancel, transfer or otherwise make changes to domain name registrations under the following circumstances: … our receipt of written or appropriate electronic instructions from you or your authorized agent to take such action;” No such instructions were provided by me, and no EPP code was used (a fact you have confirmed), rendering this removal a direct breach of your stated terms.

o    Furthermore, your agreement states: “to obtain the EPP “AuthCode” which is required to transfer domain services…” and “Only the registrant and the administrative contacts listed in the WHOIS information may approve or deny a transfer request.” Your failure to adhere to these explicit requirements, coupled with the absence of an EPP code, demonstrates a fundamental breakdown in your security and authorization processes.

o    While your “Registry / ICANN Rights” clause attempts to grant broad discretion for domain actions “without liability,” this specific protection is explicitly limited to “the first five (5) days after registration has taken place.” My domain was owned for a decade, clearly falling outside this limited liability period. This incident is a clear failure of your internal security and adherence to ICANN policies, not merely a third-party error.

o    Under “Term,” your agreement states: “The term of this Agreement shall continue in full force and effect as long as you have any domain name registered through Namecheap…” My domain was valid and paid for, meaning your obligations were active.

o    Under “Namecheap Rights” (Section 4), your agreement outlines conditions for termination “for cause” (e.g., “registration of prohibited domain name(s), abuse of the Services, payment irregularities, material allegations of illegal conduct”). My domain was not subject to any of these conditions, further demonstrating the lack of justification for its removal. Similarly, Section 6 on “prohibited activities” was not violated by me.

o    Unjustified Retroactive Application of Policy: If the domain was indeed “reserved by the Registry” due to a policy, it is Namecheap’s responsibility to explain why a policy primarily for initial domain allocations was retroactively applied to this domain name that had been under your management for many years without any prior notice to me or, by your own admission, to Namecheap. This lack of notification is a critical procedural failure.

o    Furthermore, your own Uniform Domain Name Dispute Resolution Policy (UDRP) (http://www.icann.org/dndr/udrp/policy.htm) explicitly states its “Purpose” is for “a dispute between you and any party other than us (the registrar) over the registration and use of an Internet domain name registered by you.” This confirms that the UDRP is not intended to shield Namecheap from direct claims arising from your own operational failures and breaches of contract/policy, such as the unauthorized removal of my domain. Your actions fall outside the legitimate circumstances for domain changes as defined in the “Cancellations, Transfers, and Changes” section of the UDRP, which only permit changes based on explicit registrant instructions, court orders, or UDRP panel decisions against the registrant—none of which apply here.

2. Namecheap must provide full compensationfor all documented losses incurred, including over 30 months of platform development and custom integrations, business disruption and delay of public launch, lost revenue and missed commercial opportunities, reputational damage with partners and early users, marketing investments made around the malaysia.build domain, and the ongoing cost of email correspondence, documentation, and dispute resolution. This compensation is warranted due to your confirmed security failure and your non-compliance with ICANN’s Inter-Registrar Transfer Policy (https://www.icann.org/resources/pages/name-holder-faqs-2017-10-10-en), which mandates EPP codes for secure transfers. Your inability to explain the domain’s departure without this critical security measure is a fundamental breach of your obligations as an ICANN-accredited registrar.
3. Namecheap must outline an immediate plan for the restoration of the domainor provide an equivalent remedy without further delay.

Be advised that due to Namecheap’s persistent inaction and evasion, I have already proceeded with formal UDRP proceedings and have fully activated public documentation of this egregious failure at https://loss.co. The website will present the full timeline, financial losses, evidence, display the entire email trail with Namecheap, make all materials public and searchable via Google and other search engines, and include my YouTube video and platform screenshots. Further delays will only lead to broader public disclosure and intensified legal action, as your continued failure to meet your obligations under the ICANN Registrar Accreditation Agreement (RAA) and Inter-Registrar Transfer Policy will be fully highlighted. The RAA stipulates that registrars remain fully responsible for services, even if subcontracted, meaning your reliance on “upstream providers” does not absolve you of your direct accountability to me.

I expect a substantive response addressing these demands within 24 hours.

Sincerely,

WONG TAI CHIEW

Email: dotconame@gmail.com

Phone: +6019 8280131

From: DotCoName <dotconame@gmail.com>
Date: Wed, Jul 16, 2025 at 9:40 PM
To: <legal@namecheap.com>
Cc: Namecheap Domains Support Team <domainsupport@namecheap.com>, <domains@namecheap.com>, <pr@namecheap.com>, Namecheap Risk Management Team <security@namecheap.com>, <support@namecheap.com>, Namecheap Legal & Abuse Team <abuse@namecheap.com>, <legalandabuse@namecheap.com>, <abuseescalation@namecheap.com>, <ceo@namecheap.com>

Subject: URGENT: REFUTING NAMECHEAP’S DENIAL OF RESPONSIBILITY & DEMAND FOR IMMEDIATE RESOLUTION – malaysia.build

Dear Namecheap Legal Team (legal@namecheap.com) and Support Management,

I acknowledge receipt of your recent communication, including the notification that your Legal team has concluded its investigation and that this email thread will be closed. I am writing to you directly, as instructed, to unequivocally refute your findings and reiterate my demands for immediate resolution and compensation.

As a long-standing Namecheap customer, I have always valued the trust and reliability in our registrar–registrant relationship. It has been my intention to maintain a long-term, positive collaboration. However, the current unresolved issue of the unauthorized loss of my domain, malaysia.build, has eroded this confidence entirely.

Let me be absolutely clear: NAMECHEAP, AS THE ICANN-ACCREDITED REGISTRAR OF RECORD FOR MALAYSIA.BUILD, BEARS DIRECT AND NON-DELEGABLE RESPONSIBILITY FOR THE UNAUTHORIZED LOSS OF MY DOMAIN.

It has now been over one full month (36 days) since my initial complaint on June 11, 2025. Despite submitting multiple follow-ups, detailed supporting evidence, and filing a formal complaint through ICANN.org, there has been no clear explanation or resolution from Namecheap or the .BUILD Registry.

Your repeated attempts to shift blame to an “upstream provider” or the .BUILD Registry, claiming the issue “originated at the registry level” and was “beyond our direct control,” fundamentally contradict your obligations as my service provider. My contract is with Namecheap. ICANN’s Registrar Accreditation Agreement (RAA) and Inter-Registrar Transfer Policy (IRTP) establish that registrars are ultimately accountable for the security and proper management of domains under their sponsorship, regardless of any third-party relationships.

The most damning fact, confirmed by your own logs, is that the domain malaysia.build was removed from my account, yet “no EPP code was requested.” This is not a matter for the Registry to clarify; this is a catastrophic security failure within Namecheap’s own system or processes. An authorized transfer requires an EPP code. If the domain left your control without one, it represents a profound breach of security protocols and a direct violation of ICANN’s IRTP. Your inability to explain how this occurred or who initiated such an action from your internal systems is a severe dereliction of your duty.

This domain was:

• Fully paid and valid through April 29, 2024.
• Set to auto-renew, with notifications confirmed.
• Linked to a functioning, monetizable real estate platform, visible at https://malaysia.sibu.design, which includes a live demo, PWA, Android/iOS apps, and a functioning payment gateway.

I received no prior notice from Namecheap, Enom, or the .BUILD Registry regarding any restriction, violation, or reservation status. All supporting documentation — including receipts, WHOIS history, screenshots, and app demos — has been shared. Furthermore, I have recorded a YouTube video (currently unlisted) demonstrating my ownership and development dating back to 2014, which will be made public if this matter is not resolved.

The resulting financial, operational, and reputational losses are extensive and still ongoing. These are not theoretical losses; they are tangible harms that grow with every day this issue remains unresolved.

Your continued refusal to provide direct answers, a clear timeline for domain restoration, or a concrete plan for compensation, is no longer merely frustrating – it is actively contributing to my losses. Your latest response offers nothing but further delay and a reiteration of the same unhelpful explanations.

Frankly, your position that Namecheap is “not involved in and is not responsible” is utterly perplexing, especially when viewed against the very terms you operate under. Your replies are self-contradictory and self-defeating. How, precisely, can Namecheap claim to be uninvolved when I paid you directly for the management of this domain, it was still valid, auto-renewal was enabled, and it vanished from your system without my authorization or the mandatory EPP code? Which specific part of your terms gives Namecheap the audacity to escape its fundamental responsibility as the registrar to safeguard my domain name?

Allow me to provide a simple analogy: Imagine renting a safety deposit box at a bank, diligently paying your annual rental fees, and then one day discovering that all your valuable possessions are gone, the box is “on hold” for “no reason,” and the bank claims it had “no involvement” because the vault operator (their upstream provider) or the central bank (the registry) took action without notifying them. In such a scenario, to whom should you file the complaint? The bank, the vault operator, or the central bank? And then the bank then tells you to deal directly with the central bank, stating it has nothing to do with them. Who should be the party held responsible? Would any reasonable person accept such an explanation? Would the bank not be held accountable for the security of the assets entrusted to its care? Your current stance is precisely this level of absurdity.

Perhaps Namecheap’s Legal team could benefit from an objective, unbiased assessment of this situation. I challenge you to present the entire scenario – including all my documented evidence, your conflicting statements, your own terms and conditions, and your current denial of responsibility – to any reputable, publicly available AI system or large language model. Ask it: “Based on these facts and Namecheap’s own terms, is Namecheap responsible for the loss of this domain and the resulting damages?” I am confident the response will unequivocally highlight your accountability.

Therefore, I demand immediate and decisive action:

1. Namecheap must accept full and direct responsibilityfor the unauthorized loss of malaysia.build from my account while it was valid and under your management. As per your own Domain Registration Agreement (https://www.namecheap.com/legal/domains/registration-agreement/):

o    Under “Cancellations, Transfers, and Changes,” it states: “We will cancel, transfer or otherwise make changes to domain name registrations under the following circumstances: … our receipt of written or appropriate electronic instructions from you or your authorized agent to take such action;” No such instructions were provided by me, and no EPP code was used (a fact you have confirmed), rendering this removal a direct breach of your stated terms.

o    Furthermore, your agreement states: “to obtain the EPP “AuthCode” which is required to transfer domain services…” and “Only the registrant and the administrative contacts listed in the WHOIS information may approve or deny a transfer request.” Your failure to adhere to these explicit requirements, coupled with the absence of an EPP code, demonstrates a fundamental breakdown in your security and authorization processes.

o    While your “Registry / ICANN Rights” clause attempts to grant broad discretion for domain actions “without liability,” this specific protection is explicitly limited to “the first five (5) days after registration has taken place.” My domain was owned for a decade, clearly falling outside this limited liability period. This incident is a clear failure of your internal security and adherence to ICANN policies, not merely a third-party error.

o    Under “Term,” your agreement states: “The term of this Agreement shall continue in full force and effect as long as you have any domain name registered through Namecheap…” My domain was valid and paid for, meaning your obligations were active.

o    Under “Namecheap Rights” (Section 4), your agreement outlines conditions for termination “for cause” (e.g., “registration of prohibited domain name(s), abuse of the Services, payment irregularities, material allegations of illegal conduct”). My domain was not subject to any of these conditions, further demonstrating the lack of justification for its removal. Similarly, Section 6 on “prohibited activities” was not violated by me.

o    Unjustified Retroactive Application of Policy: If the domain was indeed “reserved by the Registry” due to a policy, it is Namecheap’s responsibility to explain why a policy primarily for initial domain allocations was retroactively applied to this domain name that had been under your management for many years without any prior notice to me or, by your own admission, to Namecheap. This lack of notification is a critical procedural failure.

o    Furthermore, your own Uniform Domain Name Dispute Resolution Policy (UDRP) (http://www.icann.org/dndr/udrp/policy.htm) explicitly states its “Purpose” is for “a dispute between you and any party other than us (the registrar) over the registration and use of an Internet domain name registered by you.” This confirms that the UDRP is not intended to shield Namecheap from direct claims arising from your own operational failures and breaches of contract/policy, such as the unauthorized removal of my domain. Your actions fall outside the legitimate circumstances for domain changes as defined in the “Cancellations, Transfers, and Changes” section of the UDRP, which only permit changes based on explicit registrant instructions, court orders, or UDRP panel decisions against the registrant—none of which apply here.

2. Namecheap must provide full compensationfor all documented losses incurred, including over 30 months of platform development and custom integrations, business disruption and delay of public launch, lost revenue and missed commercial opportunities, reputational damage with partners and early users, marketing investments made around the malaysia.build domain, and the ongoing cost of email correspondence, documentation, and dispute resolution. This compensation is warranted due to your confirmed security failure and your non-compliance with ICANN’s Inter-Registrar Transfer Policy (https://www.icann.org/resources/pages/name-holder-faqs-2017-10-10-en), which mandates EPP codes for secure transfers. Your inability to explain the domain’s departure without this critical security measure is a fundamental breach of your obligations as an ICANN-accredited registrar.
3. Namecheap must outline an immediate plan for the restoration of the domainor provide an equivalent remedy without further delay.

Be advised that due to Namecheap’s persistent inaction and evasion, I have already proceeded with formal UDRP proceedings and have fully activated public documentation of this egregious failure at https://loss.co. The website currently displays a simple notice, but it will present the full timeline, financial losses, evidence, display the entire email trail with Namecheap, make all materials public and searchable via Google and other search engines, and include my YouTube video and platform screenshots. Further delays will only lead to broader public disclosure and intensified legal action, as your continued failure to meet your obligations under the ICANN Registrar Accreditation Agreement (RAA) and Inter-Registrar Transfer Policy will be fully highlighted. The RAA stipulates that registrars remain fully responsible for services, even if subcontracted, meaning your reliance on “upstream providers” does not absolve you of your direct accountability to me.

I expect a substantive response addressing these demands within 24 hours.

Sincerely,

WONG TAI CHIEW

Email: dotconame@gmail.com

Phone: +6019 8280131

Subject: URGENT: Formal Demand for Explanation – Loss of malaysia.build

From: DotCoName <dotconame@gmail.com>
Date: Fri, Sep 26, 2025 at 6:54 PM
To: Namecheap Domains Support Team <domainsupport@namecheap.com>, <legal@namecheap.com>, <support@namecheap.com>
Cc: <compliance@icann.org>, <ombudsman@icann.org>, <globalsupport@icann.org>

Dear Namecheap Legal and Compliance Team,

I am writing under extreme dissatisfaction and urgency regarding the unexplained removal of my domain, malaysia.build, which was under Namecheap’s safeguard at the time of its loss.

Despite my payment and active auto-renewal — which extended the domain’s validity until April 29, 2024 — the domain was taken away with nearly five months left before expiry. Namecheap profited directly from my payment, yet failed in its fundamental responsibility: safeguarding the domain. From my perspective, this situation appears indistinguishable from a scam.

To be absolutely clear:

1. Nearly a Decade of Investment: I had continuously developed and invested in this domain for years under registrar safeguard. Losing it without due process is unacceptable.
2. Active and Paid: Auto-renewal was enabled, and the domain was fully paid through April 29, 2024. That alone demonstrates my clear intent for uninterrupted ownership.
3. No EPP Code: Namecheap confirmed in writing (July 14, 2025, 3:20 PM): “No, according to our logs, the EPP code was not requested.” Under ICANN’s Transfer Policy §2.1.1, an EPP code is typically required for a transfer. From my perspective, this step was never followed.
4. No Prior Notice: I first learned of the domain loss only after it had occurred. To my knowledge, neither Namecheap, Enom, nor the .BUILD Registry provided any advance notification.
5. Premature Complaint Closure: My prior complaint was closed abruptly, without clear explanation or resolution. This premature closure, from my perspective, reflects a serious failure in accountability.

To compound this, Namecheap repeatedly attributed the loss to Enom and the .BUILD Registry, then referred me to your legal department — who denied any involvement and subsequently ceased responding. This pattern of behavior, in my view, is unethical, immoral, and indefensible for a registrar entrusted with customer assets.

Therefore, I demand direct answers to the following:

1. 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.
2. What proactive steps did Namecheap take to notify me as registrant before the domain was removed? Please provide records of such attempts.
3. Why was my complaint closed prematurely without explanation? Who authorized this closure, and under what grounds?
4. Given that the domain was paid for, active, and under Namecheap’s safeguard, what does Namecheap accept as its responsibility in this failure?
5. 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.

All relevant email trails have already been published at https://loss.co, with this correspondence and your reply to be added for full public transparency.

Silence or failure to provide a substantive reply within 48 hours will be treated as a deliberate refusal of accountability. From my perspective, this will only reinforce the interpretation that Namecheap’s conduct is indistinguishable from a scam, and I will continue escalating this matter to ICANN, industry forums, and public platforms.

I expect your urgent response.

Sincerely,

WONG TAI CHIEW

Registrant of malaysia.build (former)

Email: dotconame@gmail.com

Tel: +60198280131

On Fri, Sep 26, 2025 at 5:13 PM DotCoName <dotconame@gmail.com> wrote:

Dear .BUILD Registry Management,

I am writing under extreme frustration regarding the removal of my domain name, malaysia.build, which was executed by your registry on or around December 1, 2023.

This email follows numerous previous attempts to contact you via email and your online form, all of which have been met with complete silence. To date, I have received no direct explanation from your organization for this action.

The only information I have originates from Enom, who stated in a July 14, 2025, communication that your registry acted based on a request from ICANN due to an alleged violation of “Spec 5” of your Registry Agreement.

This vague explanation is unacceptable. The removal of a domain name is a serious action that requires full transparency and due process. Therefore, I require your immediate response to the following questions:

1. ICANN Directive: Please provide a copy of the specific written directive you received from ICANN that ordered the removal of the domain malaysia.build.
2. Specific Violation: Please detail the exact nature of the violation. How did the domain malaysia.build specifically contravene Section 5 of the Registry Agreement? Your response must include the specific clauses and the factual basis for your determination.
3. Registrant Due Process: What policy or procedure did you follow to notify me, the registrant, of the alleged violation and provide an opportunity to respond before taking the punitive action of removal? Please provide copies of all notification attempts sent to the registrant contact information on record.
4. Registrar Obligations: What formal instructions were issued to Enom as registrar of record at the time? Did you require them to notify me, or did you bypass the registrar entirely?
5. Appeal Process: What is the formal appeals process for this decision? Please provide the specific steps, contact information, and deadlines for submitting an appeal directly to the .BUILD registry.

Given that this action was taken over 18 months ago and my previous communications have been ignored, I must insist on a substantive response to these questions within 48 hours.

Continued silence will leave me no choice but to escalate this as a formal complaint with ICANN’s Contractual Compliance department, citing a failure by the registry to adhere to principles of transparency and fair process.

Finally, please be aware that, in the interest of transparency and accountability, I reserve the right to publish this correspondence, together with all related email trails, at https://loss.co and other relevant forums and discussion groups to ensure this matter is fully documented.

I trust that you will finally provide the clarity that I, as the rightful registrant, am owed.

Sincerely,

WONG TAI CHIEW

Registrant of malaysia.build (former)

Email: dotconame@gmail.com

Tel: +6019-828-0131

On Fri, Sep 26, 2025 at 4:47 PM DotCoName <dotconame@gmail.com> wrote:

from: DotCoName <dotconame@gmail.com> to: legal@enom.com, compliance@enom.com, abuse@enom.com, support@enom.com

date: Sep 4, 2026, 10:32 PM

Subject: Re: Urgent Clarification Required: malaysia.build Domain Removal

DISCLAIMER — FOR TRANSPARENCY:

This email is being sent to multiple parties, including Namecheap, ICANN, NTIA, FTC, MCMC, the White House, the United Nations, the U.S. Chamber of Commerce, Tech in Asia, and other relevant stakeholders. All recipients are copied for transparency and to ensure that any response — or lack thereof — is publicly documented. This correspondence is not intended to harass, defame, or make any false claims. It is a good-faith request for clarification based on documented evidence.

SUMMARY OF PARTIES CC’D

 

Dear Enom Legal Team,

I am writing to seek formal clarification regarding the domain malaysia.build and the chain of communication between Enom, Namecheap, and the .BUILD Registry.

Background:

On December 1, 2023, the .BUILD Registry sent an email to Enom (as the upstream provider) stating:

“We have been requested by ICANN to remove / Block the domain malaysia.build from registration due to it violating Spec 5 of our Registry agreement.”

This email was provided to me by Enom on July 14, 2025, confirming that Enom received the notice from the Registry.

Namecheap’s Position:

In a chat transcript dated 4 September 2026, Namecheap agent Navanish B. stated:

“Namecheap was not notified by Enom. The action was carried out at the Registry level without notice to Namecheap.”

Reference:

See full chat transcript: https://drive.google.com/file/d/1x4g-pIML9wdxIs-0OMccad9MlhLDWXkH/view

https://www.namepros.com/threads/is-your-domain-truly-secure-my-experience-raises-serious-questions.1362731/page-18#post-9588107

https://www.namepros.com/threads/is-your-domain-truly-secure-my-experience-raises-serious-questions.1362731/page-23#post-9624916

https://www.namepros.com/threads/is-your-domain-truly-secure-my-experience-raises-serious-questions.1362731/page-30#post-9642288

https://www.namepros.com/threads/is-your-domain-truly-secure-my-experience-raises-serious-questions.1362731/page-33#post-9644644

https://www.namepros.com/threads/is-your-domain-truly-secure-my-experience-raises-serious-questions.1362731/page-33#post-9645144

https://www.namepros.com/threads/is-your-domain-truly-secure-my-experience-raises-serious-questions.1362731/page-20#post-9604823

https://www.namepros.com/threads/is-your-domain-truly-secure-my-experience-raises-serious-questions.1362731/page-20#post-9606213

My Request:

1. Was Namecheap ever notified by Enom regarding the .BUILD Registry’s decision to block malaysia.build on December 1, 2023?

   • If YES, please provide the date, method, and evidence of notification.

   • If NO, please confirm that Enom did not forward the Registry’s notice to Namecheap.

2. Why was I — the registrant — never notified by any party of the pending deletion, despite having auto-renewal enabled and valid payment on file?

---

Deadline for Response:

Please respond by Monday, 7 September 2026, at 11:59 PM Arizona Time (MST) .

If no response is received by this deadline, I will draw the following conclusions:

1. Namecheap was telling the truth — that Enom never notified Namecheap of the Registry’s decision.

2. Enom bears full responsibility for failing to inform the registrant of the impending deletion, in violation of ICANN’s Registrar Accreditation Agreement (RAA) 2013.

---

ICANN RAA 2013 Regulation References:

Enom, as an ICANN-accredited registrar, is bound by the following obligations under the 2013 Registrar Accreditation Agreement:

 

---

Enom’s Specific Admission:

In your email to me dated July 14, 2025, Enom stated:

“We have no record of the transfer, or distribution of an Auth Code for transfer, as the action was performed solely at the Registry level.”

This confirms that:

• No EPP code was generated or distributed.

• No transfer authorization was obtained from the registrant.

Full ICANN RAA 2013 Text: https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en

Relevant Sections:

• Section 3.4 (Retention of Data)

• Section 3.18 (Abuse Contact)

• Section 3.20 (Security Breaches)

---

Parties CC’d:

I have copied Namecheap, ICANN, NTIA, FTC, MCMC, the White House, the United Nations, the U.S. Chamber of Commerce, Tech in Asia, and other relevant parties on this email for transparency.

If Enom fails to respond by the deadline, this email chain — and Enom’s silence — will be submitted as evidence to ICANN, NTIA, FTC, and other regulatory bodies.

Why This Matters:

Namecheap has claimed for 449+ days that it was “waiting for the Registry” and had “no information.” On 4 September 2026, Namecheap admitted it was never notified by Enom. This raises serious questions about:

• Enom’s obligation to notify its downstream registrar (Namecheap).

• Namecheap’s obligation to notify its customer (me).

• The integrity of the ICANN-mandated communication chain.

I would be grateful for your timely response.

Yours sincerely,

Wong Tai Chiew
Email: dotconame@gmail.com
Namecheap Ticket ID: NC-UWS-6390
ICANN Compliance Case: #01448650

DISCLAIMER — PROTECTION OF RIGHTS:

On Wed, Sep 9, 2026 at 12:02 AM DotCoName <dotconame@gmail.com> wrote:

Subject: URGENT: Enom’s Violation of ICANN RAA 2013 — Request for Enforcement — ICANN Compliance Case #01448650 — 424+ Days of Zero Resolution

See https://loss.co/icann-contractual-compliance-complete-email-trail/#icann-thank-you-for-your-non-response-but-what-exactly-are-registrants-paying-you-for