Over half the world’s biggest brands will be blocked in new gTLDs

More than half of the world’s most-famous brand names already stand to benefit from blocks in new gTLDs, due to the name collisions policy introduced by ICANN recently.
That’s the preliminary conclusion of a quick analysis of the 37 block-lists already published.
Using Interbrand’s list of the top 100 most valuable brands, we find that only 32 do not appear anywhere — either as strings or substrings — on the collisions lists we have today.
Fifty-nine brands are to be blocked as exact matches in at least one new gTLD. Five brands are blocked exactly in 10 or more.
Brand owners blocked in collision lists may not have to fork out for as many defensive registrations, but may also face complications when registries finally start whittling down their lists.
We present the full table of results below, for which the following explanations might be needed:

• Brand/String — The brands have been normalized to ASCII strings, removing punctuation not compatible with the DNS protocol and converting accented characters to their unaccented equivalents (for example, “Nescafé” becomes “Nescafe”). For DI PRO subscribers, each string links to a search on the database for that string.
• Exact Matches — The number of gTLDs (currently out of 37) in which this exact-match brand will be blocked.
• Unique Strings — The number of strings containing this brand that appear on block-lists. In some cases this may provide misleading results due to the usual overkill you get when matching substrings. For example, two-character brands such as 3M and HP get a lot of hits, the vast majority of which do not appear to relate to the brand itself, whereas every hit for Google does in fact refer to the brand.

[table id=19 /]
The numbers will of course grow rapidly as ICANN publishes more collisions lists.
If there’s sufficient interest from DI PRO subscribers in this breakdown being kept up to date on an ongoing basis, I’ll bolt it on to to the existing collisions database.

Over 87,000 new gTLD domains now blocked

The total number of domain names to be blocked due to the risk of name collisions has topped 87,000 with the latest batch of block-lists from ICANN, published yesterday.
According to our database, 87,670 domain names, representing 75,208 unique second-level strings, are to be blocked in the 37 new gTLDs that have published collisions lists.
The string “www” is on all 37 lists, followed closely by “com”, “org” and “net”.
The most commonly blocked names include large numbers of single characters and large numbers of two-character strings matching ccTLDs (which were already banned in new gTLDs anyway).
Lots of protocol-related strings, such as “http”, “ftp”, “isatap” and “wpad” can also be found in the top 100 strings.
Gambling-related strings are also hugely, and so far inexplicably, popular blocking candidates.
Google, Yahoo, Facebook and Apple are the most frequently seen brands.
The full consolidated list of blocked strings can be searched at the DI PRO name collisions database.
The gTLD with the biggest block-list so far is .kitchen, with 13,061 strings, over half as big again as the next-longest list, which is .uno’s 8,187 names.

Over 100 new gTLD contracts now signed

The pace is stepping up as ICANN starts to lift its heels in moving more new gTLDs towards delegation.
The organization signed contracts with registries covering 34 strings over the weekend, including popular favorites such as .wiki and .ninja.
The full list of gTLDs with freshly signed Registry Agreements goes like this:

.education, .institute, .training, .international, .builders, .build, .solar, .marketing, .solutions, .academy, .company, .camp, .systems, .business, .management, .center, .repair, .red, .glass, .house, .farm, .holiday, .kaufen, .ninja, .gal, .social, .moda, .blue, .ceo, .immobilien, .wiki, .florist, .公益 and .政务.

At 34 in a week, it’s an almost 50% increase on the number of new gTLD RAs ICANN has entered into, and dangerously close to the 40-per-week rate that was originally planned.
By our reckoning, there are now 115 new gTLDs with ICANN contracts.

ICANN rejects third new gTLD bid

ICANN has formally rejected .thai, only the third new gTLD application to suffer this fate.
It’s been flagged as “Not Approved”, following an objection from a consensus of the Governmental Advisory Committee led by an outcry from Thailand and Thai nationals.
Only DotConnectAfrica’s .africa and GCC’s .gcc have the same designation. Both also were killed off by GAC advice.
Better Living Management Company had applied for .thai, promising to restrict it to people and organizations with a local presence.
Thailand already has the ccTLD .th, of course, as well as the IDN equivalent, .ไทย, which means “Thailand”.
ICANN has not yet rejected any applications that lost crippling objections filed by non-governmental actors.

XYZ says auctions “comfortably within the rules”

New gTLD registry XYZ.com has responded to criticisms of its plan to auction .xyz and .college names with NameJet before they even have signed contracts with ICANN.
CEO Daniel Negari told DI that the plan to auction 40 names between now and the end of February, is “comfortably within the rules”.
The company seems to be operating at the edge of what is permissible under the new gTLD program’s rights protection mechanisms, which state that no domains may be allocated prior to Sunrise.
But Negari said in an email interview that nothing will be “allocated” before its Sunrise periods are done:

the buyers at auction are not buying the domain names as in a normal auction. They are buying an option to force us to allocate them the domain after the Sunrise Period for the auction price assuming various contingencies are met — such as us being able to allocate the name in the future, the name being available after sunrise, the name not being blocked-out because of name collisions and so on.

