The legacy gTLDs .cat, .pro and .travel will all be subject to the Uniform Rapid Suspension policy from now on.
Earlier this week, ICANN approved the new Registry Agreements, which are based on the new gTLD RA and include URS, for all three.
URS is an anti-cybersquatting policy similar to UDRP. It’s faster and cheaper than UDRP but has a higher burden of proof and only allows domains to be suspended rather than transferred.
The inclusion of the policy in pre-2012 gTLDs caused a small scandal when it was revealed a few months ago.
Critics, particularly the Internet Commerce Association, said that URS (unlike UDRP) is not a Consensus Policy and therefore should not be forced on registries.
ICANN responded that adding URS to the new contracts came about in bilateral negotiations with the registries.
The board said in its new resolutions this week:
the Board’s approval of the Renewal Registry Agreement is not a move to make the URS mandatory for any legacy TLDs, and it would be inappropriate to do so. In the case of .CAT, inclusion of the URS was developed as part of the proposal in bilateral negotiations between the Registry Operator and ICANN.
The concern for ICA and others is that URS may one day be forced into the .com RA, putting domainer portfolios at increased risk.
Should the Uniform Rapid Suspension process spread from new gTLDs to incumbent gTLDs, possibly including .com?
That’s been the subject of some strong disagreements during the opening weekend of ICANN 53, which formally kicks off in Buenos Aires today.
During sessions of the Generic Names Supporting Organization and the ICANN board and staff, ICANN was accused of trying to circumvent policy-making processes by forcing URS into the .travel, .pro and .cat registry agreements, which are up for renewal.
ICANN executives denied doing any such thing, saying the three registries volunteered to have URS included in their new contracts, which are modeled on the standard new gTLD Registry Agreement.
“It’s just something we’ve suggested and they’ve taken up,” said Cyrus Namazi, ICANN’s vice president of domain name services.
If a registry wants to increase the number of rights protection mechanisms in its gTLD, why not let them, ICANN execs asked, pointing out that loads of new gTLDs have implemented extra RPMs voluntarily.
ICANN admits that it stands to benefit from operational efficiencies when its registry agreements are more uniform.
Opponents pointed out that there’s a difference between Donuts, say, having its bespoke, voluntary Domain Protected Marks List, and bilaterally putting the URS into an enforceable ICANN contract.
URS is not a formal Consensus Policy, they say, unlike UDRP. Consensus Policies apply to all gTLDs, whereas URS was created by ICANN for new gTLDs alone.
Arguably leading the fight against URS osmosis is Phil Corwin, counsel for Internet Commerce Association, which doesn’t want its clients’ vast portfolios of .com domains subject to URS.
He maintained over the weekend that his beef was with the process through which URS was making its way into proposed legacy gTLD contracts.
It shouldn’t be forced upon legacy gTLDs without a Consensus Policy, he said.
While the GNSO, ICANN staff and board spent about an hour talking about “process” over the weekend, it was left to director Chris Disspain to point out that that was basically a smokescreen for an argument about whether the URS should be used in other gTLDs.
He’s right, but the GNSO is split on this issue in unusual ways.
Corwin enjoys the support of the Business Constituency, of which he is a member, in terms of his process criticisms if not his criticisms of RPMs more generally.
ICA does also have backing from some registrars (which bear the support costs of dealing with customers affected by URS), from the pro-registrant Non-Commercial Stakeholders Group, and from groups such as the Electronic Frontier Foundation.
The Intellectual Property Constituency thinks that the process is just fine — .travel et al can sign up to URS if they want to.
While the registries have not yet put forward a joint position, the IPC’s view has been more or less echoed by Donuts, which owns the largest portfolio of new gTLDs.
The registries behind .pro and .cat have agreed to new ICANN contracts with changes that, among other things, would bring the Uniform Rapid Suspension policy to the two gTLDs.
Both gTLD Registry Agreements expire this year. Proposed replacement contracts, based heavily on the base New gTLD Registry Agreement, have been published by ICANN for public comment.
They’re the second and third pre-2012 gTLDs to agree to use URS, which gives trademark owners a simpler, cheaper way to have infringing domains yanked.
Two weeks ago, .travel agreed to the same changes, which drew criticisms from the organization that represents big domain investors.
Phil Corwin of the Internet Commerce Association is worried that ICANN is trying to make URS a de facto consensus policy and thereby bring it to .com, which is still where most domainers have most of their assets.
Following DI’s report about .travel, Corwin wrote last week:
this proposed Registry Agreement (RA) contains a provision through which staff is trying to preempt community discussion and decide a major policy issue through a contract with a private party. And that very big issue is whether Uniform Rapid Suspension (URS) should be a consensus policy applicable to all gTLDs, including incumbents like .Com and .Net.
ICANN needs to hear from the global Internet community, in significant volume, that imposing the URS on an incumbent gTLD is unacceptable because it would mean that ICANN staff, not the community, is determining that URS should be a consensus policy and thereby undermining the entire bottom-up policy process. Domain suspensions are serious business – in fact they were at the heart of the SOPA proposal that inspired millions of emails to the US Congress in opposition.
The concern about .com may be a bit over-stated.
Verisign’s current .com contract is presumptively renewed November 2018 provided that it adopts terms similar to those in place at the five next-largest gTLDs.
Given that .net is the second-largest gTLD, and that .net does not have URS, we’d have to either see .net’s volume plummet or at least five new gTLDs break through the 15 million domains mark in the next three years, both of which seem extraordinarily unlikely, for .com to be forced to adopt URS.
However, if URS has become an industry standard by then, political pressure could be brought to bear regardless.
Other changes to .pro and .cat contracts include a change in ICANN fees.
While .pro appears to have been on the standard new gTLD fee scheme since 2012, .cat is currently paying ICANN $1 per transaction.
Under the new contract, .cat would pay $0.25 per transaction instead, but its annual fixed fee would increase from $10,000 to $25,000.
The .travel gTLD, which was approved 10 years ago, will have to support the Uniform Rapid Suspension service, one of several significant changes proposed for its ICANN contract.
I believe it’s the first legacy gTLD to agree to use URS, which gives trademark owners a way to remove domain names that infringe their marks that is quicker and cheaper than UDRP.
Tralliance, the registry, saw its .travel Registry Agreement expire earlier this month. It’s been extended and the proposed new version, based on the New gTLD Registry Agreement, is now open for public comment.
While the adoption of URS may not have much of a direct impact — .travel is a restricted TLD with fewer than 20,000 names under management — it sets an interesting precedent.
IP interests have a keen interest in having URS cover more than just 2012-round gTLDs. They want it to cover .com, .org, .net and the rest too.
Domain investors, meanwhile, are usually cautious about any changes that tilt the balance of power in favor of big brands.
When .biz, .org and .info came up for renewal in 2013, the Intellectual Property Constituency filed comments asking for URS to be implemented in the new contracts, but the request was not heard.
I’m aware of two ccTLDs — .pw and .us — that voluntarily adopted URS in their zones.
Other changes include a requirement for all .travel registrars, with the exception of those already selling .travel domains, to be signatories of the stricter 2013 Registrar Accreditation Agreement.
That’s something Afilias and Neustar only agreed to put in their .info and .biz contracts if Verisign agrees to the same provisions for .com and .net.
The fees Tralliance pays ICANN have also changed.
It currently pays $10,000 in fixed fees every year and $2 per billable transaction. I estimate this works out at something like $40,000 to $50,000 a year.
The proposed new contract has the same fees as 2012-round new gTLDs — a $25,000 fixed fee and $0.25 per transaction. The transaction fee only kicks in after 50,000 names, however, and that’s volume .travel hasn’t seen in over five years.
Tralliance will probably save itself thousands under the new deal.
The contract public comment forum can be found here.
If you register a .sucks domain matching a brand, could you survive a subsequent UDRP complaint? Opinion is mixed.
In my view, how UDRP treats .sucks registrants will be a crucial test of Vox Populi Registry’s business model.
Vox Populi Registry clearly envisages — and is actively encouraging with its policies — genuine critics, commentators and consumer advocates to register .sucks domains that match famous trademarks.
I really like this idea. Power to the people and all that.
But will UDRP panelists agree with me and Vox Pop? Cybersquatting case law under UDRP says, very firmly: “It depends.”
Statistics generally favor mark owners
To date, there have been exactly 100 resolved UDRP complaints against domains that end in “sucks.com”.
Of those, 47 cases ended up with a full transfer of the domain to the trademark owner. Only 30 resulted in a the complaint being denied.
Another 19 cases were withdrawn or terminated; the remainder were split decisions.
So it seems, based on historical “sucks” cases, that the odds favor trademark owners.
But each case is, theoretically at least, judged on its merits. So it does not necessarily hold that most .sucks UDRP complaints will be successful.
What does WIPO say?
The World Intellectual Property Association, which administers most UDRP cases, published a set of guidelines for its panelists.
Some guidelines specifically addresses “sucks” sites, but the advice is not always clear-cut.
There are three elements to UDRP. First, the complainant must show that the domain name in question is identical or confusingly similar to its trademark.
According to WIPO, it’s the “consensus view” of UDRP panelists that adding “sucks” to a trademark at the second level does NOT stop a domain being confusiningly similar. WIPO says:
Generally, a domain name consisting of a trademark and a negative or pejorative term (such as [trademark]sucks.com) would be considered confusingly similar to the complainant’s trademark for the purpose of satisfying the standing requirement under the first element of the UDRP (with the merits of such cases typically falling to be decided under subsequent elements). Panels have recognized that inclusion of a subsidiary word to the dominant feature of a mark at issue typically does not serve to obviate confusion for purposes of the UDRP’s first element threshold requirement, and/or that there may be a particular risk of confusion among Internet users whose first language is not the language of the domain name
Some panels have disagreed with this prevailing view, however.
It remains to be seen whether moving the string “sucks” to the right of the dot would affect the outcome, but it’s established UDRP case law that the dot in a domain can be pretty much ignored when testing for similarity.
The TLD a domain uses can be taken into account if it’s relevant or disregarded if it is not, according to precedent.
The second test under UDRP is whether the registrant of the domain has legitimate rights or interests.
Panelists disagree on this point. WIPO says:
The right to criticize does not necessarily extend to registering and using a domain name that is identical or confusingly similar to the complainant’s trademark. That is especially the case if the respondent is using the trademark alone as the domain name (i.e., [trademark.tld]) as that may be understood by Internet users as impersonating the trademark owner.
That view would seem to apply specifically to the use cases Vox Pop has in mind — the registry wants critics to own [trademark].sucks domains in order to criticize the trademark owner.
Respondents’ can very well achieve their objective of criticism by adopting a domain name that is not identical or substantially similar to Complainants’ marks. Given the free nature of the media which is the Internet and the chaotic spamming that has become epidemic, it does not appear that one can be at full liberty to use someone else’s trade name or trademark by simply claiming the right to exercise a right to freedom of expression”.
In other words: you may have a right to free speech on the internet, but you do not have the right to exercise it simply by adding “sucks” to a famous trademark.
But other UDRP panelists have disagreed. WIPO says that some panelists have found:
Irrespective of whether the domain name as such connotes criticism, the respondent has a legitimate interest in using the trademark as part of the domain name of a criticism site if such use is fair and noncommercial.
The third element of UDRP is bad faith. Complainants have to show that the registrant is up to something dodgy.
Some panelists have a pretty low threshold for what constitutes bad faith. Merely having the page parked — even if you did not park it yourself — can point to bad faith, especially in “sucks” cases.
WIPO says that “tarnishment” of a trademark — such as posting porn, which is banned under Vox Pop’s AUP anyway — can be bad faith, but legitimate criticism would not usually:
While it would not normally extend to the mere posting of information about a complainant, or to the posting of genuine, non-commercial criticism regarding the trademark holder, it may extend to commercially motivated criticism by (or likely on behalf of) a competitor of such trademark holder.
So, with all that in mind, here are some tips for improving your odds of surviving a .sucks UDRP.
How to beat a .sucks UDRP
Poring over dozens of “sucks.com” decisions, it quickly becomes clear that there are certain things you should definitely do and not do if you want to keep a hold of your brand-match .sucks domain.
Given the volume of precedent, you’ll have a hard time showing that your domain is not identical or confusingly similar to the trademark in question — strike one — but there are ways to show legitimate interests and rebut claims of bad faith.
To show you lack legitimate interests, the complainant only needs to make a face-value argument that you do not. Then the burden of proof to show rights switches to you.
If you don’t respond to the UDRP, the panel will find you lack rights. Panelists rarely try to fight the corner of a registrant who has not responded.
That’s strike two.
2. Don’t allow your domain to be parked
If a domain is parked, UDRP panelists in “sucks.com” cases invariably find that the registrant lacks legitimate interests and has shown bad faith.
Parking is considered a commercial activity, so you won’t be able to argue convincingly that you’re exercising your right to non-commercial free speech if your domain is splashed with links to the trademark owner’s competitors.
This holds true even if the domain was automatically parked by your registrar.
Dozens (hundreds?) of UDRP cases have been lost because Go Daddy parked the newly registered domain automatically, enabling the complainant to show commercial use.
Panelists are usually happy to overlook the lack of direct bad faith action by the registrant in such cases.
Parking will usually lead to strikes two and three.
In the case of .sucks, parking is actually banned by Vox Populi’s acceptable use policies (pdf).
But the registry will only enforce this policy if it receives a complaint. I don’t know if the Registry-Registrar Agreement, which isn’t public, prohibits registrars auto-parking new domains.
3. Develop a site as soon as possible
In some “sucks.com” cases, respondents have argued that they had intended to put up a criticism site, but could not provide evidence to back up the claims.
If you register a .sucks matching a trademark, you’ll want to put up some kind of site ASAP.
In the case of kohlersucks.com, the registrant had merely framed a Better Business Bureau web page, which was found to show non-commercial criticism use.
4. Don’t offer to sell the domain
It should go without saying that offering to sell the domain to the trademark owner shows bad faith; it looks like extortion.
Panelists regularly also find that registrants give up their legitimate rights to a domain as soon as they make it available to buy.
5. Don’t make any money whatsoever
The second you start making money from a domain that matches a trademark, you’re venturing into the territory of commercial use and are much more likely to fail the WIPO test of “genuine, non-commercial criticism”.
6. Be American
Depressingly, you stand a better chance of fighting off a UDRP on free speech grounds if both the case involves US-based parties and a US-based panelist.
Panelists are more likely to draw on the US Constitution’s First Amendment and associated non-UDRP case law when determining rights or legitimate interests, when the registrant is American.
Merely registering with a US-based registrar is not enough to confer First Amendment rights to a registrant living outside of the US, according to UDRP panels.
Even though freedom of speech is a right in most of the world, in the universe of UDRP it seems the rest of us are second-class citizens compared to the yanks.