.homes domain names: what buyers need to know

XYZ.COM LLC runs the show here. It's named as the sponsoring organisation in the IANA delegation record and holds the registry operator role under the .homes Registry Agreement with ICANN, signed 9 January 2014. That wasn't always the case, though. IANA's own transfer report shows .homes started out with DERHomes, LLC back in 2014, before the whole thing moved over to XYZ.COM LLC in April 2021.

The technical plumbing is a separate job, handled by CentralNic, who show up as the technical contact in the IANA record. GoDaddy's help pages back this up, confirming CentralNic as the back-end provider running the actual registration systems. We couldn't pin down a corporate parent for XYZ.COM LLC beyond a "Powered by XYZ" link sitting on the registry's own site, so we're not stating that as fact here.

Worth untangling the jargon while we're at it. The registry is XYZ.COM LLC, the outfit holding the ICANN contract and writing the rules for the whole .homes extension. The registrar is whoever you actually buy the domain from, GoDaddy, Namecheap, take your pick, accredited to sell .homes names and dealing with the registry on your behalf. The registrant is just you: the person or organisation whose name lands on the WHOIS record once you've bought it.

.homes is open to anyone, first-come, first-served. Per GoDaddy's registrar guidance, XYZ.com sponsors the extension and CentralNic runs the back-end, but nobody's checking whether you sell houses, own one, or have ever set foot in an estate agency before you can register.

That's a registry-level decision, not a loophole. The .homes Registry Agreement simply doesn't include the eligibility carve-outs you see with some country-code or sponsored extensions. Registrars can still run their own account and payment checks, and some set extra rules for particular registration scenarios, so it's worth reading the fine print at whichever registrar you use rather than assuming the base registry policy is the whole story.

Where things actually get complicated is price, not eligibility. Plenty of .homes names are sold as registry premium, which means higher registration and renewal fees than the standard rate, according to tld-list's pricing data. The exact criteria the registry uses to decide what's premium isn't spelled out anywhere in that data.

Transferring a .homes domain follows the same ICANN process as any other gTLD. Unlock the domain, grab the EPP authorisation code from your current registrar, hand it over to the gaining registrar. The usual restrictions apply too: no transfers within 60 days of initial registration or a previous transfer, and any registrar lock needs lifting first. Nothing unusual here.

Registration terms run one to ten years, with renewals capped at nine, according to Namecheap's registration page. Some .homes names sell as registry premiums, which tend to cost more both to register and to renew. The sources we checked do not spell out exactly what makes a name premium, per tld-list, so don't expect a tidy formula.

What nobody publishes: the post-expiry grace period, the redemption period, or the restore fee XYZ.COM LLC and its backend would charge to bring back a lapsed .homes domain. Don't assume these match .com's timelines. Ring a registrar and ask directly before you bank on any grace window.

Real-world use leans hard into the property sector the string is named after. EuroDNS's rundown of real estate extensions flags cocoon.homes, a home-staging and interior design business, as a live example of the extension being used commercially, sitting alongside the more established property-industry picks like .properties and .realestate.

Nothing in the sources we checked suggests the registry forces HTTPS or HSTS on .homes, unlike some restricted or sponsored TLDs, so ordinary hosting and certificate practice applies here, nothing special. There's no evidence of a specific spam-filter or deliverability penalty for .homes either. Still, treat it like any newer gTLD: warm up a new sending domain slowly and don't expect it to land in inboxes the way an aged .com would from day one.

.homes earns its keep as a primary domain when the business is obviously property-related and the name flows without repeating "home", think Cocoon.homes, not CocoonHomes.homes. If the main brand already sits on a .com, .homes does more useful work as a geographic or campaign-specific redirect, a city-level microsite for instance, than as a full replacement.