.reno
Is .reno a real TLD? Who’s applying to run it?
.reno is not contested. One application for it is on ICANN’s Reveal Day list, as of 18 November 2026. It is Phoenix Domain Partners.
Who is applying, and what they run today
Phoenix Domain Partners filed 13 applications across the round.
Will names sell?
A niche address for home-renovation businesses, with a city-name double meaning; memorable but rarely a serious primary identity.
Last round the AI scored the 2012 strings blind to their fate. Strings it scored 60 or more hold a median 27,168 names today; those under 30, a median of 30. .reno’s closest 2012 strings hold .vegas 12K, .miami 12K and .boston 4K.
The nearest 2012 strings, and how many names each holds today
The closest 2012 string, .vegas, held 11,749 names, June 2026. .miami held 12,356; .boston held 4,433. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.
Same bet exactly: a single mid-size Nevada city's own name sold as a civic/commercial identity namespace, where value depends on local hotels, casinos, agencies and residents choosing to re-badge off .com for hometown signalling rather than on any national category demand.
A US city-name string whose only buyers are businesses and residents whose primary identity is that one metro, so it lives or dies on the same thing .reno does: whether a city's local market has enough brand pride and SMB density to sustain a namespace.
Also a lone US city string betting that civic identity converts into registrations, but the parallel is looser because a top-tier metro with national recognition, universities and a much larger business base carries an easier version of the same bet than a small-market city does.
home-renovation contractors, remodelers and DIY/renovation media who want a short vertical address, plus a thin secondary pool of businesses tied to the city of Reno
What a .reno domain is
.reno is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Commerce category. One application for it is on ICANN’s Reveal Day list.
Is the .reno domain extension real yet?
.reno 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 .reno domain?
You can’t yet. A .reno 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 .reno was .vegas, delegated on 31 March 2014.
Is .reno a real TLD?
Not yet. .reno is not in the DNS root, so nothing resolves under it. It’s here because .reno is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Band chosen: 10-29 (vanity/narrow). The string carries two readings: 'reno' as colloquial shorthand for renovation, and Reno as a city name. The record shows a single standard (non-geographic) application, filed as a replacement string for .connect by Phoenix Domain Partners (legal name 101130013 Saskatchewan Ltd.); the standard type suggests the renovation reading is the intended market, and the applicant's Canadian base is consistent with that slang being most natural in Canada and Australia. Renovation is a large, fragmented, local-service vertical, but by analogy (flagged as analogy) construction- and trade-adjacent TLDs such as .contractors, .construction, .repair and .build have produced modest registration bases and thin aftermarkets, with most contractors defaulting to .com and a local-SEO web presence. The double meaning dilutes the brand signal in both directions: renovation firms outside slang-using regions may not read it as renovation, and Reno-based businesses may hesitate at a TLD not run as a city namespace. Not in 30-49 because I do not see registrations reaching volume without heavy price promotion, and the string reads as a vanity hack to most buyers; not in 1-9 because a real trade vertical and a real city affinity each supply some genuine primary-identity demand (a remodeler using 'smith.reno' is plausible). Main market uncertainty: whether 'reno' as renovation shorthand is widely enough understood in the United States and other large English-language contractor markets to drive adoption beyond Canada and Australia, and whether the city reading creates confusion or a usable second demand pool. Specific registration counts, pricing and outcomes for the analogous TLDs are unknown here and are not asserted.