.shop domains: registry operator and eligibility rules

GMO Registry, Inc., based in Tokyo, is both the IANA-listed sponsoring organisation and the ICANN-contracted registry operator for .shop, under a Base (Non-Sponsored) Registry Agreement signed 8 April 2016 (ICANN registry agreement). The sources we checked name no separate corporate parent behind GMO Registry, and the name servers (a/b/k/l.gmoregistry.net) along with the WHOIS/RDAP services all run on GMO's own infrastructure. So the technical back end looks to be handled in-house rather than farmed out to a third party such as Tucows or Neustar.

Three distinct roles sit behind any .shop domain, and it pays to know which is which. The registry, GMO Registry, holds the master database for the whole extension, sets the technical rules and answers to ICANN. A registrar, such as Gandi, GoDaddy or EuroDNS, is the accredited seller you actually deal with to register, renew or transfer a name; the registry itself does not sell to the public. The registrant is you, the person or organisation whose contact details sit in WHOIS against the domain. Policy for .shop, including dispute rules and any restrictions, comes from the registry agreement with ICANN, but registrars apply it day to day, so things like pricing tiers or renewal reminders can differ from one registrar to the next even though the underlying registry rules stay the same.

.shop is a wide-open gTLD. Anyone, anywhere, can register a name: no nexus requirement, no trading licence, no trademark to wave around. Abion and EuroDNS both confirm the registry itself imposes no restrictions, and GMO Registry won't even ask whether you actually run a live e-commerce site, despite the name practically screaming "retail".

Names run from 2 to 63 characters, built from letters, numbers and hyphens (though hyphen placement rules can vary by registrar). Internationalised domain names work too, in a range of scripts. Want something short and keyword-rich? There's a premium tier for that, at a higher upfront registration fee, though renewals and transfers drop back to standard pricing afterwards, according to DonDominio. None of that changes what individual registrars might bolt on at checkout, identity verification, payment checks, that sort of thing. The registry stays hands-off; the seller you buy from might not.

.shop domains move between registrars the same way most gTLDs do, using an EPP authorisation code. And just like other generic extensions, a domain gets locked against transfer for 60 days after initial registration, and again after any change of registrant. That's not a .shop rule specifically, it's ICANN policy applied across the board.

Registration terms run from one year up to ten, according to registrar documentation, and you can renew in one-year increments any time before expiry. GMO Registry's published contract doesn't lay out a public schedule of grace, redemption and pending-delete periods with actual day counts, so don't assume a fixed figure, check with your registrar instead. ICANN's baseline Expired Registration Recovery Policy sets a 30-day Redemption Grace Period for gTLDs in general, and at least one registrar quotes a .shop restore fee of $124.20 on top of the normal renewal cost. Treat that as a rough sense of scale rather than a universal number. What you won't find anywhere in the registry material is a .shop-specific grace period length or a restore fee set by GMO Registry itself. Those figures come from individual registrars, and they vary.

The registry's own marketing leans on customer examples like Doshi.shop, Flavor.shop, Superfoodguru.shop and Balsamico.shop, independent retailers who switched from or ran alongside a .com when their preferred name wasn't sitting there in .com (get.shop). GoDaddy's domain guidance makes a similar case, pitching .shop as a fit for direct-to-consumer brands and creators building a merch line off a social following (GoDaddy).

A few practical things before you point a .shop domain live. The registry doesn't publish a forced-HTTPS or HSTS-preload requirement the way some newer extensions do, but any storefront taking payment details needs TLS regardless of what the registry says. There's nothing in the registry documentation about email deliverability rules specific to .shop either; spam filtering on any gTLD comes down to sending reputation, not the extension. Used as your primary domain, .shop does exactly the job it was built for: it tells visitors, instantly, that the site sells something. Used purely as a redirect from an existing .com, it doesn't do much beyond defensive registration. One naming quirk worth flagging: don't stack the word. A name like myshop.shop reads clumsily and cancels out the clarity the extension is supposed to give you.