ds

.verisign

Generic top-level domain

RDAP + WHOISbrand TLD

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

Check a name

Names under .verisign 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 verisign

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 .verisign, 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 VeriSign, 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. .verisign has both, so RDAP answers and WHOIS is the fallback if it does not.

RDAP
https://tld-rdap.verisign.com/verisign/v1From IANA's bootstrap, refreshed when this page was built. The lookup is https://tld-rdap.verisign.com/verisign/v1/domain/mybrand.verisign — a 404 means the name is free.
WHOIS
whois.nic.verisignQueried on port 43, from the bundled whois.json. The name is called free when the reply contains no match for — text matching, which is why RDAP is preferred where it exists.

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

The registry

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

Run by
VeriSign, Inc.Based in United States of America. Delegated 2015-11-06, record last updated 2026-03-30.
Registry site
www.verisign.comWhere the registry documents .verisign — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
tld-rdap.verisign.com · whois.nic.verisignWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
ac1.nstld.comac2.nstld.comac3.nstld.comac4.nstld.comThe 4 authoritative servers for the .verisign 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 .verisign was delegated to; this is what the root actually answers with when a resolver asks it where .verisign lives.

Delegated to
  • ac1.nstld.com192.42.173.302001:500:120::30
  • ac2.nstld.com192.42.174.302001:500:121::30
  • ac3.nstld.com192.42.175.302001:500:122::30
  • ac4.nstld.com192.42.176.302001:500:123::30
The 4 name servers the root hands out for .verisign, 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 29816ECDSA P-256/SHA-256 · SHA-256F54B156BB5A1C4B07E9ECEC5A35CE98FF85B841F08221985C9CF54C01D81C1A8
Each one is a fingerprint of .verisign'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 .verisign 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 verisign. NS and dig +norec @a.root-servers.net verisign. DS.

Also answered by tld-rdap.verisign.com

and 3 more zones on the same server.