ds

.navy

Generic top-level domain

RDAP + WHOISsold by 3 registrarsGovernment & Politics

Register
$42.81first year
Renew
$46.98a year
Transfer
$42.81to move it
Registrars
3quoting it
Lookup
RDAP + WHOISanswers for it
DNSSEC
Signed1 DS record in the root
Level
Secondmybrand.navy

Check a name

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

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 navy

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

Every published quote in the bundled table, cheapest registration first. The figure ds prints beside .navy is the mean of the registration column — $42.81, which undercuts 43% of the 881 priced TLDs.

RegistrarRegisterRenewTransfer
porkbun.comcheapest$33.47$33.47$33.47
namecheap.com$43.98$45.98$43.98
101domain.com$50.99$61.49$50.99
Mean — what ds prints$42.81$46.98$42.81

List prices in US dollars, bundled with the binary and last regenerated 2026-09-09. Promotions, ICANN fees, taxes and premium names all move the real number, and a registry may decline to sell you the name at all. See Prices.

Where to register

3 registrars in the bundled table publish a registration price for .navy, which is evidence they sell it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld navy --where prints them.

Put a name in the box above and each link becomes that registrar's search for mybrand.navy, where it publishes one. This list is what the price table knows, not the whole market — see Where to register.

Who can register

No eligibility rule is on file for .navy, 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. .navy has both, so RDAP answers and WHOIS is the fallback if it does not.

RDAP
https://rdap.identitydigital.services/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.identitydigital.services/rdap/domain/mybrand.navy — a 404 means the name is free.
WHOIS
whois.nic.navyQueried on port 43, from the bundled whois.json. The name is called free when the reply contains Domain not found. — text matching, which is why RDAP is preferred where it exists.

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

The registry

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

Run by
Dog Beach, LLCBased in United States of America. Delegated 2014-05-29, record last updated 2025-10-07.
Registry site
www.identity.digitalWhere the registry documents .navy — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.identitydigital.servicesWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
v0n0.nic.navyv0n1.nic.navyv0n2.nic.navyv0n3.nic.navyv2n0.nic.navyv2n1.nic.navyThe 6 authoritative servers for the .navy 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.

  • Government & Politics The public sector, the armed forces, and elections.

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

Delegated to
  • v0n0.nic.navy65.22.28.342a01:8840:1e::34
  • v0n1.nic.navy65.22.29.342a01:8840:1f::34
  • v0n2.nic.navy65.22.30.342a01:8840:20::34
  • v0n3.nic.navy161.232.14.342a01:8840:f8::34
  • v2n0.nic.navy65.22.31.342a01:8840:21::34
  • v2n1.nic.navy161.232.15.342a01:8840:f9::34
The 6 name servers the root hands out for .navy, 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 24535RSA/SHA-256 · SHA-2566F05F1CC418BDC0C32058586CD7DE8CF28EC70AA9C978E2613389226053C53BF
Each one is a fingerprint of .navy'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 .navy 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 navy. NS and dig +norec @a.root-servers.net navy. DS.

Also answered by rdap.identitydigital.services

and 438 more zones on the same server.

Priced near it