TLS says .feedback will be “UDRP-proof”, will hire lawyers to defend registrants

Top Level Spectrum plans to make its .feedback domains dirt cheap for domainers during its forthcoming Early Access Period, and is claiming that its domains will be “UDRP-proof”.
CEO Jay Westerdal told DI today that the registry will even hire lawyers to defend its registrants if and when UDRP cases arise.
The company has also introduced a new $5,000 “claims” service that is guaranteed to drive the intellectual property community nuts.
.feedback is shaping up to be one of the most fascinating new gTLD launches to date.
The company’s original plan, to sell 5,000 trademark-match domains to a single entity after its sunrise period ends has been tweaked.
Now, it will instead offer huge rebates during its Early Access Period next month, which will bring the price to registrants down from as much as $1,815 to as little as $5.
It’s called the “Free Speech Partner Program”.
To qualify for the program rebate, registrants will have to agree to stick to using TLS’s specially designated name servers, which point to a hosted feedback service managed by the registry.
An example of such a site can be seen at donaldtrump.feedback, which is among several US presidential candidate names TLS has registered to itself recently.
That commitment will be passed on if the domain ever changes hands, and a $5,000 fee will be applicable if the registrant wants to switch to their own name servers.
A registry charging a lower fee during EAP than GA is unheard of, but that’s what TLS is planning.
Rebates will not be available during the first three days of EAP, which starts January 6 at $14,020 per name. Days two and three see domains priced at $7,020 and $3,520.
From January 9 to January 18, rebates will bring the prices down to $5 per domain.
That’s a quarter of the $20 registry fee it plans to charge during general availability.
“Our plan is to sell thousands of domains before normal GA,” Westerdal said.
“It is a great opportunity for domainers to register domains that will be UDRP proof,” he said. “As free speech sites they are going to improve the world and let anyone read reviews on any subject.”
“I think they are UDRP proof,” he said. “As a registry we will hire lawyers to fight cases that arise.”
Asked to confirm that TLS would pay for lawyers to defend its registrants in UDRP cases, he said: “Hell yes we will.”
The registry plans to give trademark owners a way to avoid UDRP, however, if they’re willing to pay $5,000 for the privilege.
“Free Speech” registrants will have to agree not only to use TLS’s feedback platform, but also to allow the owners of trademarks matching their domains to more or less unilaterally seize those domains for up to two years after registration.
This “claims period” is also unprecedented in new gTLD launches. It’s described like this:

The registry will accept trademarks for a period of 2 years after the initial registration on a “Free Speech Partner Program” domains. The cost is $5,000 to have the mark validated, if the trademark is found to be the first to successfully make a claim against a domain in the program the domain will be transferred to the mark holder. The mark holder will be allowed to change name servers and is not subject to the “Free Speech Partner Program” terms of service.
Domain registrants of the “Free Speech Partner Program” agree the outcome of a validated mark by the Registry have no further claim to the domain if it is transferred to a new registrant.

If TLS is trying to design a system that will enrage the trademark community to the maximum extent possible, it’s doing a fantastic job.
It even introduced a new clause (2.9, here) to its registration agreement earlier this month, obliging registrants to point their domains to a web page that collects feedback. That means nobody will be allowed to leave their .feedback domains dark.
Are these measures justifiable disincentives, or plain old extortion? Opinion will no doubt be split along the usual lines.

.phone will be restricted after Dish gTLD auction win

The new gTLD .phone is going to be tightly restricted, after Dish DBS won the contested string at auction.
The American satellite communications firm beat Donuts to the gTLD, judging by Donuts’ withdrawal from the two-horse on Friday.
This means that if you’re not a licensed telecoms or voice-over-IP service provider, you won’t be able to register a .phone domain, at least at first.
Dish originally applied for .phone as what became known as a “closed generic” — a non-trademark, dictionary word that would nevertheless be operated as a dot-brand, with a single eligible registrant.
Due to Governmental Advisory Committee advice against such business models, Dish changed its application this September to describe .phone instead as a “controlled” gTLD.
Its application states that only Dish, its affiliates and “Qualified Applicants” will at first be able to register .phone domains.
“Qualified Applicants” basically means any company licensed to run a telecommunications service anywhere in the world. The eligibility gate appears to be the “license”.
The application says Dish will reserve the right to open up the gTLD to further classes of registrants at a later date.
While it also says that Dish will not give itself or friendly registrars any “undue preference”, the telecoms industry is suspicious.
USTelecom, the industry body representing large and small US-based telecoms companies, wrote to ICANN in November to say Dish’s volte face was “unconvincing” and its proposals “simply fail to satisfy” ICANN’s rules banning closed generics.
It said in its letter (pdf):

