.query
Is .query a real TLD? Who’s applying to run it?
Nobody has applied for .query in its own right, as of 7 October 2026. Suffix Inc. named .query as the replacement string of its .research application.
A clever suffix for data, search and AI tools, but few serious projects would make .query their main address.
developers and data-tool makers (database, search, analytics and AI question-answering products) who want a descriptive, hack-style address for a side project or product sub-brand
No applications recorded for this TLD yet.
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 exactly: an unowned generic word for the act of asking a machine for information, applied for so that whoever runs the asking layer can put its primary identity on the function itself rather than on a brand.
Same bet of claiming a bare technical function-noun that an entire infrastructure industry speaks natively, where the value rests on practitioners (not consumers) adopting the term as their address.
Shares the question-shaped-word bet — identity built on the posture of asking rather than on a category or company — but it is a consumer phrase-completion play, not a term of art for a retrieval system.
What a .query domain is
.query is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody has applied for .query in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .query domain extension real yet?
.query 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 .query domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .query name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .query was .search, delegated on 29 June 2017.
Is .query a real TLD?
Not yet. .query is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .query as part of an application for another string. Every entry on this page links to its source.
- Suffix Inc. · first recordedICANN
“SI2639T-T37419 · Suffix Inc. · replacement string of .research”ICANN
“LFGL2683T-T12771 · Link Freedom Group Ltd · primary SI2639T-T84933 · Suffix Inc. · replacement string of .rep · Deactivated”ICANN
“Catalog lists: .asap .create .future .lfg .mvp .out .pal .planet .research .share .tag .this .visit”Suffix Inc.
- Band chosen: 10-29 (vanity/narrow), near its top. 'Query' is a real English and technical noun with genuine resonance in databases, search and AI question-answering, so there is a plausible end-use pocket: developer tools and data products that want an address like sql.query or ask.query. By analogy (flagged as analogy), action or concept-noun strings from the 2012 round such as .search, .click, .link and .digital either stayed effectively unused under a restricted operator or registered at volume mainly on price, with weak brand signal and thin aftermarket; dictionary nouns that describe an activity rather than a category or community tend to land there. It is not in the 30-49 band because 'query' names an action, not a category of business, so adoption would depend on wordplay rather than on a buyer group that needs the namespace, and I expect primary-identity use to be rare over the next 5 years; it is not in the 1-9 band because the string is short, pronounceable, globally understood in tech, and fits a live trend of AI and data tools branding around asking and answering. Applicant facts from the record: a single standard application by Suffix Inc., recorded as a replacement string for a primary application for .research, with no contention recorded; neutrally, a replacement-string posture suggests launch effort may prioritise the primary string, which tempers adoption likelihood but does not change the string's intrinsic market. Main market uncertainty: whether the current wave of AI query and agent tooling creates a durable identity convention around 'query' (the way .ai became a convention for AI startups, by analogy) or whether the word stays a feature name rather than an identity.