Speed-dating new TLD Registry Providers: VeriSign
July 18th, 2008
The introduction to this series gave a quick overview of the registry providers who came to our Registry Speed Dating event at the recent ICANN meeting in Paris. Most new top-level domain applicants will want to avoid the very expensive task of building their own registry system. Instead, they’ll outsource. This series profiles the registry providers competing for that outsourced business.
Keep in mind that these registry providers had five minutes only to answer some rapid-fire questions, and what we have is a quick tabulation of the results. All of the registry providers were well-prepared and (from what they told us) have strong offerings.
Caveats: There is no single perfect registry provider. Each have different strengths and serve different markets. This guide is to help you match your needs to the right registry provider. The answers below are from the representatives of the registry providers, and not an independent evaluation. Also keep in mind that this is draft information; registries may change their policies.
Now let’s have a look at them one by one, in the order they presented to us. At the end of this series, I’ll put together a downloadable PDF which will serve as a comparison chart.
First up: VeriSign

| Represented by | Sarah Langstone, Jennifer Gore |
| TLDs currently supported | COM NET CC TV JOBS NAME |
| Provides marketing support | Yes |
| Hosts registry on their system | Yes |
| Open-source software all or in part | No |
| Subscription, per-unit, flat-fee pricing | Open to any model |
| Invest money in TLD? | Will consider investment |
| Can accommodate complicated business rules | Yes |
| DNS resolution services? | Yes |
| WhoIs services | Yes |
| Customer profile (registration volume) | Medium - Large |
| IDN support | Yes |
| DNSSEC support | Yes |
| IPv6 support | Yes |
| Help with application, lobbying | Yes |
| Registrar system included | No |
| Differentiating factors | Stable, secure platform; can handle any volume |
I suspect that at least some of the registry providers will read through this series and take note of comments, so fire away.
Tags: VeriSign, VRSN, new gTLD, new TLD, new top-level domains, Sarah Langstone, Jennifer Gore, ICANN, domain registry





Nice series, Anthony!
Interesting (and confusing) to see that VeriSign says it’s offering DNSSEC support. As far as I know, VeriSign has only been experimenting with DNSSEC, and there’s no actual DNSSEC deployment like, for example, in Sweden.
So, I will regard “DNSSEC support” in this survey as: “Verisign might support this in the future, we’re ready for it, technically”. It does not reflect the current state of features supported for serving com/net and other TLDs mentioned.
VeriSign’s “Project Titan” (with support for DNSSEC services) is not there yet.
Note that VeriSign CTO Ken Silva is not enthusiastic about implementing DNSSEC at VeriSign.
See also this story:
http://www.heise.de/english/newsticker/news/109818
Jacco Tunnissen | July 18th, 2008 at 4:48 pm