While Dish purports in its amended application that the .phone gTLD will be operated as a “controlled gTLD,” it is in reality an exclusive generic TLD, prone to discriminatory and subjective determinations on which entities are “Qualified Applicants,” and a discretionary reservation “to open this TLD to additional classes of registrants in the future,” who “will not be considered members.”

USTelecom says it negotiated with Dish, in an attempt to resolve its earlier formal objection against the bid, to have Dish include some reassuring Public Interest Commitments in its application, but Dish refused.
ICANN, responding to USTelecom, said that any Registry Agreement Dish signs for .phone will include the clauses that prevent it operating as a closed generic.
Now that the contention set has been settled, Dish’s next step is to proceed to contract negotiations with ICANN.

Tata’s bid for .tata gTLD scuppered by Morocco

Tata Group, the humongous Indian conglomerate, has been told its flagship application for a dot-brand gTLD has been refused.
ICANN on Friday changed the status of the application for .tata from “On Hold” to “Will Not Proceed”, a limbo state that is usually expected to lead to the application being withdrawn.
It is believed that Tata’s row with Morocco is to blame.
While Tata Group is a 150-year-old, $100 billion-a-year company, Tata is also a province of Morocco with a population of about 120,000.
Under the rules of the ICANN new gTLD program, the string “tata” is therefore a protected geographic name, for which the applicant needs to show the unequivocal support or non-objection of the relevant government.
Tata was the last applicant to pass its ICANN evaluation, when in July 2014 it finally managed to pass its Geographic Names Review on the basis of a letter from a Moroccan official.
However, in September last year the Moroccan’s government’s digital economy minister denied that the letter indicated support for .tata.
This February, ICANN threw Tata back into a Geographic Names Review, where the onus was on the company to prove that it really did have support.
That support has evidently not been forthcoming.
Morocco has indicated in letters to ICANN that it may want the .tata gTLD itself in future.
Tata unit Tata Motors has already been delegated the dot-brand gTLD .tatamotors.

Porn firm wins .cam after years of objections

The controversial new gTLD .cam has been won at auction by Dutch porn site operator AC Webconnecting, putting an end to over two years of back-and-forth objections.
Rival applicants Rightside and Famous Four Media both withdrew their applications earlier this week.
The contest for .cam was marked by several objections and appeals.
In 2013, Verisign filed and lost String Confusion Objections against AC Webconnecting and Famous Four, but won its near-identical objection against Rightside.
Verisign had claimed that .cam and .com are so similar-looking that confusion among internet users is bound to arise.
Because the SCO panels in the three cases returned differing opinions, Rightside was one of two applicants given the right to appeal by ICANN in October 2014.
I never quite understood why Verisign wasn’t also given the right to appeal.
Rightside won the right to stay in the .cam contention set almost a year later.
Despite all that effort, it did not prevail in the resulting auction.
Separately, back in 2013, AC Webconnecting filed and lost Legal Rights Objections against its two rivals, based on a “.cam” trademark it acquired purely for the purpose of fighting off new gTLD competitors.
I’d be lying if I said I knew a lot about the soon-to-be registry.
Based in Rotterdam, its web site comes across as a wholly safe-for-work web design firm.
However, it seems to be mainly in the business of operating scores, if not hundreds, of webcam-based porn sites.
Its application for .cam states that it will be for everyone with an interest in photography, however.
When it goes live, its most direct competitor is likely to be Famous Four’s .webcam, which already has an 18-month and 70,000-domain head start.
It remains to be seen whether its clear similarity to .com will in fact cause significant confusion.

Radiohead backs .music community bid

