We got burned when our prized domain, purchased through Go Daddy for a whopping $1,700, got jacked from our personal account. We're still in the dark about how the perpetrators pulled off this domain hijacking, but we've got a bead on the culprits. The kicker is that the domain now redirects to the thieves' site.

After going back and forth with Go Daddy's support team, they dropped the bombshell that the Asian Arbitration Domain Court (ADNDRC) greenlit the transfer. In other words, Go Daddy effectively dispossessed us of our digital asset, which we acquired through their own brokerage. The support team has since gone radio silent, refusing to take our calls, leaving us high and dry without our domain or the funds we shelled out for it.
The real kicker is that no one's taking ownership of this fiasco. Go Daddy had two-factor auth in place, and there were no suspicious third-party logins, so it's clear this was an outside job.

Has anyone else fallen victim to this kind of domain fraud?

How can we possibly resolve this mess?

Any advice or tips would be greatly appreciated.

It's unacceptable that Go Daddy's support team has dropped the ball, especially given the presence of two-factor auth. This incident highlights the importance of domain security and the need for registrars to take more responsibility in preventing domain fraud.

I'd suggest reaching out to the Internet Corporation for Assigned Names and Numbers (ICANN) or the Federal Trade Commission (FTC) to report this incident and seek guidance. Additionally, consider diversifying your domain portfolio across multiple registrars to minimize the risk of a single point of failure.

Apparently, the domain name wasn't hijacked after all. The registrar merely complied with a court order, executing the ruling as mandated. In this scenario, the best course of action would be to solicit a detailed breakdown of the events leading up to the transfer, and consider retaining counsel well-versed in the jurisdiction's legal framework - specifically, an attorney specializing in intellectual property law or domain name disputes.
This expert can help navigate the complexities of the situation, potentially appealing the decision to a higher authority or seeking redress through the courts. It's essential to understand the intricacies of the Uniform Domain-Name Dispute-Resolution Policy (UDRP) and the role of the Internet Corporation for Assigned Names and Numbers (ICANN) in resolving domain name conflicts.

When navigating a domain dispute, it's essential to scrutinize the timeline of events, including the initiation of the case, domain registration, and transfer dates. Investigate whether a domain lock was in place, and if the registrant received notifications. This will help determine if GoDaddy (GD) breached their Registrar Accreditation Agreement (RAA) or Uniform Domain-Name Dispute-Resolution Policy (UDRP) obligations.

If you acquired a domain via UDRP and neglected to respond to notifications (or deliberately opted out of the process), refrain from defamatory remarks against GD and take responsibility for your inaction. However, if GD's support team dropped the ball (although unlikely, given their robust infrastructure) and ignored your concerns, revise your complaint to accurately reflect the issues and consider escalating the matter through ICANN's Complaint Resolution Process (CRP) for RAA-related UDRP violations.

Additionally, if you paid for the domain via credit card, you may want to explore the possibility of a chargeback through the card issuer, as per their policies. It's crucial to familiarize yourself with ICANN's Transfer Policy, RAA, and UDRP to effectively navigate domain disputes and ensure a fair resolution. As a domain owner, it's vital to stay vigilant and proactive in protecting your online assets.