What is .verisign?
Brand TLDs operate under Specification 13 of ICANN's registry agreement. It lets a trademark owner keep every second-level name for itself, so you won't find .verisign names for sale at any registrar.
.verisign entered the DNS root zone on November 25, 2015, 10 years ago. It came out of ICANN's New gTLD Program, the 2012 application round that grew the root from 22 generic TLDs to well over a thousand.
VeriSign, Inc. also runs 5 other TLDs, including .com, .comsec, .name, .net and .web.
On the technical side, .verisign is served by 4 authoritative name servers, every one of them reachable over IPv6. It is also DNSSEC-signed: the root zone carries a DS record for .verisign, which lets validating resolvers check its answers cryptographically. Registration data is published over RDAP and WHOIS (the WHOIS server is whois.nic.verisign).
Same registry, other endings
5 other TLDs share this operator.
.verisign FAQ
What country is .verisign?
None. .verisign is a generic top-level domain, so it isn't tied to any country.
Who owns the .verisign domain extension?
VeriSign, Inc. operates .verisign as its registry, under a registry agreement with ICANN.
When was .verisign created?
.verisign was delegated to the DNS root zone on November 25, 2015.
Is .verisign a valid domain?
Yes. .verisign is an active top-level domain in the DNS root zone, delegated in 2015, so .verisign addresses work in every browser.
Can I buy a .verisign domain?
No. .verisign is a brand TLD under ICANN Specification 13, so names are reserved for VeriSign, Inc.
Is .verisign DNSSEC-signed?
Yes, the root zone holds a DS record for .verisign.
Sources
Data from IANA root zone version 2026102000. Last changed March 30, 2026. Spotted something wrong? Tell us.