Ed O’Brien, guitarist with the band Radiohead, has become the latest musician to throw his support behind DotMusic’s community-based application for the new gTLD .music.
In a letter to ICANN today (pdf), O’Brien said that if DotMusic loses its ongoing Community Priority Evaluation, it will “be setting back the world’s chances of a Fair Trade Music Industry by many years”.
“I challenge The Internet Corporation for Assigned Names and Numbers views that the global music community to which I belong does not exist,” he wrote.
He’s arguably the highest-profile musician to support DotMusic to date. Radiohead have sold over 30 million records and a few years ago O’Brien was ranked by Rolling Stone as the 59th greatest guitarist of all time.
The phrase “Fair Trade Music Industry” appears to have been coined last week at TechCrunch Disrupt by Grammy-nominated musician Imogen Heap, another one of DotMusic’s celebrity supporters.
It refers to the notion that artists should be fairly compensated for their work, opposing services such as Spotify, which reportedly pays artists less than a tenth of a cent every time one of their songs is played.
Both Heap and Radiohead are noted for their innovative uses of technology in their music (for example, listen to Radiohead’s incredible 1997 album OK Computer, bootlegs of which are available to stream for free on YouTube).
Radiohead is also known for its love-hate relationship with internet-based music business models.
In 2007, Radiohead released a new album for free on its web site, allowing fans to set their own price. But in 2013, it pulled its back catalog from Spotify, with lead singer Thom Yorke calling the service “the last desperate fart of a dying corpse”.
Its music is back on Spotify now.
But you can see why the band would support DotMusic’s application for .music, which proposes a number of novel rights protection mechanisms covering not just trademarks, but also copyright.
One interesting proposal is to ban any domain name from .music if a matching domain in another TLD has received over 10,000 copyright infringement notices from a big music industry body. This is to prevent TLD “hopping” affecting .music.
So, for example, if thepiratebay.com had received 10,000 notices, thepiratebay.music would be permanently blocked from registration.
The company is proposing a somewhat restricted namespace too, where only “community members” are allowed to register domains.
But prospective registrants merely need to self-identify as a member of one of the community’s dozens of subsets — which includes “fans” and “bloggers” — in order to register.
Parking will be prohibited, however, which would cut down on domain investor speculation.
Quite how .music will enhance the move for “fair trade” for artists is not entirely clear from O’Brien’s letter. After .music launches, there will still be hundreds of other TLDs that do not have DotMusic’s rules in place.
It’s also unlikely that the Economist Intelligence Unit, which is currently handling the CPE, will even see O’Brien’s letter.
ICANN told DotMusic (pdf) recently that the EIU “may not consider” any support letters received after October 13, which was two months after the official deadline for letters to be submitted.
DotMusic has letters of support — mostly the same letter with a different signature — from literally hundreds of musicians, trade groups, producers and publishers.
CEO Constantine Roussos told DI last week that it has more support letters than all the other “Community” gTLD applicants combined.
He said he’s confident that DotMusic’s CPE will be successful, citing positive precedent set by EIU panels in .osaka, .hotel and .radio CPE cases.
But the closest precedent we have so far is the Far Further application for .music, which comprehensively lost its CPE a year ago, scoring just three points out of the available 16, well short of the 14-point passing score.
There are differences between the applications, but Far Further’s CPE panel told it that there was no such thing as “the music community”, which sets a pretty high bar for DotMusic to leap.
If DotMusic wins its CPE, the remaining seven competing applications for the string get kicked out of the program. If it loses, it goes to an auction it has little chance of winning.

Twitter and Justin Timberlake targeted by This.sucks