He went on to say that the 40 names being put to auction are being drawn from the 100 names the recently redrafted Registry Agreement says registries are allowed to allocate to themselves “necessary for the operation or the promotion of the TLD”.
There’s also the potential problem that neither TLD has yet received its list of name collisions, which are likely to contain thousands of strings that the registry must block at launch.
As we’ve seen with the gTLDs that already have their lists, many desirable second-level strings are likely to be blocked, which could clash with names XYZ is planning to auction.
But XYZ seems to have access to the Day In The Life Of The Internet data from which these lists are compiled, and Negari said that the names it is auctioning off do not appear.
“We think these auctions are a great way to both promote our TLD as anticipated by ICANN in the RA and to bring increased innovation to the space in line with ICANN’s stated goals for the new gTLD program,” Negari said.

Tucows takes over as Cheapies loses accreditation

ICANN has terminated the registrar Cheapies.com and is to transfer its registrations to Tucows.
Cheapies had fewer than 12,000 gTLD domains under management judging by the last available registry reports.
The registrar was terminated two weeks ago, having previously having its accreditation suspended for 90 days, for various violations of the Registrar Accreditation Agreement mainly related to records keeping.
ICANN said Cheapies’ customers should receive an email from Tucows instructing them how to proceed.

Nine Donuts gTLDs delegated

Donuts has had a batch of nine new gTLDs delegated to the DNS root today.
The nine strings are: .ventures, .camera, .clothing, .lighting, .singles, .voyage, .guru, .holdings and .equipment.
All belong to various Donuts subsidiaries that have signed Registry Agreements with ICANN over the last few months.
At this precise moment it does not seem that any have their basic “nic.” second-level domains active and resolving, but all are appearing in the DNS root zone.
Earlier today, Donuts announced the sunrise dates for the first seven gTLDs in its portfolio.
The company already has one gTLD delegated, the Chinese-script version of “.games”.

.sexy and .uno raise the average collisions list size

The third batch of new gTLD collisions lists has been released by ICANN, raising the average number of domains that registries are being told to block on extremely cautious security grounds.
The average number of second-level domains to be blocked per gTLD is now 1,904, largely due to the impact of very large lists for .uno (which has 8,187) and .sexy (6,560), which were published yesterday.
This number is only going to get bigger as more cool-sounding Latin-script gTLDs raise the average.
It will be tempered somewhat by the IDN gTLDs, however. The average list for IDNs has only 253 names on it, based on the five published so far.
The most popular strings, ranked by the number of gTLDs’ lists in which they show up (out of a possible 18), are:
[table id=15 /]
There are 30,581 unique second-level strings in total, all of which are fully cross-referenced and searchable at DI PRO.
The most-blocked exact-match brands so far are Yahoo and Google, which both appear on 10 lists. Apple, Facebook and YouTube appear as exact matches on eight.

Applicants call for new gTLD objections appeals process

Twelve new gTLD applicants, representing many dozens of applications, have called on ICANN to create an appeals process for when Community Objections have debatable outcomes.
Writing to ICANN and the International Chamber of Commerce this week, the applicants focus on the recent decision in the .sport case, which they said proves that ICC panelists don’t fully understand the Community Objection policy as laid out in ICANN’s Applicant Guidebook.
The letter points to five “glaring errors” in the “fatally flawed” .sport decision, in which Olympics-backed applicant SportAccord prevailed over Famous Four Media’s competing application.
The signatories — which include Radix, United TLD, Donuts, Famous Four, TLDH and others — say that the ICC panelist simply assumed SportAccord represented the “sport” community and failed to pinpoint any “likelihood of material detriment” that would be caused by Famous Four’s .sport going ahead.
It seems to me that the latter arguments are much more well-founded.
While the letter tries to pick holes in the panelist’s finding that SportAccord represents enough of the “sport” community to be able to win the objection, the arguments are pretty tenuous.
The applicants use an definition of “community” found elsewhere in the Guidebook, for example, to attempt to show that the panelist failed to follow the guidelines for establishing a community in a Community Objection.
The panelist’s actual ruling uses the definition of “community” from the relevant part of the Guidebook and seems to follow it fairly closely. The applicants make a poor job of questioning his logic.
However, on “detriment”, the letter seems to be on much firmer ground.
It argues that the panelist deliberately lowered the bar from “likelihood of material detriment” to “possibility of material detriment” in order to hand SportAccord a victory.
The letter states:

If the Expert’s current logic is followed, every application, including the Objector’s own application, creates “possible” damage. In this case, an allegation of material detriment against any application would be upheld because there is future “possible” damage.

It also makes reference to the fact that the panelist appears to in many cases have been weighing the Famous Four application against SportAccord’s, which was not his job.
It reads in part: “The Expert did not identify a single objectionable or lacking aspect in the application that creates a likelihood of material detriment.”
The applicants call on ICANN to immediately create an appeals mechanism for Community Objections, and to ensure that ICC panelists are given training before making any more decisions.
Here’s the full list of signatories: Radix, United TLD, DotClub Domains, Top Level Design, Donuts, Top Level Domain Holdings, Priver Nivel, Fegistry, Employ Media, Famous Four Media, Merchant Law Group, DotStrategy.

