Identity Digital is gobbling up Verisign’s back-end business
Verisign appears to be getting out of the new gTLD back-end registry services business, with Identity Digital taking over most of its dot-brand contracts.
Since 2018, over 80 gTLDs have moved from Verisign’s back-end to a competitor or have been removed from the DNS altogether. Over the same period, it hasn’t won any business from any of its rivals, according to data I’ve compiled.
Over the last few months about 30 new gTLDs have moved their technical back-end from Verisign to competitors, all but two to Identity Digital. Nominet and CIRA picked up a gTLD deal each.
Verisign tells me it’s not interested in providing new gTLD back-end services any more. A Verisign spokesperson said in an email:
In the case of the back-end services we provide to new gTLDs, we continually evaluate our business objectives and a few years ago, we decided that we would not be renewing our current new gTLD registry services customers and that we would help them transition before their contracts expired if they wished.
gTLDs moving home recently include .bosch, .crown, .chanel, .next, .nikon, .juniper and .fidelity.
Given the sheer number of gTLDs going to Identity Digital, it appears that there may be a side deal between the two registries to recommend migration to ID, but both companies declined to comment on that suggestion.
In 2012, Verisign had signed on to be the back-end for 220 new gTLDs, mostly dot-brands. Not all of those made it through the application process, but today my database has the company as RSP-of-record for fewer than 80 2012-round labels.
The company was said to be among the priciest option for dot-brands, trading on decades of .com uptime prestige, but the need for an RSP with 150 million domains under management is debatable when your gTLD is essentially just parked.
And for Verisign, the dot-brand business is not material to revenues and probably not especially profitable, at least when compared to the vast amounts of cash .com effortlessly generates.
In 2021, Verisign lost its deal to manage .tv to GoDaddy, after it declined to compete presumably due to the anticipated lower profit margins.
.org back-end contract up for grabs
Public Interest Registry has started vetting potential registry service provider replacements for Identity Digital, ahead of a formal request for proposals later this year.
The company said this week that in order to run .org’s back-end, which would have to support almost 11 million domains, an RSP would have to hit a list of high-end criteria.
Candidates will have to have seven years experience running an RSP across multiple TLDs, with at least three registry clients, over 500,000 domains, and at least 25 ICANN-accredited registrars on its books, among other items.
That narrows the field down to probably fewer than a dozen companies. The likes of GoDaddy, CentralNic, Verisign, ZDNS, Tucows and Nominet would all presumably qualify, along with Identity Digital itself.
If a transition to a new RSP were to happen, it would be the largest TLD back-end migration in history by a considerable margin. The largest to date was the 3.1 million names that moved from Neustar (now GoDaddy) to Afilias (now Identity Digital) in 2018.
The .org migration from Verisign to PIR in 2003 was when .org was substantially smaller, at 2.7 million names.
According to PIR’s most-recent tax return, Afilias was paid $15.6 million in 2021 for registry services.
PIR said in 2021 that it expects to issue the RFP in the second half of 2023.
GoDaddy could lose out as NIXI brings .in in-house
Indian ccTLD registry NIXI wants to become a back-end registry services provider for its own .in and other TLDs, and seems set to push GoDaddy out of its current role as it looks for a company to build its new infrastructure.
The company is looking to expand its current role as .in overseer and take over day-to-day operational management of the EPP registry, DNS, Whois, etc, from its current back-end. That’s been Neustar, now GoDaddy Registry, since 2019.
By the time the transition takes place, it could be the largest TLD migration in history.
NIXI currently says it has over three million domains under management. The previous biggest move was .au from Neustar to Afilias in 2018, at 3.1 million names. The .org migration from Verisign to PIR in 2003 was for 2.7 million names.
NIXI basically wants a company to come in to design and build a registry system, run it for a year, and then hand over operations, and maybe staff, to NIXI before retreating into a maintenance role for seven years.
The selected provider must be established in India and preference will be given to “companies whose parent / holding company is registered in India having subsidiaries in other developing countries.”
If NIXI already has a preferred provider in mind, it certainly isn’t GoDaddy, judging by this criterion.
“This is as part of future expansion plan / business plan of NIXI,” the tender (pdf), which says several times that NIXI wants to become the back-end for ccTLDs in other developing countries, notes.
After a number of extensions, NIXI’s tender is due to expire next Monday.
Kiwis finally making the switch to EPP with Canadian deal
InternetNZ has picked the winner in its registry replacement project RFP, which will see it switch the entire .nz back-end to the industry standard EPP protocol by the end of next year.
It’s selected the CIRA Registry Platform from Canadian .ca registry CIRA, but will continue to run its own back-end in-house in New Zealand.
InternetNZ had said last October that it planned to overhaul its outdated infrastructure, and put out its feelers for would-be vendors or service providers.
At that time, 65% of its over 720,000 .nz registrations and about 65% of its registrars were still using its old, proprietary Shared Registration System protocol.
Now, SRS is to be deprecated in favor of the CIRA platform and the Extensible Provisioning Protocol that has been industry standard across all gTLDs and many ccTLDs for the better part of two decades.
And they say New Zealand is progressive.
InternetNZ plans to make the switch fully by the end of next year. This is of course going to require some implementation work by registrars, which will have to code new hooks into the .nz registry.
UPDATE: This article was updated April 20 to correct “this year” to “next year”. InternetNZ plans to finish the switch before the end of 2022, not 2021.
Is the .co rebid biased toward Afilias? Yeah, kinda
The Colombian government has come under fire for opening up the .co registry contract for rebid in a way that seems predetermined to pick Afilias as the winner, displacing its fierce rival Neustar.
As I blogged in November, Colombia thinks it might be able to secure a better registry deal, so it plans to shortly open .co up to competitive proposals.
A company called .CO Internet, acquired by Neustar for $109 million in 2014, has been running the ccTLD for the last decade. There are currently around 2.3 million .co domains under management, according to Colombia.
With the renewal deadline looming, the government’s technology ministry, MinTIC, published an eyebrow-raising request for proposals last month.
What’s surprising about the RFP is that some of the four main technical performance criteria listed are so stringent that probably only two companies in the industry qualify — Verisign and Afilias, and so far Verisign has not been involved in the RFP process.
The companies that have been engaging with the government to date are Afilias, Neustar/.CO, Nominet, CentralNic and Donuts.
First, MinTIC wants a registry that’s had at least two million domains under management across its portfolio continuously for two years. All five registries qualify there.
Second, it wants a registry that’s been involved in the migration of a TLD of at least one million names, either as the gaining or losing back-end.
That immediately narrows the pack to just two of the five aforementioned registries — Neustar and Afilias.
Verisign would also qualify, if it’s in the bidding, but I suspect it’s not. Taking over .co would look like a “buy it to kill it” strategy, which would be horrible optics for the Colombian government.
There have only ever been three migrations over one million names, to my knowledge: the Verisign->Afilias .org transition of 2003, the Neustar->Afilias .au move of 2018, and last year’s Afilias->Neustar .in handover.
CentralNic, Nominet and Donuts have all moved numerous TLDs between back-ends, but with much smaller per-TLD domain volumes.
Third — and here’s the kicker — the successful .co bidder will have to show that it processes on average 25 million registry transactions — defined as “billable EPP (write) transactions, as well as all EPP search (read) transactions” — per day. (All of the RFP quotes in this post have been machine-translated from Spanish by Google and run by a few generous Spanish speakers for verification.)
The RFP is not entirely clear on what exact data points it’s looking at here, but my take is that qualifying transactions include, at an absolute minimum, attempts to create a domain, renew a domain, transfer a domain and check whether a domain is registered.
The vast majority of such transactions are in the check and create functions, and I believe a great deal of that activity relates to drop-catching, where registries are flooded with add requests for just-deleted domains.
Whichever way you split it, 25 million a day is a ludicrously high number. Literally only .com, which sees 2.3 billion checks and 1.5 billion adds per month, sees that kind of action.
According to Neustar, which actually runs .co, it only sees 6.4 million transactions per day on average. The requirement to handle 25 million a day is “exaggerated, unjustified and discriminatory” against Neustar, Neustar told MinTIC.
But the RFP allows for the bidding registries to spread their 25-million-a-day quota across all of the TLDs they manage, and this MAY sneak Afilias over the line.
I say MAY in big letters because I don’t believe the numbers that Afilias (and probably other registries too) reports to ICANN every month are reliable.
If you add up the reported, qualifying EPP transactions for September in Afilias’ top four legacy gTLDs — .org, .info, .mobi and .pro — you get to over 25 million per day.
But those same records show that, for example, .mobi, .pro and .info had exactly the same number of EPP availability checks that month — 215,988,497 each.
This is clearly bad data.
I reported on this issue last May, when ICANN’s Security and Stability Advisory Committee informed ICANN that major registries were providing “not reliable” or possibly “fabricated” data about port 43 Whois queries.
Afilias, which was one of the apparent offenders, told me at the time that it was addressing the issue with ICANN, but it does not yet appear to have fully fixed its reporting to enable TLD-by-TLD breakdowns of its registry activity.
It is of course quite possible, even very likely, that Afilias has on average more than 25 million qualifying EPP transactions per day, but how’s it going to prove that to the Colombian government when the numbers it reports under contract to ICANN are clearly unreliable?
It’s a little harder to determine whether Neustar would qualify under the 25-million transaction rule, because some of its largest zones are ccTLDs — .co, .in and .us — that do not publicly report this kind of data. Its comments to the RFP suggest it would not.
Numbers aside, I’ll note that there’s very probably an inherent bias towards legacy gTLD operators like Afilias and against relative newcomers such as CentralNic if you’re counting EPP transactions. As I noted above, a lot of these transactions are coming from drop-catch activity, which is more prevalent on larger, older TLDs where there are more dropping domains that are more likely to have existing backlinks and traffic.
The fourth technical requirement in the Colombian RFP that looks a bit fishy is the requirement that the new registry must have channel relationships with at least 10 of the largest 25 registrars, as listed by a web site called domainstate.com.
I can’t say I’ve looked at domainstate.com very often, if at all, but a quick look at its numbers for September strongly suggests to me that it does not count post-2012 new gTLD registrations in its registrar league table. One registrar with almost four million domains under management doesn’t even show up on the list. This arguably could give an advantage to a registry that plays strongly in legacy gTLDs.
That said, it’s probably an academic point — I don’t think any of the bidders for the .co contract would have difficulty showing that they have 10 of the top 25 registrars on board, whichever way you calculate that league table.
Cumulatively, these four technical hurdles have led some to suggest that Afilias has somehow steered MinTIC towards creating an RFP only it could win.
Apart from what I’ve discussed here, I’ve no evidence that is the case, and Afilias has not yet responded to my request for comment today.
Luckily for the bidding registries, the Columbian RFP has not yet been finalized. Comments submitted by the bidders and others are apparently going to be taken on board, so the barriers to entry for respondents could be lowered before bids are finally accepted.
MinTIC posted an update last night that extends the period that the RFP could run, and the transition period should Neustar lose the contract. A handover, should one happen at all, could now happen as late as February next year.
Neustar’s .co contract up for grabs
Colombia is looking for a registry operator for its .co ccTLD.
If you’re interested, and you’re reading this before noon on Wednesday November 6 and you’re at ICANN 66 in Montreal, hightail it to room 514A for a presentation from the Colombian government that will be more informative than this blog post.
Hurry! Come on! Move it!
The Ministry of Information Technology and Communications (MinTIC) has published a set of documents describing some of the plan to find a potentially new home for .co.
There doesn’t appear to be a formal RFP yet, but I gather one is imminent.
What the documents do tell us is that Neustar’s contract to run .co expires in February, and that MinTIC is looking into the possibility of a successor registry.
Currently, .co is delegated to .CO Internet, a Colombian entity that relaunched the TLD in 2010 and was acquired by Neustar for $109 million in 2014.
But under a law passed earlier this year, it appears as if MinTIC is taking over policy management for .co and may therefore seek IANA redelegation.
There’s no indication I could see that there’s a plan to reverse the policy of allowing anyone anywhere in the world to register a .co, indeed MinTIC seems quite proud of its international success.
The documents also give us the first glimpse for years into .co’s growth.
It had 2,374,430 names under management in September, after a couple of years of slowing growth. The documents state that .co had an average of 323,590 new regs per year for the first seven years, which has since declined to an average of 32,396.
.co is not the cheapest TLD out there, renewing at around $25 at the low end.
Form an orderly queue: New Zealand wants a new back-end
New Zealand is looking to possibly outsource its .nz ccTLD registry back-end for the first time, and has invited interested parties to get in touch.
Registry manager InternetNZ today published a request for expressions of interest in what it’s calling its “registry replacement project”.
It won’t be as straightforward as most registry migrations, as .nz is currently running essentially two different back-ends.
Today, about 65% of its registrations are based on an outdated custom Shared Registration System protocol, with the remainder on the industry standard Extensible Provisioning Protocol.
The proportion of registrars running SRS versus EPP is roughly the same, with about 65% on SRS, according to the REOI.
But the registry wants to get rid of SRS altogether, forcing all SRS-only registrars to adopt the EPP, and the new back-end provider will have to support this transition.
While registrars always have a bit of implementation work to do when a TLD changes back-ends, it’s not usually as complicated as adopting a completely different protocol with which they may not be unfamiliar.
So the risk of issues arising during the eventual handover — which will probably take a bit longer than usual — is probably a bit higher than usual.
But .nz is an attractive TLD. At the start of the month, it had 711,945 domains under management, a pretty good penetration on a per-capita basis when compared to the biggest ccTLDs.
It’s in the top 50 of the 1,338 TLDs for which I have data.
The deadline for responses to the REOI is November 29, a little over a month from now, InternetNZ said.
The registry is taking briefings at ICANN 66 in Montreal from November 2, and the following week in New Zealand.
UPDATE: This article originally stated that InternetNZ has decided to outsource its back end. In fact, outsourcing is just one of a number of options.
.blog registry handover did NOT go smoothly
The transition of .blog between registry back-end providers ended up taking six times longer than originally planned, due to “a series of unforeseen issues”.
Registry Knock Knock Whois There today told registrars that the move from Nominet to CentralNic took 18 hours to complete, far longer than the two to three hours anticipated.
An “unexpected database error” was blamed at one point for the delay, but KKWT said it is still conducting a post-mortem to figure out exactly what went wrong.
During the downtime, .blog registrations, renewals, transfers and general domain management at the registry level would not have been possible.
DNS resolution was not affected, so registrants of .blog domains would have been able to use their web sites and email as usual.
The migration, which covered roughly 200,000 domains, wrapped up at around 0800 UTC this morning. It seems engineers at the two back-end providers, both based in the UK, will have been working throughout the night to fix the issues.
KKWT reported the new CentralNIC EPP back-end functioning as expected but that several days of “post-migration clean-up” are to be expected.
Eighteen hours is more than the acceptable 14 hours of monthly downtime for EPP services under ICANN’s standard Registry Agreement, but below the 24 hours of weekly downtime at which emergency measures kick in.
CentralNic already handles very large TLDs, including .xyz, but I believe this is the largest incoming migration it’s handled to date.
KKWT is owned by Automattic, the same company as WordPress.com.
Mystery .vu registry revealed
Neustar has been selected as the back-end domain registry operator for the nation of Vanuatu.
The company, and the Telecommunications Radiocommunications and Broadcasting Regulator, announced the appointment, which came after a competitive tender process between nine competing back-end providers, last night.
The ccTLD is .vu.
It’s unrestricted, with no local presence requirements, and currently costs $50 per year if you buy directly from the registry, Telecom Vanuatu Ltd (TVL).
Unusually, if you show up at TVL’s office in Vanuatu capital Port Vila, you can buy a domain for cash. I’ve never heard of that kind of “retail” domain name option before.
A handful of international registrars also sell the domains marked up, generally to over the $80 mark.
TVL was originally the sponsor of the ccTLD, but ICANN redelegated it to TRBR in March after Vanuatu’s government passed a law in 2016 calling for redelegation.
Under the deal, Neustar will take over the registry function from TVL after its 24 years in charge, bringing the .vu option to hundreds of other registrars.
Most registrars are already plugged in to Neustar, due to its operation of .us, .biz and .co. It also recently took over India’s .in.
There’s no public data on the number of domains under management, but Vanuatu is likely to have a much smaller footprint that Neustar’s main ccTLD clients.
It’s quite a young country, gaining independence from France and the UK in 1980, a Pacific archipelago of roughly 272,000 people.
Neustar expects the transition to its back-end to be completed September 30.
Nic.br wins dot-brand from Afilias
Brazilian registry Nic.br has won its sixth gTLD client.
It’s taking on the dot-brand back-end business of Natura, a cosmetics company based in its home town of Sao Paulo.
The .natura gTLD was previously managed by Afilias.
I can’t imagine it’s a hugely valuable deal.
Natura has only a few domains in its zone. It’s using global.natura as a portal to its various national ccTLD sites and app.natura as a gateway to app stores where its mobile app can be obtained.
It’s the latest gTLD to change back-ends in the current wave of new gTLD rejiggering to come about as contracts negotiated during the 2012 application round start to expire.
Nic.br also runs the dot-brands .uol and .globo, the small city TLD .rio, the unlaunched generics .bom (means “good” in Portuguese) and .final, and of course its original ccTLD, .br.
Recent Comments