.hug
Is .hug a real TLD? Who’s applying to run it?
Nobody has applied for .hug in its own right, as of 7 October 2026. Name Space named .hug as the backup string of its .sound application.
A warm, memorable word with few serious uses: expect gift, care and campaign sites, not companies building their main brand on it.
charities, care and wellness services, greeting and gifting brands, and campaigners who want an affectionate, feel-good address for a side project or promotion
Nobody has applied for .hug 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 almost exactly: a short, warm, non-commercial gesture word that names no industry and no customer, so it can only work as an expressive label people adopt for sentiment rather than as the primary identity of any business category.
Also a pure affect noun with no vertical behind it, betting that a feeling-word can carry registrations on emotional resonance alone, though an abstract state is slightly easier to attach to brands and campaigns than a physical gesture is.
The same emotion-word bet one size up: it shares .hug's lack of a defined buyer but has real commercial gravity (dating, weddings, charity, gifting) that a gesture as narrow as a hug cannot summon.
What a .hug domain is
.hug 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 .hug in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .hug domain extension real yet?
.hug 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 .hug domain?
You can’t yet. A .hug 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 .hug was .smile, delegated on 5 December 2015.
Is .hug a real TLD?
Not yet. .hug is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .hug as part of an application for another string. Every entry on this page links to its source.
- Name Space · first recordedICANN
“NSL2674T-T61555 · NAME SPACE LLC · replacement string of .sound”ICANN
- Band chosen: 10-29 (vanity/joke/narrow). The string is short and instantly understood, which gives it memorability for emotional, charitable and gifting uses (free.hug, send.a.hug style phrasing, mental-health and elder-care campaigns), but a serious project rarely chooses an emotion word as its primary identity, so the expected pattern is event-driven and promotional registrations with thin renewal, as with other sentiment strings such as .love and .fun (inference from analogy; their actual registration figures are unknown to me under the rules here). It is not in the 30-49 band because there is no evident volume or price-driven channel and no category of businesses whose name naturally ends in 'hug'; it is not in the 1-9 band because the word is positive, globally recognised English, and a modest care/wellness/greeting niche can realistically sustain some genuine use. The record shows one standard application by Name Space LLC, filed as a replacement string for its primary .sound, which suggests the string may be marketed as part of a portfolio rather than as a stand-alone category play; I use this only to note that adoption likelihood depends on general-channel distribution. Main market uncertainty: whether a wellness, mental-health or caregiving segment adopts affectionate addresses as real brand identities over the next 5 years, or whether demand stays at one-off campaigns and novelty gifts.