question Registered GPS.QA, Had Full Control, Then Taken Back by Registrar – Need Advice & Opinions

[Maronox]

Hi everyone,


I’m dealing with a frustrating and frankly shocking situation involving the domain GPS.QA, and I’d appreciate some feedback, advice, or insights from anyone who has experienced something similar.

---

The Situation:​

• I registered the domain GPS.QA through AEserver (ICANN-accredited registrar) after WHOIS showed it had expired and was publicly available.
• I received full confirmation, and the domain was under my control — I could update DNS, and even listed it on Atom.com.
• Shortly after listing, I received a serious $5,999 offer, with a net payout of $5,099.15 — I was already in advanced negotiations with the buyer.

---

What Went Wrong:​

• A few days later, AEserver contacted me claiming the domain had been “accidentally deleted” during their registrar partner’s technical migration, and that it was still “technically owned” by a previous registrant.
• They told me that as a result, the domain was returned to that prior registrant, and they simply refunded my purchase.
• Despite this, the domain still resolves to my Atom.com landing page, indicating that the DNS settings were active from my original registration.

---

My Concerns:​

• I acted in good faith — followed the correct process, relied on accurate WHOIS data, and made business decisions based on what I believed was a valid domain registration.
• This isn’t just about the domain — it’s about the financial loss of a deal already in motion, and the principle of removing a domain from a paying customer based on internal errors.
• I now face a potential $5,000+ loss, and AEserver’s response has been a generic apology and refund.

---

Looking for:​

• Has anyone experienced something similar — where a registrar allowed you to register a domain, gave you control, and then took it back?
• Is there any industry-recognized process or precedent when domains are reclaimed due to internal errors?
• Would you suggest pursuing this further — possibly via public exposure, a formal complaint to Qatar Domains Registry, or legal advice?

---

This is the first time I’ve ever had a domain removed from my account after confirmed registration, and it concerns me deeply as both a buyer and investor.


Any guidance, similar stories, or suggestions would be greatly appreciated.


Thanks in advance!
Maronox

 

[jberryhill]

I registered the domain GPS.QA through AEserver (ICANN-accredited registrar) after WHOIS showed it had expired and was publicly available.

Whether the registrar is accredited by ICANN in relation to gTLDs is not relevant to the registrar's offering of ccTLD registrations. Since .qa is a ccTLD, then domains can be registered through whomever the registry allows, whether they are ICANN accredited or not.

I am kind of curious about "WHOIS showed it had expired" since, as far as I can tell, expiration dates are not published in WHOIS for .qa domain names. I've taken a look at the DT WHOIS history on this domain, for example, and for a good stretch of recent history, it rotates through various sales platforms and brokerages, but since there is no creation or expiration date in the data, it would be interesting to know specifically when all this happened.

It's also kind of interesting that the last time it was registered through AEServer was back in late 2024:

In December, it changes to Q Host as the registrar:

...and from there it bounces back and forth from Efty to Atom a couple of times, but stays at Q Host:

So, it is difficult to match up your facts with the WHOIS history of the domain, unless you are talking about something that happened quite some time ago.

Alternatively, if this did happen recently, and happened through AEServer, then the issue would seem to have arisen in the interface between AEServer and the .qa registry, since, as can be seen from the WHOIS history (and several captures between 12/24 and 7/25 which I didn't bother to cap and post), the name hasn't been registered through AEServer recently - at least not long enough for a WHOIS capture to have occurred.

That said, this general type of situation - "I registered a domain name and it got taken back because the registrar/registry claimed some kind of error" - is relatively common. All sorts of errors can happen when there is a problem with the registrar synching up with the registry. Offhand, I don't know who runs the .qa backend infrastructure or if they have their own platform. But, long story short, there's a laundry list of common issues that can occur and which lead to a registrar's interface incorrectly indicating a domain name to be available when it is not.

This isn’t just about the domain — it’s about the financial loss of a deal already in motion, and the principle of removing a domain from a paying customer based on internal errors.

The "financial loss" is the simplest one to address. From what you wrote, it seems you had an offer of $5k but had not accepted it and had not completed a deal. There isn't a registrar on the planet whose terms do not exclude liability for what are called "consequential" damages, and the general terms of AEServer, which I did take a quick look at, are no exception in that regard. The other thing one can safely conclude is that all legal disputes, when you are dealing with a service provider in the UAE, are to be brought in the UAE. Now, I haven't litigated a case in the UAE, but I would imagine that a $5,000 claim is nowhere near worth it.

As far as the "principle of removing a domain from a paying customer goes", I'm curious to know what you think should happen to the other paying customer here? Assuming for a moment that the "error" here has something to do with the domain name incorrectly having been indicated to be available, when in fact it shouldn't have been, then would you be comfortable with the principle of having a domain name you've owned for years suddenly registered to someone else because of an error?

What is it you believe should happen when some kind of error at the registry or registrar momentarily and incorrectly indicates a registered name to be available, registers that domain name to someone else, and the original registrant shows up to complain?

Another common variant that happened a lot when the new gTLDs were rolled out was the registrar platform not being set up to correctly distinguish registry premium domains from ordinary price domains. There were a ton of threads at that time by people who actually went out and found registrars where these errors were happening, intentionally registering domains at prices they knew were incorrect, and then whining about having their domains taken away.

But if there is one thing to which you respond in any of this, I'm most interested by how you had determined the domain name was previously registered and then expired, at the time you checked. Can you go through that in a little more detail?

 

[jberryhill]

 

[djmc50]

26 and 25 years ago (years: 1999 and 2000)
NetworkSolutions and Tucows stole several premium ONE WORD/TWO WORD domains from my account.
They claimed the domains were "accidentally" deleted...