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.

New gTLDs bring back tiered renewal pricing

Only one mass-market TLD used it, and it’s often considered a bad idea, but variable pricing for domain name renewals is making a comeback with the launch of new gTLDs.
What Box? and Plan Bee are the first two new gTLD registries to start selling domains with tiered renewal fees, in .menu and .build respectively, via Go Daddy.
If you pay Go Daddy $189.99 for a “Priority Rre-registration” in .build, your annual renewal fee if you secure the name will be be $149.99, instead of the $99.99 other pre-registrants will pay.
Similarly, a Priority Pre-registration in .menu will set you back $199.99 a year, forever, instead of $49.99.
I understand that the standard Go Daddy initial registration fee for these two TLDs during general availability will also be $99.99 and $49.99 respectively.
The other two new gTLDs with announced pricing, .uno and .luxury, do not appear to be charging tiered rates.
Go Daddy confirmed that the renewal pricing will be permanently higher in the .build and .menu, telling us:

The industry is starting to move toward a tiered pricing system. As such, some registries have elected to make renewals higher on domain names captured during the priority pre-registration period.

It’s actually permitted under ICANN’s standard Registry Agreement.
Generally, the RA prevents registries charging variable renewal fees. If you find yourself running a successful business in a new gTLD, the registry is not allowed to gouge you for higher renewals.
There’s a provision in section 2.10 of the contract that is designed to “prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry Operator”.
But the rule does not apply if you’re told at the point of registration that your renewal pricing will be higher.
The contract states that “Registry Operator must have uniform pricing for renewals of domain name registrations”, but grants this huge exception:

if the registrar has provided Registry Operator with documentation that demonstrates that the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domain name following clear and conspicuous disclosure of such Renewal Pricing to such registrant

The only major TLD to try variable pricing before now was .tv, which Verisign currently operates.
The .tv registry held back thousands of desirable strings when it launched in 2000. Instead of auctioning them, it priced these names to sell, but with renewal prices matching the initial registration fee.
If you bought a premium .tv name 10 years ago for $10,000, you’ve been paying $10,000 a year ever since.
This proved very unpopular — especially with domain investors, who continue to moan about the high carrying cost of .tv names bought years ago — and Verisign scrapped the policy on new registrations in 2010.
Some say tiered renewal pricing is the main reason .tv isn’t nearly as popular as it arguably should be.
But will it work in 2014?
Tiered renewal fees seems like an excellent way to discourage domainers from participating in your launch.
Would you be willing to pay higher renewal fees ad infinitum just for the chance for first dibs on the new gTLD domain name you want?

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”.

Donuts puts date to first Sunrise, signs big registrars, says it won’t have a landrush

Donuts has announced the dates of its first Sunrise periods and revealed that it’s not planning to run a landrush period for its first seven new gTLDs.
The company said today that it plans to take .bike, .clothing, .guru, .holdings, .plumbing, .singles and .ventures to Sunrise on November 26.
It’s opted for a 60-day Sunrise period, going to full general availability on January 29 next year. The company said:

Donuts will forego a traditional land-rush and move directly to general availability to all registrants on January 29, 2014. Donuts’ gTLDs are available for registration by anyone without restriction.

Donuts also said it has signed the following registrars to its channel: GoDaddy, 1&1 Internet, Web.com, Tucows, Host Europe Group, Key-Systems, CSC Digital Brand Services, MarkMonitor, NetNames, Gandi, united-domains, Melbourne IT and 101domain.
While the press release issued this afternoon suggests that the seven strings in question have already been delegated, I’m not seeing them in the DNS root zone yet.

.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.

dotShabaka Diary — Day 23, Wrap-up and Top Tips

We’re wrapping up the dotShabaka Diary series today with this, the final entry from general manager Yasmin Omer.
It’s been an interesting ride, and I thank Yasmin and the dotShabaka team for the time and effort they’ve put into sharing their experiences with DI readers.

