.container
Is .container a real TLD? Who’s applying to run it?
Nobody is chasing .container, as of 7 October 2026. One applicant claimed it and is out. We keep the entry on the record either way.
- Journey To The West
A word owned by shipping and software alike, but neither industry needs it as an address; expect low-volume, explain-it-every-time use.
devops and cloud-native tool vendors wanting a literal namespace, plus freight, intermodal-logistics and container-leasing firms; secondarily self-storage and modular-construction businesses playing on the word
In Journey To The West's published portfolio of 323 strings submitted in the ICANN 2026 round. Their catalog line: “The steel box that moves the world's goods.”
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: an unowned singular generic noun that straddles a physical industry (self-storage/warehousing) and a computing abstraction (stored data), so the registry is selling one word to two unrelated buyer pools and hoping at least one adopts it as primary identity.
Same bet in that a plain English noun was applied for on the wager that a computing paradigm had annexed the word hard enough that infrastructure vendors would treat it as their category home rather than as a dictionary term.
Same kind of string — a short, concrete container noun with no owner — carrying the same weakness that its everyday physical meaning competes with its tech meaning, leaving no single industry that must have it.
What a .container domain is
.container is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody is chasing .container today. The applicants that claimed it are out.
Is the .container domain extension real yet?
.container 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 .container domain?
You can’t yet. A .container 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 .container was .storage, delegated on 18 December 2015.
Is .container a real TLD?
Not yet. .container is not in the DNS root, so nothing resolves under it. It’s here because an applicant claimed .container and is no longer in it. We keep the entry, and every entry on this page links to its source.
- Journey To The West · now abandonedICANN
- Journey To The West · first recordedJourney To The West Corporation
“.container · Trade & Logistics · “The steel box that moves the world's goods.””Journey To The West Corporation
- The string has an unusual dual market: the applicant catalogs it under trade and logistics, but the larger addressable demand over the next 5 years is plausibly the software-container ecosystem, which is large and namespace-hungry. Working against it: by analogy, logistics-flavored dictionary gTLDs (.delivery, .shipping, .cargo-adjacent strings) have seen thin registration bases and near-zero primary-identity use, and devops projects already default to .dev/.io-style namespaces, so .container would need explaining everywhere. Also by analogy, long generic-word gTLDs tend to sell on price promotions rather than brand pull, implying a weak aftermarket beyond a handful of exact-match tech keywords. I place it at the bottom of the 30-49 'usable but limited' band: above 10-29 because the software meaning gives it a real, non-joke registrant pool and some keyword resale value, but below 50-69 because there is no sign of sustained primary-identity demand in either meaning. Main market uncertainty: whether the cloud-native community treats it as a usable identity or purely as a novelty, given entrenched incumbEnglish namespaces.