.world domains: registry, eligibility and lifecycle rules

The IANA delegation record lists Binky Moon, LLC, based at Identity Digital Inc.'s Bellevue, Washington address, as the sponsoring organisation for .world. The ICANN Registry Agreement confirms Binky Moon, LLC as the contracted registry operator, under a base, non-sponsored agreement signed 12 June 2014.

Binky Moon's parent is Identity Digital Inc., which runs one of the biggest gTLD portfolios in the industry and supplies the administrative and technical contacts named in the IANA record. Name servers sit on the nic.world infrastructure, and RDAP lookups route through Identity Digital's own service, a sign that Identity Digital handles the technical side directly rather than farming it out to a separate backend. The sources we checked turn up no distinct third-party backend provider for .world.

In practical terms: the registry is the authoritative database of every registered .world name, run by Binky Moon/Identity Digital. A registrar is the company you actually buy from, one accredited to sell .world names, and it deals with the registry on your behalf. The registrant is you, the person or organisation whose contact details sit on the registration. Policy on transfers and expiry comes from ICANN at the top, gets applied by the registry, and is carried out day to day by your registrar.

.world runs an open registration policy. No residency requirement, no trademark, no professional qualification, no need to represent any particular type of organisation. Individuals and companies anywhere can register, and you don't even need a local administrative contact, according to active-domain.com.

This is set at registry level, so it holds regardless of which registrar you go through. Registrars can still add their own checks on top, payment verification, the usual WHOIS accuracy rules that apply across gTLDs generally, but none of that amounts to a .world-specific eligibility test. The real constraints are technical, not administrative: name length, permitted characters, the standard syntax rules every domain has to follow rather than anything particular to this extension.

With no sponsored community and no nexus requirement, .world lands at the more permissive end of the gTLD spectrum. Closer to .com or .net in who can hold a name than to any restricted country-code domain.

Transfers follow the usual ICANN drill: your current registrar hands over an AuthInfo code, you lift any transfer lock, and the new registrar files the request. As with most gTLDs, a fresh registration or a recent change of registrant triggers a 60-day lock before the domain can move house, under the domain-wide ICANN transfer policy. Nothing about this is unique to .world. ICANN has already approved plans to retire that lock eventually, but the sources we checked give no date for when the change actually lands on this extension.

Registration terms run from 1 to 10 years, and registrar sources describe renewal as instant. Beyond that, the sources we checked stay quiet on .world's own grace period length or restore fee. The ICANN Expired Registration Recovery Policy sets a floor rather than a fixed answer: registries must offer at least a 30-day Redemption Grace Period after deletion, during which a lapsed name can be clawed back, usually for a fee on top of standard renewal that each registrar sets on its own terms. Something similar almost certainly applies here, but check your own registrar's fee schedule rather than guess a number. None is published for .world specifically in the sources we have.

Registrar commentary points to a handful of recurring uses for .world: international nonprofits and charities pitching a global mission, travel and tourism operators, multinational corporations, and consultants or educators working across borders, as set out by Network Solutions. Coverage from CNET also frames .world as suited to sites built around immersive or virtual experiences. Nobody names a specific flagship .world site, so treat these as use-case patterns rather than proof of a killer example out there already.

Before going live, note that the registry itself does not appear to mandate HTTPS or HSTS for .world, unlike some Google-run extensions, so certificate setup is down to your host, not the registry. Email deliverability on a less common gTLD depends far more on your SPF, DKIM and DMARC setup than on the extension itself, though a newer ending can still draw a second glance from recipients, so warm up your sending volume gradually rather than blasting from day one. As a primary domain, .world works best when the word genuinely describes the scope of the business, not as a generic redirect target you bolt on for the look of it. One naming tip worth keeping: pair .world with a concrete noun, a mission, a product, a sector, rather than a vague brand word. The extension only reads well when the combination forms a real phrase, not a name searching for meaning.