.fix
Is .fix a real TLD? Who’s applying to run it?
.fix is contested: 6 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are Identity Digital, GoDaddy Registry, Innovation Service, Aruba, ShortDot and Radix. XYZ Registry named .fix as a backup string for its .park application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup. Intercap named .fix as a backup string for its .hire application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A punchy verb domain for repair services and developer tools, but most serious businesses will treat it as an extra, not their main address.
home-repair and trade businesses, gig-economy service marketplaces, and developer or IT tooling brands who want a short action-word identity (including bug.fix / hot.fix style name hacks)
One of 46 ICANN 2026-round applications Radix announced on its own applications page. Radix states it intends to build and operate each TLD it wins.
One of the 80 strings ShortDot published for the ICANN 2026 round. ShortDot states it has submitted 40 applications, but publishes the 80 strings without revealing which 40 are applications and which 40 are designated replacements. The submission claim is therefore applicant-level, not string-level: nothing in the source says ShortDot applied for THIS string. Catalogued, not announced.
Aruba S.p.A. told Domain Name Wire it applied for 39 strings in the 2026 round 'as primary or replacement', listing .fix among them without saying which strings are primary. The claim is the applicant's own, post-filing, relayed by the publication. Founder ruling 2026-09-09: recorded as announced. Already on the record from another applicant, so this adds to the contention set.
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .hire application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .park 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.
Same bet exactly: an open generic service-verb/noun sold to independent tradespeople and repair shops who need a descriptive second-level identity, where value depends on millions of small local operators choosing a category word over .com.
Same bet shape — a short, punchy English verb-as-utility aimed at support and service-desk use, monetized as a memorable call-to-action string rather than a category directory, though its buyer skews to software/customer support rather than trades.
Also a generic service word whose registrants put their remedy-for-a-problem identity on it (helpdesks, service arms of brands), betting the same way that customers will type the action they need — but it is a longer, more corporate-noun version of the same wager.
What a .fix domain is
.fix is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Commerce category. 6 applications for it are on ICANN’s Reveal Day list.
Is the .fix domain extension real yet?
.fix 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 .fix domain?
You can’t yet. A .fix 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 .fix was .repair, delegated on 28 December 2013.
Is .fix a real TLD?
Not yet. .fix is not in the DNS root, so nothing resolves under it. It’s here because .fix is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- XYZ Registry · first recordedICANN
- Intercap · first recordedICANN
- Identity Digital · first recordedICANN
- GoDaddy Registry · first recordedICANN
- Innovation Service · first recordedICANN
- Radix · now confirmedICANN
- ShortDot · now confirmedICANN
- Aruba · now confirmedICANN
- ShortDot · now announced
- Aruba · first recordedDomain Name Wire (Andrew Allemann), quoting Aruba S.p.A.
- ShortDot · first recordedShortDot (Ireland) Limited
- Radix · first recordedRadix
“APEC2611T-T67575 · Aruba PEC S.P.A. · primary · contention set 2026-85 IRI2679T-T99888 · Intercap Registry Inc. · replacement string of .hire · Deactivated ISL2626T-T82788 · Innovation Service Limited · primary · contention set 2026-85 NA2626T-T48225 · ShortDot (Ireland) Limited · primary · contention set 2026-85 NA2631T-T72857 · Registry Services, LLC · primary · contention set 2026-85 RC2677T-T79526 · Rein Check, LLC · primary · contention set 2026-85 RTIS2674T-T29496 · Radix Technologies Inc SEZC · primary · contention set 2026-85 XL2625T-T66829 · XYZ.COM LLC · replacement string of .park · Deactivated”ICANN
“APEC2611T-T67575 · Aruba PEC S.P.A. · primary · contention set 2026-85 ISL2626T-T82788 · Innovation Service Limited · primary · contention set 2026-85 NA2626T-T48225 · ShortDot (Ireland) Limited · primary · contention set 2026-85 NA2631T-T72857 · Registry Services, LLC · primary · contention set 2026-85 RC2677T-T79526 · Rein Check, LLC · primary · contention set 2026-85 RTIS2674T-T29496 · Radix Technologies Inc SEZC · primary · contention set 2026-85”ICANN
“Aruba S.p.A., which operates the .cloud top level domain, is expanding its domain portfolio. The company told Domain Name Wire that it applied for 39 top level domains in this year's new TLD round. That number includes replacement strings. [...] The company applied for the following strings as primary or replacement: aid, all, ask, beta, bit, bnb, cart, ciao, daily, demo, easy, fix, gaming, gen, genius, gym, happy, hello, hola, human, kit, lab, mars, max, moon, omg, pec, pop, rem, roma, sign, sito, super, tag, tex, vps, yes, zen, zzz”Domain Name Wire (Andrew Allemann), quoting Aruba S.p.A.
“ShortDot (Ireland) Limited has submitted 40 applications to ICANN's 2026 New gTLD Program. The 80 strings shown include applied-for and designated replacement strings across ShortDot's 40 ICANN applications, presented without revealing their status or pairing.”ShortDot (Ireland) Limited
“Radix has applied for these TLDs; we do not own or operate them today.”Radix
- I place .fix in the 30-49 band (usable but limited), at 40. The string is a short, common English verb with two genuine demand pools: repair and trade services (plumbers, phone repair, handyman platforms) and software culture (bugfix/hotfix vocabulary), and the applicant is a large portfolio registry that states it builds and operates what it wins, which by analogy to its established channel reach supports meaningful registration volume. It is not in the 50-69 band because, reasoning by analogy from service-verb and repair-adjacent TLDs of the 2012 round, such strings have historically produced mostly defensive or secondary registrations rather than sustained primary-identity use, and their aftermarkets have been thin; adoption of .fix as a main brand would still need explaining to customers. It is not in the 10-29 band because the word is positive, broadly commercial, and maps to real recurring purchase intent (things break, people search for fixes), which is more than vanity or event-driven demand. Specific volumes, prices, and renewal figures for analogous TLDs are unknown to me under the rules here, so those comparisons are qualitative analogies only. My main market uncertainty: whether service-sector small businesses, the natural buyer, will use a verb TLD as their primary identity at all, or default to legacy extensions and treat .fix as a redirect.