Skip to content
Law & policyRegistrarsTLD policy

.Qa domains get new restrictions: change your nameservers now

Qatar is closing second-level .qa registration to anyone without a local commercial, trademark or residency footing, and barring resale of the names. Existing holders face an eligibility check on their next nameserver change, and the window to act is measured in hours.

The .qa registry is introducing eligibility rules for second-level .qa domains, effective midnight on 22 October Qatar time, which is 21:00 UTC on 21 October. The change coincides with a migration of the registry's backend platform. The registry has not published updated guidelines; the most recent registration agreements on its site are more than a decade old. The operative detail has reached registrants through QHost, an accredited registrar.

The rules end open registration. Until now, anyone anywhere could register a second-level .qa name without a local company or supporting paperwork. Registration will now run through defined categories: a trade licence or commercial registration, trademark rights, a Qatar ID or residency permit, qualifying sporting, charitable, public or religious organisations, schools and other educational institutions, and government and military entities.

For companies outside Qatar, the trademark route looks like the only plausible one, and even that is unresolved. QHost says it is not clear whether foreign companies can register at all. Until the registry publishes its own text, the categories are known second-hand, and the detail behind them — what counts as a relevant trademark, which documents are accepted — is not.

The rule that matters most for the aftermarket is the prohibition on selling, renting or leasing a second-level .qa domain. That removes the exit. A name held for resale stops being inventory and becomes a renewal obligation with no lawful transfer path. Buyers should treat .qa as a use asset rather than a tradeable one until the registry's own policy says otherwise.

Existing registrants face a different mechanism. Holding a name is not itself a validation event; changing it is. The registry sees nameserver records, so a nameserver change triggers an eligibility check. CNAME and A records sit below that line and do not. The practical consequence, relayed by QHost, is to move nameservers to their intended destination before the new policy takes effect — after the migration, the same edit becomes a test the holder may fail.

The window is short. The report surfaced in the afternoon UTC on 21 October; the deadline is 21:00 UTC the same day. Anyone reading it afterwards is already past the point where the advice helps. And the manoeuvre is one-time: it settles the nameserver question, not the status of the name.

More is unknown than settled. Whether the registry will validate the existing base at migration, at renewal, or only when a record changes. Whether holders who cannot document eligibility lose names immediately or receive a grace period. Whether the resale ban is enforced by audit or by complaint. Whether other suffixes follow; the reported changes concern second-level .qa only.

Eligibility tightening is a familiar move for country-code registries. Resale bans are rarer, and they change what kind of asset a name is. For anyone with .qa exposure the work is concrete: establish which category you can document, decide whether the name is worth keeping on those terms, and do not acquire .qa names expecting to transfer them.

The Sourcedomainnamewire.com

We hope our commentary provided you value, please don't forget to also read the source article at Domain Name Wire.

Discussion