.qwer
Is .qwer a real TLD? Who’s applying to run it?
Nobody has applied for .qwer in its own right, as of 7 October 2026. XServer named .qwer as the backup string of its .server application.
A keyboard-row string with no natural meaning; a gaming in-joke at best, unlikely to be a serious project's main address.
gamers and keyboard or typing hobbyists who want a playful in-joke address, plus speculators betting on a quirky string
Nobody has applied for .qwer in its own right.
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet as .qwer: a semantically empty keyboard/alphabet fragment with no audience of its own, where all the value has to be manufactured by a registry selling it as a blank, cheap, universal namespace rather than by any buyer who already identifies with the word.
Also a coined, meaning-free short string nobody's primary identity already attaches to, so it is the same pure open-registry speculation — a string that only works if the registry invents a use for it after delegation.
Another deliberately contentless placeholder string whose registrants would have to supply the meaning, though it differs from .qwer in carrying a ready-made geek-culture connotation that gives it a built-in constituency .qwer lacks.
What a .qwer domain is
.qwer is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Culture category. Nobody has applied for .qwer in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .qwer domain extension real yet?
.qwer is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .qwer domain?
You can’t yet. A .qwer name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .qwer was .xyz, delegated on 19 February 2014.
Is .qwer a real TLD?
Not yet. .qwer is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .qwer as part of an application for another string. Every entry on this page links to its source.
- XServer · first recordedICANN
“XI2694T-T62176 · XRegistry Incorporated · replacement string of .server”ICANN
- Band chosen: 10-29 (vanity/joke/narrow). The string is the opening run of a standard keyboard row; it carries no dictionary meaning, no category, and no geographic or brand association. On the record it is a standard application filed as a replacement string for .server, with no category tag and no contention, which signals a fallback choice rather than a market thesis. Its only natural constituency is the gaming and typing subculture where the first keyboard-row letters are shorthand for ability keys or for typing itself, and that constituency has shown, by analogy with other joke or gibberish strings in earlier rounds, that it produces a burst of hobby registrations and little primary-identity use (analogy flagged). It is not in the 30-49 band because there is no evident volume driver such as a cheap generic meaning or a large price-driven market; even gaming projects have more descriptive strings to choose from. It is not in the 1-9 band because the string is short, pronounceable, and memorable enough that some hobby sites, gaming clans, and speculators would register it, so a thin but real market exists. Main market uncertainty: whether the gaming shorthand association is strong enough to make .qwer a recognisable in-group identity rather than an unexplained string, which would move it toward the top of its band.