.order
Is .order a real TLD? Who’s applying to run it?
.order is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are CamConnecting and Link Freedom Group.
A call-to-action web address for online ordering; handy for links and campaigns, but few businesses would make it their main identity.
restaurants, food-delivery services, and e-commerce brands wanting a memorable direct-ordering link (brand.order), plus marketers running order-now campaigns
In LFG's published list of 300+ strings submitted before the ICANN window closed on 2026-08-12. Their catalog tagline: “Raise your hand, make your move.”
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: a bare, ubiquitous English transaction verb sold as a call-to-action address for merchants and platforms, so nobody's primary identity lives there and the registry is renting a checkout step rather than a category membership.
Same bet in a narrower vertical: a transactional verb-noun naming the moment a customer commits, bought by ordering/booking intermediaries as an action URL rather than as a statement of who the registrant is.
Adjacent stage of the same commerce workflow with the same one-word-verb structure, but it skews toward financial institutions defending a payments identity rather than merchants renting a generic transaction verb.
What a .order domain is
.order is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Commerce category. 2 applications for it are on ICANN’s Reveal Day list.
Is the .order domain extension real yet?
.order is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .order domain?
You can’t yet. A .order 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 .order was .buy, delegated on 5 December 2015.
Is .order a real TLD?
Not yet. .order is not in the DNS root, so nothing resolves under it. It’s here because .order is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- CamConnecting · first recordedICANN
- Link Freedom Group · now confirmedICANN
- Link Freedom Group · first recordedLink Freedom Group
“CCS2640T-T48725 · Cam Connecting SARL · primary · contention set 2026-173 LFGL2683T-T78260 · Link Freedom Group Ltd · primary · contention set 2026-173”ICANN
“.order · Commerce · “Raise your hand, make your move.””Link Freedom Group
- Band chosen: usable but limited (30-49). The string reads as an action verb, so its natural use is brand.order as a redirect to an ordering page rather than a primary identity, which caps end-use utility and brand signal. It is not in the strong-niche band (50-69) because, by analogy, action-verb TLDs have tended to serve as campaign or redirect namespaces rather than genuine primary identities, and the aftermarket for verb-suffix names is thin since the meaningful inventory (food terms, cuisine terms, brand names) is narrow. It is not in the band below (10-29) because the ordering use case is real, recurring, and commercially adjacent to money movement: a restaurant or retailer plausibly registers and actively uses brand.order at volume if priced accessibly, which is more than event-driven vanity demand. The secondary sense of 'order' (fraternal, monastic, fictional organizations) adds a small culture/brand tail. Applicant facts: the string is announced by Link Freedom Group, which filed more than 300 strings in the ICANN 2026 round and categorizes this one as Commerce; a portfolio applicant of that breadth suggests registry-side marketing attention per string may be spread thin, which I weigh neutrally but slightly against rapid category-building. Main market uncertainty: whether ordering-platform intermediaries (delivery apps, POS and online-ordering vendors) would ever surface .order links by default, since restaurants mostly acquire ordering URLs through those platforms rather than registrars; without that channel, demand stays retail-registrar-driven and shallow over the next 5 years.