.drive

Generic top-level domain

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.drive

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 drive

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 .drive, 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 .drive, 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. .drive has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

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

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

The registry

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

Run by: Charleston Road Registry Inc.Based in United States of America. Delegated 2015-06-04, record last updated 2025-04-11.
Registry site: www.registry.googleWhere the registry documents .drive — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: pubapi.registry.googleWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: ns-tld1.charlestonroadregistry.comns-tld2.charlestonroadregistry.comns-tld3.charlestonroadregistry.comns-tld4.charlestonroadregistry.comns-tld5.charlestonroadregistry.comThe 5 authoritative servers for the .drive 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

What it is for

Our reading, not a fact — nothing in the root zone says what a TLD means. Hand-maintained in tld-categories.json.

Internet & Technology Software, hosting, data, devices, and the web itself.

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 .drive was delegated to; this is what the root actually answers with when a resolver asks it where .drive lives.

Delegated to: ns-tld1.charlestonroadregistry.com216.239.32.1052001:4860:4802:32::69
ns-tld2.charlestonroadregistry.com216.239.34.1052001:4860:4802:34::69
ns-tld3.charlestonroadregistry.com216.239.36.1052001:4860:4802:36::69
ns-tld4.charlestonroadregistry.com216.239.38.1052001:4860:4802:38::69
ns-tld5.charlestonroadregistry.com216.239.60.1052001:4860:4805::69
The 5 name servers the root hands out for .drive, with the glue addresses that come with them — every one of them answers 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 32974RSA/SHA-256 · SHA-256BE68DE85AD9A87657CEB1F620FA37FEBFC725180E40117914886CCBB6947D619
Each one is a fingerprint of .drive'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 .drive 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 drive. NS and dig +norec @a.root-servers.net drive. DS.