Slow start for .christmas with under 500 sales
Uniregistry’s latest new gTLDs .christmas and .blackfriday seem to have stumbled out of the gates, both amassing fewer than 500 registrations in their first full day of general availability.
In today’s zone files, .christmas has 501 names and .blackfriday has 445. Those numbers include dozens of sunrise registrations. They both went to GA on Tuesday afternoon UTC.
As you might expect, the .christmas zone comprises a mix of brands and generic words and phrases related to retail and travel. It’s a similar state of affairs in .blackfriday.
What there do not appear to be are large numbers of product categories registered, suggesting that domainers feel that the new gTLDs fail Uniregistry CEO Frank Schilling’s own Toilet Paper Test.
That’s where one judges the potential popularity of a TLD by putting the string “toiletpaper” at the second level.
Domainer Mike Berkens appears to have picked up a handful of decent-looking names, including santatracker.christmas (NORAD’s Santa tracker got 19.58 million unique visitors last year) and whatiwantfor.christmas.
Schilling himself paid $90,000 — half the price of a new gTLD application fee — for blackfridaysales.com back in 2010. In November 2009, Kevin Ham’s blackfriday.com purportedly took 18 million visitors.
Neither Uniregistry TLD appears to be available currently at Go Daddy, despite the two companies’ reported distribution deal.
.christmas and .blackfriday are notable because they’re the first TLDs to launch that are tied to specific calendar dates. Those dates are of course several months away.
I have a feeling that it may prove tough to build up sustainable buzz for these TLDs.
Even if they’re used by big brands in marketing campaigns this year, which is of course by no means assured, it’s still going to take another year to figure out whether they’ve captured the imagination of their target markets.
In an industry of long plays, these could be two of the longer ones.
Pinyin to beat IDN? .wang ready to overtake .在线
The .wang gTLD has seen great success, relatively, in its first week of general availability, crossing the 30,000 mark yesterday and entering the top 10 new gTLDs by registration volume.
At its current rate of growth, the Zodiac Holdings domain is going to overtake .在线, the highest-ranking Chinese gTLD so far, this week.
.wang went to GA June 30. After its initial spike, it’s added one to two thousand names per day and, with 31,011 names today, currently sits at 9th place in the new gTLD program’s league table.
That’s a whisker behind TLD Registry’s .在线 (“.online”), which had a strong start when it launched at the end of April but has since plateaued at around 33,000 names, adding just a handful each day.
A skim through the zone files reveals that the vast majority of the names in .wang appear to be, like .wang itself, Pinyin — the official Latin-script transliterations of Chinese-script words.
.wang, which would be “网” in Chinese script, means “net”.
To pluck a couple of names from the zone at random, I see tanpan.wang, which could mean something like “negotiation.net” and xingshi.wang, which may or may not mean “shape.net”.
I suspect that many of the registered domains are personal names rather than dictionary words. Wang is a popular surname in China.
The vast majority of the names also appear to be registered via China-based registrars, some of which are promoting the TLD strongly on their home pages.
There certainly appears to be a lot of domainer activity in .wang, but I haven’t seen anything yet to suggest a massive orchestrated effort that would throw out the numbers considerably.
Either way, I find it fascinating that a Latin transliteration of a Chinese word seems set to out-perform the actual Chinese IDNs currently on the market.
Almost half of registrars “deficient” in compliance audit
Almost half of accredited domain name registrars were found “deficient” during a recent ICANN compliance survey.
Results of an audit published today show that 146 of 322 registrars (45%) picked at random for the September 2013 to May 2014 study had to carry out some form of remediation in order to comply with their contracts.
The report comes at the end of the second year of ICANN’s audit program, which aims to bring all accredited registrars and gTLD registries into compliance over three years.
The deficiencies noted at 146 registrars cover areas ranging from compliance with ICANN consensus policies to the availability of Whois services over the web and port 43.
In almost every instance the numbers were down on last year.
For example, ICANN documented 86 registrars who could not initially show compliance with requirements on the retention of registrant data, down from 105 a year ago.
Only 15 registrars of the 322 (4.6%) flunked the audit and will be re-tested. The others were all able to bring their systems into line with ICANN’s requirements during the course of the audit.
Three registrars were terminated as a result of deficiencies identified during this phase of the program.
The full report, along with the list of participating registrars, can be found here.
ICANN puts porn gTLDs on hold for no good reason?
In a decision that seems to have come out of nowhere, ICANN has effectively put bids for three porn-themed new gTLDs on hold.
In a June 21 meeting, the board’s New gTLD Program Committee discussed .adult, .sex and .porn, calling them “sensitive strings”.
While it passed no resolution, I understand that ICANN legal staff is delaying the signing of contracts for at least one of these gTLDs while the NGPC carries out its talks.
It’s a surprising development, given that the three strings are not subject to any Governmental Advisory Committee advice, are not “Community” applications, and have not been formally objected to by anyone.
The report from the NGPC meeting acknowledges the lack of a GAC basis for giving the strings special treatment (emphasis added):
The Committee engaged in a discussion concerning applications for several adult-oriented strings in the current round of the New gTLD Program, including .ADULT, .PORN, and .SEX. The applications propose to serve the same sector as the .XXX sponsored TLD. Staff noted that the applications were not the subject of GAC advice, or any special safeguards, other the safeguards that are applicable to all new gTLDs. The Committee considered how the safeguards in the new gTLD Program compare to the safeguards that were included in the .XXX Registry Agreement. The Committee requested staff prepare additional briefing materials, and agreed to discuss the matter further at a subsequent meeting.
This begs the question: why is ICANN giving .porn et al special treatment?
What’s the basis for suggesting that these three strings should be subject to the same safeguards that were applied to .xxx, which was approved under the 2003 sponsored gTLD round?
.porn, .sex and .adult were were applied for under the 2012 new gTLD program, which has an expectation of predictability and uniformity of treatment as one of its founding principles.
Who decided that .sex is “sensitive” while .sexy is not? On what basis?
Is it because, as the NGPC report suggests, that the three proposed gTLDs “serve the same sector” as .xxx?
That wouldn’t make any sense either.
Doesn’t .vacations, a contracted 2012-round gTLD, serve the same sector as .travel, a 2003-round sponsored gTLD? Why wasn’t .vacations subject to additional oversight?
Is it rather the case that the NGPC is concerned that ICM Registry, operator of .xxx, has applied for these three porn strings and proposes to grandfather existing .xxx registrants?
That also wouldn’t make any sense.
.sex has also been applied for by Internet Marketing Solutions, a company with no connection to .xxx or to the 2003 sponsored gTLD round. Why should this company’s application be subject to additional oversight?
And why didn’t .career, which “serves the same sector” as the sponsored-round gTLD .jobs and was applied for by the same guys who run .jobs, get this additional scrutiny before it signed its contract?
It all looks worryingly arbitrary to me.
US winemakers rebel against their government
Groups representing thousands of US winemakers have come out against .wine and .vin, bringing their government’s position on the two proposed new gTLDs into question.
Seven regional associations, representing close to 2,000 wineries, issued a statement last night raising “strong objections” to the gTLDs with “non-existent to grossly insufficient safeguards”.
The joint statement says:
If granted to unscrupulous bidders, second-level domain names such as napavalley.wine or wallawalla.wine could be held in perpetuity by a company or individual that has never seen a vineyard, cultivated fine wine grapes or made a single bottle of wine.
It’s the first mass objection from US winemakers, but they join colleagues from France, Spain and other European Union nations in their opposition to a .wine that does not respect geographic indicators (GIs).
It also makes the US delegation to ICANN’s Governmental Advisory Committee look rather out of touch with the very companies it professes to be looking out for.
At the ICANN 50 meeting in London last week, US rep Suzanne Radell told the GAC:
The three U.S. wineries that our colleagues in Europe have cited as being privy to the exchanges between the European wine industries and the applicants are, in fact, just three U.S. wineries. If I may emphasize, the United States has thousands and thousands of wineries who are quite interested in this matter and do not support the European model of GI protection. So let’s just please put that to bed.
The US winery groups now objecting comprise almost 2,000 wineries. According to Wikipedia, the US has fewer than 3,000 wineries.
We’re looking at a two-thirds majority objection from the US wine-making industry here.
“The coalition of American quality wine regions representing nearly 2,000 U.S. wineries clearly contradicts Radell’s testimony in London on June 22,” the groups said.
The groups also have Californian congresspeople Anna Eshoo and Mike Thompson on their side. As we reported yesterday, Eshoo has already written to ICANN to urge it to kill off .wine.
The big questions are: will this be enough to change the position the US takes to the GAC in future, and will that help the GAC find consensus on anti-.wine advice?
Australia and Canada have also been vocal opponents of the European demands in the past. They’d need to change their minds too, in order for the GAC to find a new consensus.
Without a GAC consensus, the .wine and .vin applicants have little to worry about.
Democrat congressman sides with France on .wine
US Representative Anna Eshoo has written to ICANN’s top brass to express “deep concerns” about the .wine and .vin new gTLDs and urge that they be permanently killed off.
In a letter (pdf) to CEO Fadi Chehade, Eshoo wrote:
it’s my understanding that the .wine and .vin gTLDs have been met with fierce opposition from the wine industry, both here in the US and around the world. Given these concerns, coupled with the complexities of reaching agreement on Geographic Indications (GIs), I urge you to advocate for the .wine and .vin gTLDs to be permanently withdrawn from consideration.
Eshoo, a Democrat, is breaking rank with the official position of the Obama administration on this, which is that no special treatment is warranted for the two wine-related gTLDs.
Europe, on the other hand, is vehemently opposed to the introduction of either without strong protection for GIs.
At ICANN 50 in London last week the European Commission and France led the charge against approval of the gTLDs, with the Commission even floating the idea of legal action at one point.
France, meanwhile, seems ready to throw ICANN’s ambitions for independence under a bus in order to get what it wants.
Eshoo is ranking member of the House Communications and Technology Subcommittee, which recently passed the DOT-COM Act over her protestations that it was “embarrassing”.
She also represents the Silicon Valley area of northern California, which is known for its wineries.
While a handful of US winemakers do have a decidedly European attitude to GI protections, the US Governmental Advisory Committee delegation last week said that only a few out of “thousands” agree with France.
.london predicts 50,000 landrush names
Two months into its combined sunrise/landrush period Dot London Domains estimates it will end July with 50,000 applied-for names.
A “projection based on current applications”, the number doesn’t say a heck of a lot about how many names have actually been applied for since the TLD opened for applications on April 29.
It could mean that 33,000 names, given that we’re two-thirds of the way through the launch phase. Alternatively, the registry could be predicting the kind of last-minute rush common to sunrise periods before 2014.
The number doesn’t say much about .london’s eventual number of names under management, given that there’s likely to be multiple applications for the same names.
If it were to sell 50,000 names, that would make it the fifth-largest new gTLD, based on today’s numbers.
The three-month launch phase combines the sunrise and landrush, with trademark owners listed in the Trademark Clearinghouse getting first priority.
Registrants based in London applying for a non-TMCH business name get second dibs, followed by Londoners generally and then anyone anywhere in the world.
Clashing applications will see the names going to auction. Sunrise applicants will not have to compete at auction with non-sunrise applicants, of course.
Back-end registry provider Minds + Machines is being promoted heavily as the primary registrar. It’s selling the names for £30 ($51) per year and pushing sunrise applicants to Com Laude.
1&1, 123-reg, GoDaddy, Fasthosts and CentralNic, which all have dedicated .london pages or sites, are also being promoted by M+M as partner registrars.
The cheapest deal of those registrars appears to be at FastHosts, which is selling at £24.99 ($42.85).
The price of .bar was $100,000 to a school
Wondering how the new gTLD registry Punto 2012 managed to get government approval for .bar, even though it’s a protected geographic term in Montenegro under ICANN rules?
At least part of the deal seems to involve a 10-year, $100,000 commitment to fund a school in the tiny Montenegrin city of Bar, judging by a press release today.
The registry will pay $10,000 a year to the school for the duration of its 10-year registry agreement.
It’s a stroke of good fortune for the city. Whilst not a capital city, it’s also a ISO-designated administrative region of the country and therefore protected by the ICANN Applicant Guidebook.
Punto 2012 intends to reserve a few names for the city, and said it hopes residents will use .bar — intended to represent drinking establishments — as a city TLD also.
With a little over 17,000 inhabitants, Bar is likely going to be have one of the smaller city TLDs, and I expect most registrations will in fact come from bars elsewhere in the world.
In related news, as of last Friday there’s only one new gTLD application of the original 1,930 still under ICANN evaluation and it’s .tata, the dot-brand for a massive Indian conglomerate that is also the name of a province in Morocco. Coincidence? Probably not.
Bieber plug has no impact on .tattoo sales
Justin Bieber used his extensive social media channels to plug a .tattoo domain name to his bazillions of “beliebers” last week, but so far the plug has had no impact on sales of the gTLD.
The pop singer, beloved of 11-year-old girls worldwide, tweeted and Facebooked about the domain joker.tattoo, which leads visitors to his Tumblr blog.
A Facebook update reading simply “My Tumblr is http://joker.tattoo” has been “liked” over 230,000 times and shared almost 2,500 times by the over 70 million people following him on the platform.
On Twitter, where Bieber has 52.6 million followers, his identical tweet was retweeted over 50,000 times and favorited close to 60,000 times.
My Tumblr is http://t.co/PBP0ceJXeF ♛
— Justin Bieber (@justinbieber) June 27, 2014
The “news” was even picked up by MTV, which gently ribbed the musician for apparently (don’t ask me, I’m 37) not understanding that Tumblr isn’t just for “selfies”.
But the widespread publicity for a .tattoo name had no impact whatsoever on .tattoo sales, judging by zone files.
The Uniregistry TLD hasn’t grown by more than one name per day since Bieber’s tweet.
One June 27 the .tattoo zone file had 6,312 names in it, today it has 6,316.
The joker.tattoo domain — apparently chosen because Bieber has a tattoo of a joker — is registered to one of the founders of RockLive, a San Francisco selfie-oriented app start-up funded in part by Bieber.
The domain redirects to a Tumblr third-level subdomain, so there’s no visibility for the new gTLD in browser address bars.
There’s also the issue that most of Bieber’s fans are probably too young to own a credit card, which is a prerequisite for buying a domain name.
Unanimous support for new ICANN appeals process
The Generic Names Supporting Organization has issued an “unprecedented” statement of “unanimous” support for a new way for ICANN community members to appeal ICANN decisions.
All seven constituency groups signed onto a statement that was read by representatives of registries, non-commercial users and intellectual property interests at the ICANN 50 public forum last week.
“It only took us 50 meetings, but I think the rarity of what you’re witnessing this afternoon sends a very strong message about our views,” the Registries Stakeholder Group’s Keith Drazek said.
This is the meat of the demand:
The entire GNSO joins together today calling for the Board to support community creation of an independent accountability mechanism that provides meaningful review and adequate redress for those harmed by ICANN action or inaction in contravention of an agreed upon compact with the community.
Rafik Dammak of the Non-Commercial Users Constituency added that the creation of such a mechanism is “a necessary and integral element of the IANA stewardship transition.”
“The Board’s decisions must be open to challenge and the Board cannot be in a position of reviewing and certifying its own decisions,” he said.
“We need an independent accountability structure that holds the ICANN Board, Staff, and various stakeholder groups accountable under ICANN’s governing documents, serves as an ultimate review of Board/Staff decisions,” said Kristina Rosette of the Intellectual Property Constituency.
What they’re basically looking for is a third way to appeal ICANN decisions beyond the existing Independent Review Process and Request for Reconsideration mechanisms.
IRP is considered too time-consuming and expensive for anyone other than well-funded commercial stakeholders. It cost ICM Registry millions in legal fees to win its IRP in 2010.
RfR, meanwhile, sees the ICANN board review its own decisions, and is only successful (in 15 years it’s only happened once, a week ago) when a requester can bring new evidence to the table.
What the GNSO seems to be looking for is a third way — independent review of ICANN decisions that doesn’t cost a bomb and can be used to reexamine decisions on the merits.
In many ways the demand represents the low-hanging fruit of the amorphous “accountability” discussion that took place at length at the London meeting last week.
ICANN accountability is being examined simultaneously with the proposed transition of the IANA stewardship functions from the US Department of Commerce to a yet-undefined mechanism.
There seems to be broad community consensus that the transition should be linked to improvements in accountability.
During the “constituency day” sessions on Tuesday, during which the ICANN board visits in turn with each GNSO constituency, accountability was the theme common to each and every session.
Time and again, CEO Fadi Chehade pushed the constituency he was addressing to provide some specifics.
“What is accountability and how accountable are we today?” he asked the RySG. “Who are we accountable to for what? We need to get precise before you ask us to answer a question that says when you finish accountability, then you can move to the transition.”
The GNSO statement two days later, which still needs fleshing out with details, appears to be the first step toward providing the precision Chehade wants.
Chehade said multiple times that the accountability review and the IANA transition discussions are “interrelated” but not “interdependent.”
If one were dependent on the other, it would be easier for opponents to stonewall the IANA transition by delaying the accountability review, he said.
“There are people in this community would like the transition from the US government to never happen,” he told the RySG. “They won’t admit it, but there are several, in this room even, who want this to never happen.”
He later told the NCUC that these bogeymen were “not in this room”, highlighting perhaps his belief that one or more gTLD registries is preparing to throw a spanner in the works.
Suspicion immediately fell on Verisign, forcing Drazek to issue a separate statement at the public forum on Thursday denying that the company (his employer) opposes the transition:
VeriSign supports NTIA’s March 14th, 2014 announcement. VeriSign supports NTIA’s four key principles. VeriSign Supports the bottom-up multistakeholder process that is now under way and that we have already been very much engaged. VeriSign supports the target date of September 2015 for transition. We support these things provided the multistakeholder community recommendations for ICANN’s accountability reforms are accepted by NTIA before the final transition, and sufficiently implemented by ICANN subject to measurable deliverables.
It’s not much of a denial, really, more of a clarification of where Verisign stands and confirmation that it wants, as Chehade alluded to, accountability reform prior to the IANA transition.
In my view, accountability is the more important of these two threads.
The Department of Commerce doesn’t actually do much in terms of its hands-on role as steward of the IANA functions as they related to domain names. It merely checks that ICANN’s proper procedures have been followed before signing off on DNS root zone changes.
If sanity prevails in the ICANN community’s transition discussions (and I have no reason to believe it will) whatever replaces the US should be similarly mute and invisible.
However, Commerce’s arguably more important role has been to act as a constant Sword of Damocles, a threat that ICANN could lose its IANA powers if it goes rogue and starts acting (in the US government’s view) against the best interests of the internet community.
That’s a very crude accountability mechanism.
What ICANN needs in future is not a direct replacement of that existential threat, but a mechanism of accessible, independent third-party review that will give the ICANN community and internet users everywhere confidence that ICANN isn’t a loose cannon with its hand on the internet’s tiller.
Recent Comments