.festival
Is .festival a real TLD? Who’s applying to run it?
.festival is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Identity Digital. XYZ named .festival as a backup string for its .connect application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A clear, self-explaining word for events, but festivals already live on .com and social, so demand stays modest.
music, film, food and cultural event organizers, plus event-tech and ticketing startups wanting a descriptive address
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .connect application, shown as deactivated: another applicant applied for the same string or named it as a backup
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.
The same bet one rung up the genus: an open generic naming the gathering itself, sold to whoever organizes one and needs the occasion — not a company — to be the primary identity.
Also a single-word generic for a gathering that anyone staging one can claim, so it rides on organizers and vendors adopting the occasion as their name, though it skews personal and promotional rather than a recurring produced event.
A named genre of recurring cultural event where the event, not a firm, carries the identity, and success depends on a finite circuit of organizers plus their fans and vendors registering — the same narrow, event-producer demand base.
What a .festival domain is
.festival is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. One application for it is on ICANN’s Reveal Day list.
Is the .festival domain extension real yet?
.festival 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 .festival domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .festival name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .festival was .events, delegated on 4 February 2014.
Is .festival a real TLD?
Not yet. .festival is not in the DNS root, so nothing resolves under it. It’s here because .festival is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Band chosen: usable but limited (30-49), at its low edge. The string is a plain, globally understood dictionary word with a defined buyer group — event organizers and the companies serving them — so it is more than a vanity or joke string, and a festival could plausibly use name.festival as a primary identity. It is not a strong niche TLD (50-69) because, reasoning from analogy, descriptive event-style strings from the 2012 round (such as .events, .party and .live) did not become the default identity for their sector; established festivals keep legacy .com or country-code addresses and lean on social and ticketing platforms, so a .festival address needs explaining and the aftermarket is likely thin beyond a handful of generic city or genre names. It is above vanity (10-29) because festival demand is recurring and seasonal rather than one-off, and city-plus-festival or genre-plus-festival strings have real end-use utility. The verified-facts block shows a single confirmed applicant (Pirin Tablet, LLC), no category tag and no contention; pricing, launch policy and marketing intent are unknown, and those will drive whether this becomes a low-volume vanity space or a modestly adopted descriptive one. Main market uncertainty: whether the operator prices and markets it as a mass descriptive TLD or as a premium curated namespace; the volume and primary-use outcome differ substantially between those two paths.