.conf
Is .conf a real TLD? Who’s applying to run it?
Nobody has applied for .conf in its own right, as of 7 October 2026. Name Space LLC named .conf as the replacement string of its .fest application.
A natural short home for conferences, but event-driven demand and the .com habit keep it a niche, modest-value address.
conference and event organizers, especially tech-community conferences that already brand themselves as "<name> Conf", plus developer-tool projects playing on the config-file meaning
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: a bare gathering-category generic that the organizer of the gathering puts its primary identity on, which only works if people accept a category word as the name of a specific occasion.
Also a convening-format noun sold to whoever runs the convening, but it carries a second life as a software/discussion-board word, so the buyer pool is split in a way the target's is not.
The same clipped-shorthand bet as the target: a trade's own abbreviation of its category noun, which pays off only if insiders already write it that way and outsiders can decode it.
What a .conf domain is
.conf is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody has applied for .conf in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .conf domain extension real yet?
.conf 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 .conf domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .conf name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .conf was .events, delegated on 4 February 2014.
Is .conf a real TLD?
Not yet. .conf is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .conf as part of an application for another string. Every entry on this page links to its source.
- Name Space LLC · first recordedICANN
“NSL2674T-T26988 · NAME SPACE LLC · replacement string of .fest”ICANN
“NSL2674T-T89586 · NAME SPACE LLC · replacement string of .brain · Deactivated VSL2633T-T11017 · Vinyl Strings, LLC · replacement string of .wealth · Deactivated VSL2633T-T61422 · Vinyl Strings, LLC · replacement string of .form · Deactivated VSL2633T-T72232 · Vinyl Strings, LLC · replacement string of .air · Deactivated VSL2633T-T88070 · Vinyl Strings, LLC · replacement string of .apparel · Deactivated XL2625T-T57285 · XYZ.COM LLC · primary”ICANN
“We are thrilled by the opportunity to help expand the domain name space with innovative new alternatives.”Domain Name Wire
- Band chosen: 30-49 (usable but limited), at its low end. The string reads naturally as 'conference' and matches an existing naming habit in the technology community, where events brand as '<name> Conf', so a left-of-dot pairing like js.conf or data.conf is plausible as a primary identity for a recurring event over the next 5 years; conferences are a worldwide, recurring buyer group rather than a joke or single-event fad, which is why it is not in the 10-29 band. It is not in the 50-69 band because, by analogy with event-themed TLDs such as .events and .expo, event namespaces have tended to see registrations without becoming the primary identity of serious events (flagged as analogy, no figures asserted): organizers mostly keep the event under the organizer's own .com or .org or a subdomain, demand is seasonal and tied to the event calendar, and the aftermarket for such strings has by analogy been thin. The second meaning of 'conf' as a configuration-file extension is a developer-vanity hook rather than a commercial one and risks diluting the conference reading. On the record, the only application is Name Space LLC's, where .conf is a replacement string for .fest and contention count is 0; this is stated neutrally and bears only on the likelihood of a single, undivided launch, not on string quality. Main market uncertainty: whether tech-conference organizers, who already use the 'Conf' convention, would move a flagship event's primary address onto a standalone TLD rather than a subdomain of the sponsoring project or company, and whether the registry positions the string toward events or toward the config-file meaning, which would split a market that is already modest.