.website domain names: registry, eligibility, renewal

IANA's delegation record lists Radix Technologies Inc. as the sponsoring organisation for .website, and the ICANN Registry Agreement names Radix Technologies Inc SEZC as the contracted registry operator, a base, non-sponsored agreement signed 3 April 2014. IANA's transfer reports show the registration hopping between related Radix entities over the years: first to DotWebsite Inc. in 2014, then to Radix FZC in 2021, then back to Radix Technologies Inc. in 2024. That pattern reads as internal corporate reshuffling, not a change of ownership.

The technical contact on file is Tucows.com, Co., which runs the trs-dns nameservers named in the delegation record. Radix's own policies page, though, states that registry functions for all Radix TLDs are supported by CentralNic Ltd. Those two sources contradict each other, so this guide treats the current backend provider as unconfirmed rather than picking a side. ICANN sits above both, holding the agreement that sets the rules Radix has to operate within.

For a registrant, the three roles don't overlap. Radix is the registry: it sets policy for the .website namespace, defines pricing tiers and runs the authoritative database behind the extension. Registrars, the resellers listed on Radix's own get.website page among others, sell the registrations to the public and handle billing, support and day-to-day DNS changes. The registrant is simply whoever's details sit on the registration record, the party on the hook for renewal and for following both Radix's and ICANN's rules.

Radix's launch policy puts .website on a first-come-first-served basis for anyone, individual or organisation, once Sunrise and Landrush wrap up. No nationality test, no eligibility hoops. Sunrise held names back for trademark holders verified through the Trademark Clearinghouse, and Landrush let early applicants in ahead of general release. Both phases are ancient history now, given the domain launched back in 2014.

The policy sets a one-year minimum registration term. That figure applied to Sunrise and Landrush applications, but it's also the floor for ordinary registrations in practice. Radix also runs Pricing Tiers, categories of premium names that carry higher registration, renewal and transfer fees than a standard string. Which names actually sit in a tier isn't published anywhere; registrars have to ask their account managers to find out.

Past that registry-level baseline, registrars can bolt on their own account checks, payment verification or abuse policies, but that's registrar practice, not anything specific to .website. There's no country nexus requirement here, no industry-verification step, nothing of the sort.

A .website domain moves between registrars the way most generic top-level domains do: the losing registrar drops the ClientTransferProhibited lock and hands over an authorisation code, then the gaining registrar pushes the request through the standard ICANN transfer process. ICANN's GNSO voted in 2025 to eventually scrap the long-standing 60-day post-registration and post-transfer lock, but implementation wasn't in force as of the sources reviewed here. Assume the lock still applies unless your registrar tells you otherwise.

Radix's published policy for .website sets a one-year minimum term for Sunrise and Landrush applications, and general availability sticks to the same one-year floor you'll find across most gTLDs. What the sources we checked do not give is just as important: no maximum term for .website is stated anywhere, and Radix's policy page never publishes the length of the post-expiry grace period, the redemption period, or what it costs to restore a name that's lapsed. Elsewhere in gTLD land the pattern is usually a few weeks of free grace followed by a paid redemption window, but nothing in the sources here nails down those figures for .website specifically. Don't guess. Ask your registrar before you let a renewal slide.

Radix's own promotional page for the extension lists a handful of early adopters, including petidco.website, livechat.website, customkitchen.website, boulder.website, anthropology.website and discjockey.website, mostly small businesses and hobby projects rather than large brands. That fits the pattern: this string tends to turn up on modest, single-purpose sites rather than flagship company domains.

A few practical points before you go live. Nothing in the sources reviewed shows the registry imposing an HTTPS or HSTS requirement on .website, unlike some newer TLDs that mandate encrypted connections at the registry level, so that decision sits with you and your host. As with any newer or less common extension, build up sending volume and authentication (SPF, DKIM, DMARC) gradually if you plan to send mail from a .website address. Inbox providers weight domain history when filtering, and a brand-new TLD with no track record gets treated with suspicion at first. The extension works fine as a primary address for a small or single-purpose project, but plenty of buyers register it defensively instead and just redirect it to an existing .com. One naming point specific to this string: because "website" is already sitting in the suffix, do not stack the word again in the second-level label. mysite.website or myweb.website reads as redundant. Put the brand name alone in front of the dot and leave it at that.