.homecare
Is .homecare a real TLD? Who’s applying to run it?
Nobody has applied for .homecare in its own right, as of 7 October 2026. Phoenix Domain Partners named .homecare as the replacement string of its .bbq application.
A narrow label for home-care agencies; a real industry, but most will keep a .com and the string adds little brand weight.
home-care and domiciliary-care agencies, caregiver staffing firms, and senior-care franchises wanting a descriptive local web 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 exactly: a compound generic naming a care-delivery sector, sold to the many independent provider organisations in it who would each put their primary identity on the category word rather than on a brand.
Same buyer pool and the same 'category noun as provider identity' bet, but the bare root sits one abstraction level up and splits across unrelated meanings (customer care, car care, child care), so the registrant it must attract is far less defined than for a named care sector.
Also a service-profession generic whose registrants are small owner-operated care practices wanting a credential-flavoured address, though it bets on one licensed clinical discipline's practitioners rather than on an agency-staffed in-home service industry.
What a .homecare domain is
.homecare 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 .homecare in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .homecare domain extension real yet?
.homecare 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 .homecare domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .homecare name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .homecare was .healthcare, delegated on 30 July 2014.
Is .homecare a real TLD?
Not yet. .homecare is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .homecare as part of an application for another string. Every entry on this page links to its source.
- Phoenix Domain Partners · first recordedICANN
“MLG2688T-T77522 · 101130013 Saskatchewan Ltd. · replacement string of .bbq”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: 10-29 (vanity/narrow), at its upper edge. The buyer group is genuine: home care is a large, fragmented service industry made up mostly of small local agencies, and 'city.homecare' reads naturally as a descriptive address. But by analogy (flagged as analogy) with existing health-adjacent strings such as .care, .healthcare, .clinic and .dental, descriptive service TLDs in this space have drawn modest registration bases and are rarely chosen as a primary identity; agencies tend to register a .com and treat the descriptive TLD as a redirect, if at all. The string is long, a compound word, and already covered semantically by .care and .healthcare, so it competes with established substitutes rather than opening a new namespace. Not the band above (30-49): I do not expect registrations at volume or on price, because the catchment is a single service sub-vertical and the aftermarket for such strings has, by analogy, been thin. Not the band below (1-9): there is a real, identifiable buyer with a plausible end-use, and defensive registrations by franchises and larger providers are likely. On the record, the string has one application, filed as a replacement string of .bbq by Phoenix Domain Partners (standard type, not brand/community/geographic); treated neutrally, a replacement-string filing is consistent with a portfolio launch, which informs adoption likelihood only in that marketing would likely be generic rather than industry-led. Main market uncertainty: whether home-care operators, under regulatory and referral pressure to look credible, will adopt a descriptive TLD as their primary address or continue to see .com as the trust default; specific registration figures for the analogous TLDs are unknown to me here.