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:
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.
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:
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.
Read the full series here.
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.
ICANN did not have much to report in this week’s batch of new gTLD evaluation results, as that stage of the program gradually winds down.
Two dot-brands — Shaw Cablesystems and TUI — passed Extended Evaluation for their .shaw and .tui applications.
TUI had to secure permission from Burkina Faso for .tui, which matches the protected name of one of its provinces, while Shaw had to provide better financial statements to pass.
Only four applications remain in Initial Evaluation — .pwc, .bbb, .kosher and .search. Eight applications are currently in Extended Evaluation.
Four new gTLD registries signed their contracts with ICANN yesterday.
Donuts added Registry Agreements for .email and .codes to its portfolio, bringing its total up to 43.
CORE Association signed for بازار., which means “bazaar”. It’s CORE’s third and final RA as an applicant and its only Arabic application. It’s already live with two Cyrillic strings.
Finally, DotBerlin signed its contract for the city TLD .berlin, apparently confirming the rumor that the one it signed on stage alongside .wien at the newdomains.org conference earlier this week was in fact a prop.
According to the DI PRO database, ICANN now has contracts with 80 new gTLDs and 18 legacy gTLDs.