ICANN makes GAC’s Category 1 new gTLD advice less stupid

After six months, ICANN is finally giving its Governmental Advisory Committee what it wants. Kinda.
The New gTLD Program Committee has quietly sent its plan to implement the GAC’s so-called “Category 1” advice on new gTLDs, which called for regulated gTLDs where applicants had applied for open namespaces.
But it’s rewritten the advice in such a way that it’s unlikely to win many fans in either camp, causing headaches for applicants while also falling short of giving the GAC everything it wanted.
In a letter to GAC chair Heather Dryden, ICANN chair Steve Crocker laid out the NGPC’s plan.
The Category 1 advice, which comprised eight “safeguards” applicable to at least 386 gTLD applications for 174 unique strings, has been rewritten, making it a little more palatable to the majority of applicants.
The list of strings has also been cut in two, with the 42 strings considered most often linked to highly regulated industries taking the brunt of the regulation.
These 42 may or may not find their business models killed off, but are certainly facing more friction as a result of the NGPC’s decision:

.abogado, .attorney, .autoinsurance, .bank, .banque, .bet, .bingo, .carinsurance, .casino, .charity (and Chinese IDN), .corp, .cpa, .creditcard, .creditunion, .dds, .dentist, .gmbh, .hospital, .inc, .insurance, .ira, .lawyer., .lifeinsurance, .llc, .llp, .lotto, .ltd, .ltda, .medical, .mutualfunds, .mutuelle, .pharmacy, .poker, .sal, .sarl, .spreadbetting, .srl, .surgery, .university, .vermogensberater, .versicherung

Each of these registries is going to have to sign up to eight new mandatory Public Interest Commitments, obliging them to engage with the industries associated with their strings, among other things.
And while the GAC wanted these strings to be limited to credential-holding members of those industries, ICANN seems to be giving the applicants much more implementation wiggle room.
The GAC had originally called for all 386 Category 1 registries to:

Establish a working relationship with the relevant regulatory, or industry self-regulatory, bodies, including developing a strategy to mitigate as much as possible the risks of fraudulent, and other illegal, activities.

But ICANN has reinterpreted the advice to make it a bit less onerous on applicants. It will also only affect 42 strings. The advice, now rewritten as a PIC, reads:

Registry operators will proactively create a clear pathway for the creation of a working relationship with the relevant regulatory or industry self-regulatory bodies by publicizing a point of contact and inviting such bodies to establish a channel of communication, including for the purpose of facilitating the development of a strategy to mitigate the risks of fraudulent and other illegal activities.

Does that PIC mean registries will actually be obliged to listen to or give policy-making power to the relevant industries on a formal basis? It’s ambiguous enough that the answer might easily be no.
The GAC had also called for some Category 1 gTLDs to become restricted to card-carrying members of the industry or industries the strings relate to, saying in Beijing:

At the time of registration, the registry operator must verify and validate the registrants’ authorisations, charters, licenses and/or other related credentials for participation in that sector.

ICANN has basically rejected that advice, replacing it instead with the much more agreeable (to registries) text:

Registry operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring a representation that the Registrant possesses any necessary authorisations, charters, licenses and/or other related credentials for participation in the sector associated with the Registry TLD string.

You’ll notice that the ICANN version does not require credentials to be provided at the point of registration. In fact, the PIC seems to require nothing more than a check-box that the registrant must click.
This is obviously tolerably good news for applicants that had proposed unrestricted policies for their gTLDs — they no longer face the kiss of death in the registrar channel that the GAC’s version would have created — but let’s not pretend it’s what the GAC had asked for.
Again, it only applies to the 42 strings ICANN has identified as particularly broadly regulated.
These registries are not getting an easy ride, however. They will have to enforce a post-registration regime of verifying credentials in response to complaints. The new ICANN PIC reads:

If a Registry Operator receives a complaint expressing doubt with regard to the authenticity of licenses or credentials, Registry Operators should consult with relevant national supervisory authorities, or their equivalents regarding the authenticity.

It’s implied, but not stated, that uncredentialed registrants should lose their domains. Again, the ICANN version of the GAC advice may be less of a nightmare to implement, but it’s still very vague indeed.
For any Category 1 applicant that is not on the sub-list of 42 sensitive strings, there will be three new PICs to adopt.
These all instruct the registry to require registrars to get registrants to agree to abide by “all applicable laws”. It’s the kind of stuff that you usually find in registration agreements anyway, and doesn’t appear at first look to present any hugely problems for registries or registrars.
Overall, ICANN seems to have done a pretty good job of making the Category 1 advice less onerous, and applicable to fewer applicants, than the GAC originally wanted.
But applicants for the 42 strings most heavily affected still face some vague contractual language and the very real possibility of industry complaints in future.