Verisign’s .net is on the rocks due to new gTLDs, executives have confirmed.
Speaking to investors and analysts on the company’s third-quarter earnings call last week, CFO George Kilguss said that .net “is experiencing some headwinds from the launch of the new gTLD program”.
Further comments from Kilguss and CEO Jim Bidzos seem to confirm what DI reported a month ago: .net is in trouble.
Latest stats collated by DI show that the .net zone file shrunk by over 121,000 domains in the seven months between March 26 and October 26 this year.
Executives said on the call that .net stood at 15.1 million names at the end of September. That compares to 15.2 million at the end of the previous quarter.
“It’s been relatively flat,” Kilguss said. “I actually think .net has held up pretty well over the year with all these new names coming on… So I don’t view .net’s performance as anything negative.”
Bidzos told analysts that “confusion” around the new gTLDs was to blame.
“I think generally, .net may be more susceptible to that confusion that swirls around new gTLDs,” he said.
He characterized .net as being like new gTLDs, falling into “that category of ‘different'”.
In my view, this is an implicit acknowledgement that .net has been getting a free ride for the last 20 years.
Asked whether the .net weakness could spill over to .com, Bidzos said that .com is a “trusted brand” because it’s almost 30 years old and has a 17-year record of uninterrupted up-time.
While there’s no doubt that .com is a trusted brand, it’s not because of its up-time or longevity, in my view — .net has the same stability record and is actually fractionally older than .com.
The reason .net is suffering now is that that for the last two decades it’s been essentially a defensive play.
People buy the .net when they buy the .com because they’ve been marketed as a bundle — the only two truly generic TLDs out there. Unlike .org, .net lost its semantic differentiation a long time ago.
As .com buyers start to see more and more options for duplicative or defensive registrations in their shopping carts, they’re going to be less likely to grab the .net to match their .com, in my opinion.
And it’s likely to get worse.
“It’s going to continue,” Bidzos said. “We’re seeing hundreds of more new gTLDs coming, and they’re coming at the rate of many every single week. So that confusion is likely to get worse.”
New gTLD registries will be able to release all two-character strings in their zones, following an ICANN decision last week.
The ICANN board of directors voted on Thursday to instruct ICANN’s executive to
develop and implement an efficient procedure for the release of two-character domains currently required to be reserved in the New gTLD Registry Agreement
The procedure will have to take into account the advice of the Governmental Advisory Committee issued at the end of last week’s ICANN 51 meeting in Los Angeles.
But that advice merely asks that governments are informed when a registry requests the release of two-character names.
All two-character strings were initially reserved due to the potential for confusion with two-letter ccTLDs.
But the GAC decided in LA that it doesn’t really have a problem with such strings being released, with some governments noting that ccTLD second-levels such as us.com and uk.com haven’t caused a problem to date.
The board’s decision is particularly good news for dot-brand applicants that may want to run domains such as uk.google or de.bmw to service specific regions where they operate.
Registries representing over 200 new gTLDs have already filed Registry Service Evaluation Process requests for the release of some two-character strings (some including ccTLD matches, some not).
It’s not yet clear how ICANN will go about removing the two-character restriction.
It may be more efficient to offer all registries a blanket amendment to the RA rather than process each RSEP request individually as it is today.
However, because the GAC has asked for notification on a case-by-case basis, ICANN may be forced to stick to the something along the lines of the existing procedure.
ICANN has reopened the contention sets for .cam and .通販 after deciding that two String Confusion Objection panels may have been wrong to reject certain applications.
Two rulings — that .cam is confusingly similar to .com and that .通販 is confusingly similar to .shop (really) — will now head to an appeals panel for a “final” determination.
The decision was made by the ICANN board’s New gTLD Program Committee this week at the ICANN 51 public meeting in Los Angeles.
The first case being reopened for scrutiny is Verisign versus Rightside, where the original SCO panel found that .cam and .com were too similar to coexist on the internet.
But a different panelist found that the two strings were not confusingly similar in objections filed by Verisign against two other applicants — Dot Agency and AC Webconnecting.
The opposing rulings meant that Rightside’s application would have been kicked out of the .cam contention set, which hardly seems fair.
This and many other “perceived inconsistencies” led to the ICANN board being pressured to come up with some kind of appeals process, which it agreed to do in February.
Verisign, unfairly in my view, was not given the opportunity to appeal the two .cam decisions that went against it, even though they were made by the same panelist for the same reasons.
The second, altogether more peculiar, case was .shop applicant Commercial Connect versus .通販 applicant Amazon.
The panelist in that case seemed to have checked his brain at the door that day, concluding that the two strings are confusingly similar simply because 通販 means “online shopping” in Japanese.
Another panelist, in a different case also involving Commercial Connect, had found that .购物 (Chinese for “shopping”) was not confusingly similar to .shop because duh.
ICANN’s NGPC has now decided that the two controversial decisions are “not being in the best interest of the New gTLD Program and the Internet community”.
Both .cam and .通販 will now be referred to a three-person panel at the International Center for Dispute Resolution, the same body that processed the original objections, for a final determination.
ICANN’s Governmental Advisory Committee does not plan to advise against the release of two-character domain names in new gTLDs.
In fact, judging by a GAC discussion at ICANN 51 in Los Angeles yesterday, the governments of many major nations are totally cool with the idea.
Under the standard Registry Agreement for new gTLD registries, all two-character domains (any combination of letters, numbers) must not be sold or activated in the DNS.
The blanket ban was designed to avoid clashes with two-letter ccTLD codes, both existing and future.
ICANN left the door open for registries to request the release of such names, however, and many companies have formally applied to do so via the Registry Services Evaluation Process.
Some registries want all two-character domains released, others have only asked for permission to sell those strings that do not match allocated ccTLDs.
There seems to have been an underlying assumption that governments may want to protect their geographic turf. That assumption may turn out to be untrue.
Representatives from the United States, Netherlands, Spain, Denmark, Australia, Austria and Iran all said yesterday that the GAC should not issue formal advice against the the two-character proposals.
No governments opposed that apparent consensus view.
“The use of the ‘US’ two-letter country code at the second level has not presented any technical or policy issues for the United States,” US rep Suzanne Radell said.
“We, in fact, do not require any approval for the use of US two-character country codes at the second level in existing gTLDs, and do not propose to require anything for new gTLDs,” she said.
She even highlighted domains such as us.com and us.org — which are marketed by UK-based CentralNic as alternatives to the .us ccTLD — as being just fine and dandy with the US government.
It seems likely that the GAC will instead suggest to ICANN that it is the responsibility of individual governments to challenge the registries’ requests via the RSEP process.
“What we see at the moment is that ICANN is putting these RSEP requests out for public comment and it would be open to any government to use that public comment period if they did feel in some instances that there was a concern,” Australian GACer Peter Nettlefold said.
I’ve not been able to find any government comments to the relevant RSEP requests.
For example, Neustar’s .neustar, which proposes the release of all two-character strings including country codes, has yet to receive a comment from a government.
Many comments in other RSEP fora appear to be from fellow dot-brand registries that want to use two-letter codes to represent the countries where they operate.
The music industry-backed application for the new gTLD .music today suffered a humiliating defeat at the hands of a Community Priority Evaluation panel.
The Far Further (.music LLC) application scored a pitiful 3 out of 16 possible points in the evaluation, missing the required 14-point passing threshold by a country and western mile.
CPE is a way for applicants representing genuine communities to avoid an auction. If one applicant in a contention set wins a CPE, all the others must withdraw their applications.
But in this case the CPE panel went so far as to accuse the applicant of attempting to get its hands on a nice generic string by creating a new community, rather than by representing an existing one:
The Panel determined that this application refers to a proposed community construed to obtain a sought-after generic word as a gTLD. Moreover the applicant appears to be attempting to use the gTLD to organize the various groups noted in the application documentation, as opposed to applying on behalf of an already organized and cohesive community.
The application was backed by dozens of music industry trade groups and (by inference) thousands of their member associations and millions of individual members, spread over 150 countries.
But that wasn’t enough to persuade the CPE panel that “music” is even a “community” within the meaning of the ICANN new gTLD program’s Applicant Guidebook:
While the Panel acknowledges that many of the members in the proposed community share an interest in music, the AGB specifies that a “commonality of interest” is not sufficient to demonstrate the requisite awareness and recognition of a community among its members.
The panel pointed to the existence of legions of amateur musicians — estimated at 200 million — that do not identify with the community as defined in Far Further’s new gTLD application, which is restricted to the four million or so members of the application’s backers.
The panel found therefore that “there is no entity mainly dedicated to the entire community as defined by the applicant, nor does the application include reference to such an organization”.
The very fact that the Far Further application included reference to 42 trade groups, covering different facets of the music industry, seems to have counted against it. One overarching body dedicated to “music” in its entirety may have been enough to win the applicant some points.
The fact that the panel decided the community did not exist had a knock-on effect in other parts of the evaluation.
Has the community been around for a long time? No, because the community doesn’t exist. Is it a big community? No again, because the community doesn’t exist. And so on.
The only places Far Further managed to pick up points were on its registration policies, where it had promised to restrict registration to certain community members, and on community endorsement.
There are eight applicants for .music in total. One other, regular DI commenter Constantine Roussos’ DotMusic Limited, is also a Community application that is eligible for CPE.
It’s always seemed highly improbable that any .music applicant could pass CPE, but it’s looking even less likely for DotMusic after today’s result for Far Further.
.music, it seems, is heading to auction, where it is likely to fetch big bucks.