.huge
Is .huge a real TLD? Who’s applying to run it?
Nobody has applied for .huge in its own right, as of 7 October 2026. Intercap named .huge as the replacement string of its .all application.
A playful adjective ending with vanity appeal but no natural category; expect memorable domain hacks, not serious primary identities.
founders, marketers and hobbyists who want a playful, memorable domain hack (go.huge, dream.huge), plus a thin crowd of speculators holding short dictionary words
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: a bare English superlative adjective with no category to anchor it, sold as an open registry where the string's only value is the boast it lets any registrant make about anything.
Also a magnitude/superiority adjective offered as a generic open suffix, but it carries a secondary structural reading ("top level") and short-string cheap-volume appeal that a pure hype word like the target does not.
Same expressive-modifier bet — an attitude word nobody's primary identity sits on, monetized by marketers and campaign microsites using it as a punchline rather than a category — though it is an exclamation rather than a scale adjective.
What a .huge domain is
.huge is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. Nobody has applied for .huge in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .huge domain extension real yet?
.huge 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 .huge domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .huge name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .huge was .best, delegated on 27 February 2014.
Is .huge a real TLD?
Not yet. .huge is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .huge as part of an application for another string. Every entry on this page links to its source.
- Intercap · first recordedICANN
“IRI2679T-T65817 · Intercap Registry Inc. · replacement string of .all”ICANN
“EDI2665T-T28371 · Endpoint Domains, Inc. · primary IRI2679T-T96997 · Intercap Registry Inc. · replacement string of .wiz · Deactivated NA2626T-T63059 · ShortDot (Ireland) Limited · replacement string of .ask · Deactivated XL2625T-T48604 · XYZ.COM LLC · replacement string of .con · Deactivated”ICANN
- Band chosen: 10-29 (vanity/joke/narrow). .huge is a bare adjective with no category, industry, geography or product class attached to it; its appeal is tonal (bigness, hype, humor), which makes it a slogan ending rather than an identity ending. By analogy (flagged as analogy), earlier adjective and exclamation strings such as .cool, .wow, .best, .fun and .top show two outcomes: either a registry drives volume through deep promotional pricing, producing registrations that are rarely primary identities and churn heavily, or the string stays small and lives on a handful of memorable hacks. .huge sits toward the narrower end of that family because it reads naturally in fewer phrases than .cool or .fun and is harder to say as a brand name without sounding like a joke. It is not in the 30-49 band because there is no evident channel or buyer group that would register it at volume on merit rather than on price, and the brand signal it gives a serious project is weak to negative in most sectors. It is not in the 1-9 band because a real, if small, market exists for playful dictionary-word hacks, and a short, pronounceable English adjective will attract some aftermarket interest for the obvious phrases. The application on the record is recorded as a replacement string of .all, filed as a standard application by Intercap Registry Inc.; stated neutrally, that means the registry's positioning and pricing for .huge specifically are unknown, which matters because adjective TLDs' outcomes have historically (by analogy) been set almost entirely by registry pricing and registrar promotion rather than by inherent demand. Main market uncertainty: whether any registry treats .huge as a promotional volume string or as a premium-priced curiosity, and whether any visible consumer brand adopts a .huge hack as its primary address and normalises the ending.