Consider the least exciting part of opening a website: the address works. You type a name, press Enter, and expect the machinery to know where to send you. Nobody applauds. Nobody wonders which company kept the directory available. For Verisign, that lack of curiosity is a rather useful business condition.
- Verisign runs the registries behind .com and .net. Registrars sell the names.
- It collects recurring wholesale fees for registrations and renewals.
- Its advantage combines technical reliability with contractual operating rights.
At September 30, 2026, its .com and .net base contained 182.5 million registrations. Those are registrations, not people or active websites. A single person can own many. Still, the scale makes a small annual charge worth examining. This is a company whose financial story begins with an apparently trivial question: who keeps track of the names?
The shop and the stockroom
Buy a domain through an accredited registrar and you encounter the shop: search boxes, discounts, renewal reminders. Behind that shop sits the registry. Verisign maintains the authoritative registration system for .com and .net and the infrastructure that directs DNS queries toward a domain’s name servers. Hosting the actual website is somebody else’s job.
The distinction matters when comparing alternatives. Changing registrars can change your bill or customer service. It does not replace Verisign as the .com registry operator. Other domain extensions compete for your attention; a registrar selling the same extension occupies a different place in the chain.
Ten dollars, multiplied
As of October 23, 2026, the annual .com registry fee is $10.26. Verisign has announced $10.97 from November 1. These are wholesale figures; the registrar decides the retail price. Registration revenue is recognized over the registration term, which gives the business a recurring rhythm rather than a dependence on a single launch day.
In 2025, Verisign generated $1.6566 billion in revenue and $1.121 billion in operating income. Divide the latter by the former and the operating margin is roughly 68%. Keeping a shared naming system running is expensive work, but the figures show how profitable the established operation has become.
Operating income / operating costs. Rounded; before interest and tax.
The latest quarter, reported October 22, brought $443 million in revenue, up 5.7% from a year earlier. Dependability supports the proposition. So do contracts governing who operates the registry and how prices may rise. Treating those agreements as a minor footnote would miss much of the business.
The padlock came first
Jim Bidzos launched Verisign in 1995 as an RSA trust-services spinout. Its early task was helping strangers trust one another online through digital certificates. Visa, Intel, Mitsubishi and Ameritech were among the founding investors. The browser padlock and Verisign checkmark gave an abstract cryptographic transaction a recognizable face.
Acquiring Network Solutions in 2000 brought the .com and .net registries. The company later narrowed its scope. In 2010, it agreed to sell its authentication business to Symantec for approximately $1.28 billion in cash. That business had supplied 39% of the preceding quarter’s revenue. This was a substantial change in what shareholders owned.
The stated rationale was focus on internet infrastructure. Rising demand for DNS, expanding dependencies and changing security threats made that field a larger responsibility. The useful lesson is quite specific: a company can sell an important business because a different responsibility deserves more attention.
The wrong answer to a wrong address
There is a catch to being responsible for shared infrastructure. In September 2003, Verisign introduced Site Finder. Requests for nonexistent .com and .net names received the address of a Verisign server instead of the standard error response. A missing destination became an opportunity to direct traffic.
What failed first was compatibility with expectations elsewhere in the system. ICANN cited effects on email applications, web browsing and established protocols. Software had reasons to distinguish a nonexistent name from an existing one. Turning failure into an answer changed that distinction for everyone.
In shared infrastructure, even an error message can be part of the product.
YesPress analysis
Verisign initially rejected a voluntary suspension request. ICANN then demanded reversal and threatened contractual enforcement. The service was suspended in October. This was a documented change of action under pressure, rather than evidence of a private change of heart. The episode explains why infrastructure innovation requires consultation beyond the people who build it.
Reliability has a boundary
In July 2026, Verisign reported 29 years of continuous availability for the .com and .net resolution system. That is a defined infrastructure claim. Your hosting provider, internet connection or individual domain settings can still fail. Understanding the boundary makes the achievement more useful to a customer.
Its responsibilities also extend upward through DNS. Verisign operates the A and J root server identities and maintains the root zone under agreement with ICANN. The familiar diagram of 13 root identities describes logical names, not thirteen lonely machines. The wider root system uses thousands of servers.
Its mission is plain: “Verisign enables the world to connect online with reliability and confidence, anytime, anywhere.” Its expertise includes cryptography and internet standards. DNSSEC adds authentication to DNS data, helping detect tampering; it does not make a dishonest website honest. Verisign’s published values emphasize stewardship and accountability, sensible priorities for engineers whose changes can affect systems outside their own organization.
Copy the discipline. Read the contract.
A business owner can use a registrar to secure a domain, then arrange hosting separately. Registrars can use Verisign’s tools, including NameStudio’s domain suggestions. Engineers can examine its public code and technical work. None of these uses requires confusing a registry with a complete security service.
For other companies, the transferable habit is defining a dependable service and measuring its continuity. The economics will not necessarily follow: they depend on demand, renewals and operating agreements. October’s results also introduced a limited beta for Verisign Informed, a validation service, while .web rollout remained on track. Even this continuity business has new things to test.