.gap
Generic top-level domain
Nobody outside the registry can register here. .gap is a brand TLD run by The Gap, Inc., which under ICANN's Specification 13 means its operator is the only permitted registrant. ds reports names here as PRIVATE rather than AVAILABLE, and leaves the zone out of --tld all unless you pass --private include. See Brand and reserved TLDs.
- Registration
- Closedno public names
- Operator
- The Gap, Inc.
- Lookup
- RDAPanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.gap
Check a name
Names under .gap cannot be registered, but ds will still tell you what the registry says.
ds mybrand --tld gapAdd --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 .gap, 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, though here it is neither: the zone is closed. See Prices for supplying your own table with --pricing-file.
Who can register
Nobody outside The Gap, Inc. — see the note at the top of this page.
How ds answers for it
RDAP first, WHOIS second — the same order for every TLD. .gap has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.
- RDAP
https://rdap.nic.gapFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.nic.gap/domain/mybrand.gap— a 404 means the name is free.
ds mybrand --tld gap --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .gap today. See Accuracy notes.
The registry
From IANA's delegation record for .gap. .gap is a generic TLD.
- Run by
- The Gap, Inc.Based in United States of America. Delegated 2016-07-14, record last updated 2024-05-11.
- Registry site
- www.gap.comWhere the registry documents .gap — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.nic.gapWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
a.nic.gapb.nic.gapc.nic.gapns1.dns.nic.gapns2.dns.nic.gapns3.dns.nic.gapThe 6 authoritative servers for the .gap zone — what the root delegates to. Nothingdsqueries 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.
genericIANA Root Zone Database types it "generic"brandICANN records Specification 13 — a brand TLD, closed to the publicnew-gtldICANN delegated it on or after 2013-10-23, when the 2013 round opened — seedelegated
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 .gap was delegated to; this is what the root actually answers with when a resolver asks it where .gap lives.
- Delegated to
a.nic.gap37.209.192.92001:dcd:1::9b.nic.gap37.209.194.92001:dcd:2::9c.nic.gap37.209.196.92001:dcd:3::9ns1.dns.nic.gap156.154.144.662610:a1:1071::42ns2.dns.nic.gap156.154.145.662610:a1:1072::42ns3.dns.nic.gap156.154.159.662610:a1:1073::42
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 34711RSA/SHA-256 · SHA-256
E6B688299E2DFC3B96259647E8A564475401D4504729BF8B523A08B4359B4C9F
- key 34711RSA/SHA-256 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net gap. NS and dig +norec @a.root-servers.net gap. DS.