Tuesday 5 November 2013
After four months of journal entries, the dotShabaka Registry Diary is wrapping up today following the delegation of شبكة. and official commencement of Sunrise.
The journey has been long and challenging at times. After all the blood, sweat and tears, I strongly believe our experience will be to the benefit of other applicants to follow.
Along the way we experienced the joys of passing pre-delegation testing and commencing Sunrise, but we also documented the lows of name collisions and difficulties in writing a Registry Registrar Agreement.
Throughout the journey it was helpful to receive feedback and comments from the community supporting our cause. This dialogue helped get us to where we are today and a special thank you must be made to IBM’s TMCH team, ICANN, the Pre-Delegation Testing team at IIS (and the PDT Helpdesk) and the many Registrars who have connected with us along the way. Also, a big thank you to Domain Incite and Kevin Murphy for making this journal series possible.
As our delegation journey comes to an end, our TLD launch strategy begins. We have strong ambitions for شبكة. to be the centre of all things Arabic online and we encourage you to continue to watch our progress via our website.
As a parting message, below are our top five tips for other applicants:
1. Communication
Communication is vitally important throughout the process. Be prepared for important emails at any time of the day. When in doubt, always clarify with ICANN and your advisors first. If you are not sure ask ICANN through the CSC portal and if you don’t get a good answer from ICANN ask again through the CSC portal.
2. Seamless integration with RSP
Ensure you have open lines of communication with your Registry Services provider to avoid hiccups and delays. We received technical communications that should have been intended for ARI Registry Services, but our close working relationship with them helped ensure a smooth process.
3. Sort out your product and strategy
Registrar community, potential Registrants, media and interest groups will want information about your TLD. Be ready to describe your TLD, the primary market, eligibility, the launch strategy and other key information.
4. Expect the unexpected
This goes without saying, especially in the ICANN ecosystem. Be flexible and prepare for the worst.
5. The ICANN interface is improving
We understand that many of the frustrations with ICANN occurred because we were the first, and we were pushing hard to go to market. However, it is improving. ICANN are now sending a media kit and hopefully one day someone will get a Welcome Pack.
Good luck to all the other applicants, we’ll be closely watching your progress through delegation.
Regards
Yasmin Omer
General Manager
dotShabaka Registry

Read the full series here.

dotShabaka Diary — Day 22, Sunrise has gone live!

In this penultimate entry in the dotShabaka Diary series, dotShabaka general manager Yasmin Omer officially announces the launch of the Sunrise period for شبكة., the first new gTLD to enter this phase.

Saturday 2 November 2013
It’s with great pleasure that I can finally say that we are the first new gTLD Registry Operator to commence its Sunrise Period! I’m truly excited about taking this TLD to the Arabic speaking world and revolutionising their Internet experience. So what’s happened since the last entry?
We received, and responded to, the TLD on-boarding Information Request from ICANN. New gTLD Registry Operators (and their Registry Services Providers) should be prepared to promptly provide ICANN with technical information regarding:

• The Registry Operator’s provision of the zone file access service;
• Bulk thin registration data access to ICANN;
• Data Escrow – Registry Reporting Interface;
• Implementation of the URS system;
• EPP extensions for the TLD; and
• EPP SLA Monitoring.

We requested the registration of our IDN Table on the IANA Repository of IDN Practices.
We obtained approval of our TLD Startup Information from ICANN. It’s certainly clear from our interactions with ICANN that the process of, and the requirements for, obtaining IBM’s acceptance of Sunrise dates and ICANN’s approval of TLD Startup Information, is yet to be defined. As a result, there was a delay in obtaining ICANN’s approval of our TLD Startup Information.
If you’re a new gTLD Registry Operator and you want your TLD Startup Information approved quickly, here are some tips:

• Once you have a fair idea of when your Sunrise will commence (could be before you’re delegated), reach out to IBM independently and request a number of potential dates. The team at IBM has been very responsive by promptly accepting our Sunrise dates.
• Include your eligibility policy for general registration with your TLD Startup Information. Yes, ICANN has explicitly stated that this is not a requirement they have imposed but it seems that they need it.
• Remember that ICANN’s review is a legal review. Ensure that your policies very clearly demonstrate your compliance with the relevant requirements. Use diagrams.
• Be prepared to respond to ICANN or IBM at any time – they’re both on opposite sides of the world to each other. ICANN thankfully ensure that the process is interactive, so be prepared to interact.

Good luck to everyone. We look forward to being joined by many more New gTLD Registry Operators in Sunrise.

Read previous and future diary entries here.