ds

.vanguard

Generic top-level domain

RDAP + WHOISbrand TLD

Nobody outside the registry can register here. .vanguard is a brand TLD run by The Vanguard Group, 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 Vanguard Group, Inc.
Lookup
RDAP + WHOISanswers for it
DNSSEC
Signed1 DS record in the root
Level
Secondmybrand.vanguard

Check a name

Names under .vanguard cannot be registered, but ds will still tell you what the registry says.

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 vanguard

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 .vanguard, 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 Vanguard Group, 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. .vanguard 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.vanguard — a 404 means the name is free.
WHOIS
whois.nic.vanguardQueried 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 vanguard --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .vanguard today. See Accuracy notes.

The registry

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

Run by
The Vanguard Group, Inc.Based in United States of America. Delegated 2016-08-18, record last updated 2023-08-11.
Registry site
vanguard.comWhere the registry documents .vanguard — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.identitydigital.services · whois.nic.vanguardWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
a0.nic.vanguarda2.nic.vanguardb0.nic.vanguardc0.nic.vanguardThe 4 authoritative servers for the .vanguard 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"
  • brand ICANN records Specification 13 — a brand TLD, closed to the public
  • 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 .vanguard was delegated to; this is what the root actually answers with when a resolver asks it where .vanguard lives.

Delegated to
  • a0.nic.vanguard65.22.112.722a01:8840:6e::72
  • a2.nic.vanguard65.22.115.722a01:8840:71::72
  • b0.nic.vanguard65.22.113.722a01:8840:6f::72
  • c0.nic.vanguard65.22.114.722a01:8840:70::72
The 4 name servers the root hands out for .vanguard, 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 28675RSA/SHA-256 · SHA-256DE83F2879537F8479C81335DA97C8D0B923767B78B5FB56544889D3A7006EFB2
Each one is a fingerprint of .vanguard'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 .vanguard 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 vanguard. NS and dig +norec @a.root-servers.net vanguard. DS.

Also answered by rdap.identitydigital.services

and 438 more zones on the same server.