This.sucks, a company with close ties to .sucks registry Vox Populi, has started registering domain names matching famous brands to itself.
Twitter, along with singer Justin Timberlake, software maker Adobe and investment bank Goldman Sachs all saw their matching .sucks domains registered by This.sucks on Friday, according to the .sucks zone file and Whois queries.
The domains twitter.sucks, goldmansachs.sucks, justintimberlake.sucks and adobe.sucks currently resolve in browsers, but only to a password-protected web site.
New York-based This.sucks says its service is in beta. It plans to give 10,000 .sucks domains away for free, and to sell them for as little as $12 per year. Its business model has not been revealed.
That’s a deep discount from their regular $250 suggested retail price, which rises to $2,500 for domains matching famous brands.
Technically, the company should have just paid around $10,000 for the four brand-matching domains it has just registered.
But it is broadly suspected that This.sucks shares ownership with Vox Populi, the .sucks registry operator, which would make this a case of the right hand paying the left.
As we uncovered in October, Vox Populi originally hosted This.sucks’ web sites and the CEO of Momentous, which founded Vox Pop, paid for its web site to be developed.
The two companies also share a physical address and a Cayman Islands lawyer.
Vox Pop has denied any involvement in This.sucks, saying it’s just another customer.
It will be interesting to see how long it takes for one of the four affected brands to file a UDRP or URS complaint on these new domains.
As far as I can tell, the .sucks namespace currently has an unblemished UDRP record.
Unlike rival Top Level Spectrum, which runs .feedback, neither Vox Pop nor This.sucks has revealed any plans to use brands belonging to third parties as part of their services.
TLS has said it plans to sell 5,000 branded .feedback domains to a third party after its sunrise period ends next month.
It has already registered fox.feedback to itself as one of its special 100-domain pre-sunrise registry allowance.
Since we last reported on .feedback a month ago, the registry appears to have also registered the names of all the current US presidential candidates — such as donaldtrump.feedback and hillaryclinton.feedback — to itself.
The sites are all live, as is santaclaus.feedback, which seeks commentary on the “fictional” character.

Foot-dragging Amazon has bumper crop of new gTLDs

Amazon Registry Services took possession of 17 new gTLDs at the weekend.
The would-be portfolio registry had .author, .book, .bot, .buy, .call, .circle, .fast, .got, .jot, .joy, .like, .pin, .read, .room, .safe, .smile and .zero delegated to the DNS root zone.
Amazon seems to have waited until the last possible moment to have the strings delegated.
It signed its registry agreements — which state the TLDs must be delegated with a year — in mid-December 2014.
Don’t plan on being able to register domains in any of these gTLDs. You may be disappointed.
All of the strings were originally applied for as what became known as “closed generics”, in which Amazon would have been the only permitted registrant.
It recanted this proposed policy in early 2014, formally amending its applications to avoid the Governmental Advisory Committee’s anti-closed-generic advice.
Its registry contracts do not have the standard dot-brand carve-outs.
However, the latest versions of its applications strongly suggest that registrant eligibility is going to be pretty tightly controlled.
The applications state: “The mission of the <.TLD> registry is: To provide a unique and dedicated platform while simultaneously protecting the integrity of Amazon’s brand and reputation.”
They go on to say:

Amazon intends to initially provision a relatively small number of domains in the .CIRCLE registry to support the goals of the TLD… Applications from eligible requestors for domains in the .CIRCLE registry will be considered by Amazon’s Intellectual Property group on a first come first served basis and allocated in line with the goals of the TLD.

They state “domains in our registry will be registered by Amazon and eligible trusted third parties”.
Amazon has not yet published its TLD start-up information, which may provide more clarity on how the company intends to handle these strings.
I suspect we’ll be looking at a policy that amounts to a workaround of the closed-generic ban.
The registry seems to be planning to run its registry from AmazonRegistry.com.

Schilling: registries could wind-down unprofitable gTLDs

New gTLD portfolio registries may one day decide to wind down some of their gTLDs if they fail to reach profitability.
That’s according to Uniregistry CEO Frank Schilling, who told DI today that registries may “sunset” under-performing TLDs.
His comments came in response to our post earlier today about registries going out of business involuntarily due to lack of sales.
But he’s referring to registries managing large numbers of strings, winding down the unprofitable ones in a controlled manner.
“I can’t see Uniregistry doing that today, but if in round two we get 100 strings that all kill it and we have some round one stuff that sucks, yes,” he said in an email. “I would consider raising prices to get the string profitable or sunset the string.”
“That said,” he added, “that’s 5-8 years out [and] by then even the slowest should be profitable.”

ICANN security advisor predicts “hundreds” of new gTLDs will “go dark”

A security company led by a member of ICANN’s top security committee reckons that “hundreds” of new gTLDs are set to fail, leading to web sites “going dark”.
Internet Identity, which provides threat data services, made the prediction in a press release this week.
IID’s CTO, quoted in the release, is Rod Rasmussen. He’s a leading member of the Anti-Phishing Working Group, as well as a member of ICANN’s influential Security and Stability Advisory Committee.
He has a dim view of new gTLDs:

