.roof
Is .roof a real TLD? Who’s applying to run it?
Nobody has applied for .roof in its own right, as of 7 October 2026. Phoenix Domain Partners named .roof as the replacement string of its .quince application.
A roofing-trade address that contractors may buy for local marketing, but few will make it their main name.
roofing contractors, roofing material suppliers and home-services lead-generation sites wanting a descriptive local-marketing address
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 single generic noun naming one building trade's domain, sold as primary identity to thousands of small local contractors who all need a geo-qualified name, with no corporate or community claimant to defend it.
Same bet in the same shape: the building component itself rather than the profession, counting on the installers and suppliers of that component to adopt the material's name as their address.
Also a part-of-the-house noun bet on the remodel trade that sells it, but its buyer pool widens into consumer and lifestyle use, where .roof stays almost purely a contractor's trade sign.
What a .roof domain is
.roof is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. Nobody has applied for .roof in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .roof domain extension real yet?
.roof 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 .roof domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .roof name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .roof was .plumbing, delegated on 14 November 2013.
Is .roof a real TLD?
Not yet. .roof is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .roof as part of an application for another string. Every entry on this page links to its source.
- Phoenix Domain Partners · first recordedICANN
“MLG2688T-T49491 · 101130013 Saskatchewan Ltd. · replacement string of .quince”ICANN
“MLG2688T-T61684 · 101130013 Saskatchewan Ltd. · replacement string of .beach · Deactivated XL2625T-T45963 · XYZ.COM LLC · replacement string of .mart · Deactivated”ICANN
“Phoenix Domain Partners published 13 strings for which it says it has applied and paid the application fees.”Domain Name Wire
- Band chosen: 30-49 (usable but limited). The string is a plain English trade noun tied to one large, fragmented home-services vertical where contractors spend heavily on local search and lead generation; that gives a realistic pool of registrants who would buy a descriptive address (a city or surname before .roof) as a marketing or redirect name. By analogy (flagged as analogy) with existing trade-vertical TLDs such as .plumbing, .contractors and .builders, that demand tends to materialize as modest, price-sensitive registration volume with little primary-identity use and a thin aftermarket. It is not in the 50-69 band because trade-vertical TLDs have not, by analogy, shown sustained primary-identity adoption or a real secondary market, and the noun 'roof' is a less natural fit than the trade term 'roofing', which weakens the string further. It is not in the 10-29 band because the demand is tied to an ongoing commercial trade rather than an event or a joke, so registrations should recur year over year rather than fade. Applicant facts on the record are neutral: a single standard application, filed as a replacement string for a primary application of .quince, with no contention recorded; this says nothing about the string's market beyond a single-operator launch. Main market uncertainty over the next 5 years: whether roofing contractors treat a descriptive TLD as worth paying for at all when they already rely on .com plus directory and map listings for local visibility, or whether volume comes mainly through registrar promotions.