.ggee

Generic top-level domain

RDAP

Register: —first year
Renew: —a year
Transfer: —to move it
Registrars: —quoting it
Lookup: RDAPanswers for it
DNSSEC: Signed1 DS record in the root
Level: Secondmybrand.ggee

Check a name

One command, straight against the registry — no account, no page to load.

Name

Fills the command and the registrar links below in with your own name. The page is static — nothing is looked up here, and nothing you type leaves the browser.

ds mybrand --tld ggee

Add --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.

What it costs

No registrar in the price table bundled with ds quotes .ggee, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells. See Prices for supplying your own table with --pricing-file.

Who can register

No eligibility rule is on file for .ggee, which is not the same as a promise that it is open: the list is hand-maintained and covers the restricted TLDs a registrar is likely to offer you. Check the registry's own page before counting on a name. 81 TLDs do carry a rule — see Who can register.

How `ds` answers for it

RDAP first, WHOIS second — the same order for every TLD. .ggee has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

RDAP: https://rdap.gmoregistry.net/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.gmoregistry.net/rdap/domain/mybrand.ggee — a 404 means the name is free.

ds mybrand --tld ggee --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .ggee today. See Accuracy notes.

The registry

From IANA's delegation record for .ggee. .ggee is a generic TLD.

Run by: GMO Internet, Inc.Based in Japan. Delegated 2014-12-18, record last updated 2019-08-07.
Registry site: nic.ggeeWhere the registry documents .ggee — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: rdap.gmoregistry.net · whois.nic.ggeeWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: a.gmoregistry.netb.gmoregistry.netk.gmoregistry.netl.gmoregistry.netThe 4 authoritative servers for the .ggee zone — what the root delegates to. Nothing ds queries directly; they are what makes a registered name resolve.

What it is

Derived from the root zone and ICANN's registry list — each one is a fact with a source.

generic IANA Root Zone Database types it "generic"
new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated

In the root zone

The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .ggee was delegated to; this is what the root actually answers with when a resolver asks it where .ggee lives.

Delegated to: a.gmoregistry.net37.209.192.42001:dcd:1::4
b.gmoregistry.net37.209.194.42001:dcd:2::4
k.gmoregistry.net37.209.196.4
l.gmoregistry.net37.209.198.42001:dcd:4::4
The 4 name servers the root hands out for .ggee, with the glue addresses that come with them — 3 of them answer over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC: Signed — 1 DS record in the root
key 602RSA/SHA-256 · SHA-2560D54D07BEBF1A6AFE76ECF6D55C48698D8F233B719009329E4465B75078479D5
Each one is a fingerprint of .ggee's own signing key, published by the root and signed with the root's key — which is how a resolver that trusts only one key can prove an answer under .ggee came from its registry and was not tampered with in transit. It says nothing about who owns a name or whether one is free.

Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net ggee. NS and dig +norec @a.root-servers.net ggee. DS.