Most new gTLDs have failed to take off and many have already been riddled with so many fraudulent and junk registrations that they are being blocked wholesale. This will eventually cause ripple effects on the entire domain registration ecosystem, including consolidation and mass consumer confusion as unprofitable TLDs are dropped by their sponsoring registries.

The press release acknowledges that ICANN has an Emergency Back-End Registry Operator (EBERO) program, which will keep failing gTLDs alive for up to three years after the original registry operator goes out of business.
But it continues:

questions abound as to who would risk an investment in poorly performing TLDs, especially as they start to number in the hundreds. “That’s why eventually some are going to just plain go dark,” added Rasmussen.

The prediction is for “2017 and beyond”. Given the existence of the EBERO, we’re probably looking at 2020 before IID’s claim can be tested.
It’s a bit of a strange prediction to come out of a security company.
The whole point of EBERO is to make sure domain names do not go dark, giving either the registry the chance to sell on the gTLD or the registrants a three-year heads-up that they need to migrate to a different TLD.
It would be a bit like being told that there’s a horrible bit of malware that is set to brick your computer, but that you’ll be fine if you change your anti-virus provider in the next three years.
I could live with that kind of security threat, personally.
But what are the chances of hundreds of live, non-dot-brand going fully post-EBERO dead in the next few years?
I’d say evidence to date shows the risk may be over-stated. It may happen to a small number of TLDs, but to “hundreds”?
We’ve already seen new gTLD registries essentially fail, and they’ve been taken over by others even when they’re by definition not profitable.
Notably, .hiv — which has a contractual agreement with ICANN to not turn a profit — failed and was nevertheless acquired by Uniregistry.
We also see registries including Afilias and Donuts actively searching for failing gTLDs to acquire.

It’s official: new gTLDs didn’t kill anyone

The introduction of new gTLDs posed no risk to human life.
That’s the conclusion of JAS Advisors, the consulting company that has been working with ICANN on the issue of DNS name collisions.
It is final report “Mitigating the Risk of DNS Namespace Collisions”, published last night, JAS described the response to the “controlled interruption” mechanism it designed as “annoyed but understanding and generally positive”.
New text added since the July first draft says: “ICANN has received fewer than 30 reports of disruptive collisions since the first delegation in October of 2013. None of these reports have reached the threshold of presenting a danger to human life.”
That’s a reference to Verisign’s June 2013 claim that name collisions could disrupt “life-supporting” systems such as those used by emergency response services.
Names collisions, you will recall, are scenarios in which a newly delegated TLD matches a string that it is already used widely on internal networks.
Such scenarios could (and have) led to problems such as system failure and DNS queries leaking on to the internet.
The applied-for gTLDs .corp and .home have been effectively banned, due to the vast numbers of organizations already using them.
All other gTLDs were obliged, following JAS recommendations, to redirect all non-existent domains to 127.0.53.53, an IP address chosen to put network administrators in mind of port 53, which is used by the DNS protocol.
As we reported a little over a year ago, many administrators responded swearily to some of the first collisions.
JAS says in its final report:

Over the past year, JAS has monitored technical support/discussion fora in search of posts related to controlled interruption and DNS namespace collisions. As expected, controlled interruption caused some instances of limited operational issues as collision circumstances were encountered with new gTLD delegations. While some system administrators expressed frustration at the difficulties, overall it appears that controlled interruption in many cases is having the hoped-for outcome. Additionally, in private communication with a number of firms impacted by controlled interruption, JAS would characterize the overall response as “annoyed but understanding and generally positive” – some even expressed appreciation as issues unknown to them were brought to their attention.

There are a number of other substantial additions to the report, largely focusing on types of use cases JAS believes are responsible for most name collision traffic.
Oftentimes, such as the random 10-character domains Google’s Chrome browser uses for configuration purposes, the collision has no ill effect. In other cases, the local system administrators were forced to remedy their software to avoid the collision.
The report also reveals that the domain name corp.com, which is owned by long-time ICANN volunteer Mikey O’Connor, receives a “staggering” 30 DNS queries every second.
That works out to almost a billion (946,728,000) queries per year, coming when a misconfigured system or inexperienced user attempts to visit a .corp domain name.