Friday, June 30, 2017

.SEARCH new gTLD coming...from Google

Charleston Road Registry, the legal entity belonging to Google in charge to create/launch its TLDs, has three extensions coming to the market:
  1. The .SEARCH new gTLD;
  2. .MAP
  3. .PHD
(Amazon also applied for .MAP and .SEARCH but applications were withdrawn in the end).


Google is about "search": isn't it?
This domain name extension comes late in the ICANN new gTLD program and there is a reason for this but what matters is what use is Google to have of ".search" domain names.

What the application says
Extracted from the application submitted to the ICANN:
The mission of the proposed gTLD, .search, is to provide a domain name space that makes it easier for Internet users to locate and make use of the search functionality of their choice. The proposed gTLD will open possibilities for new, more convenient ways for Internet users to navigate to the services they like and use.
Most of the time, the purpose of the extension is explained in question 18 A from the application ("Describe the mission/purpose of your proposed gTLD") but it is in the following question (18 B) of that Google explains in one line how ".search" domains will be used:
The goal of the proposed gTLD is to provide a space dedicated to Internet search offerings, and to make it easier for users to access the search functionality of their choice. The proposed gTLD will signal to the general population of Internet users that .search websites are indeed websites that offer search functionality, and adhere to basic technical standards.
Shoot in the feet?
When you are the number one search engine worldwide, do you want to offer a tool to incite others to start building search engines? I seriously doubt it and maybe this sentences extracted from the application gives more info about the real use ".search" registrants will be able to have of their domain name:
Charleston Road Registry plans to develop and publish eligibility criteria for all registrants in the proposed gTLD and will work with its registrars to execute the eligibility verification process. This process will imbue additional meaning to all second-level domains in the gTLD and enhance the gTLD’s reputation by establishing an authoritative community of websites that offer search functionality. When Internet users visit a website in the proposed gTLD environment, they will be able to reliably expect services relevant to the proposed gTLD.
Will this be a restriction? It is a little unclear to me but
Innovation
Again, some sentences are unclear but innovation seems to be around the corner:
The .search gTLD will provide a new mechanism whereby websites with search functionality can enact second-level domains that offer search-related services. This signification is not currently available in the gTLD space.

...it provides a simple technical standard describing how users and other software can interact with search functionality within the TLD.

Even more importantly, a consistent query interface across all search websites in the TLD makes it easier for third-party developers to create new and innovative services that will allow users to interact with search functionality in new and creative ways.
Trademarks
Charleston Road Registry will also develop policies to limit registrations within the domain to the names that registrants commonly use in trade related to their provision of search-related services, possibly including restricting registrations to exact matches of trademarks.
Technical requirements
Here we are, it appears that registering a ".search" domain name will not be as simple as registering a ".club":
Charleston Road Registry will implement a validation service to verify compliance with these technical requirements.
Check 18.b.iv. Registration Policies from the application "TECHNICAL REQUIREMENTS FOR REGISTRATION WITHIN THE .SEARCH GTLD" for details.

Interesting too:
Supplying Google account information will be optional for registrants.
I understand from this sentence that it will be possible to connect a ".search" domain names to Google' services.

(My) conclusion
I am a fan of Google's products and I use them everyday. I like this last idea to be able to supply my Google account information to a ".search" domain name because it will probably help one develop his business: few know much about coding so if connecting a Google account to a ".search" domain can save time developing a search engine, it adds credibility to this Registry's project. I don't think Google is selling ".search" domains for money and even if the application does not say it explicitly, the ".search" Registry looks like it is a restricted one so I expect content to be found on ".search" websites...not to be crap. A candidate to the Verified Top-Level Domains (vTLD) Consortium maybe?

Google.search coming? Probably...but I don't expect Google.com to change to Google.search :-)

Thursday, June 29, 2017

gTLD.club : WTF?

I frankly admit that I have no idea with what's going on at the moment at gTLD.club. Below is a copy-paste of the stats.


Wednesday, June 28, 2017

New gTLDs: what was said recently

Extracted from our Newsletter, below are the latest NEWS related to new gTLDs from previous days:
  1. Follow-up: ICANN and new gTLDs (slides);
  2. Domain registrars hate registry exceptions;
  3. Phishing: the Worst of Times in the DNS;
  4. .BRANDs : a solution to face Phishing;
  5. Boots becomes latest company to terminate new gTLD;
  6. 3 Keys to the Right Domain Name for Building a Brand;
  7. Which New gTLD Is Winning The Website Development War?
  8. New website for .GLOBAL Registry;
  9. Greatest Benefits of New gTLDs is PR;
  10. Backend Registries: who are they?
  11. Heading to South Africa for ICANN 59: A Quick Preview;
  12. New gTLD to be delegated soon: .MERCKMSD;
  13. .BNPPARIBAS went down;
  14. Draft Framework for the Registry Operator to Respond to Security Threats;
  15. Navigating the World of New gTLDs – Read the Latest Trends;
  16. .BOOTS self-terminates;
  17. .NYC’s most trafficked websites are actually legit;
  18. HOT - Announced today and started: the .BASKETBALL Sunrise Period (...);
  19. Domain Names Looks Kind of Random;
  20. Analyzing Donuts’ deal to acquire Rightside;
  21. Dot .BAWSTON : gTLD application denied by ICANN (joke of the day);
  22. What is Happening with ICANN Reviews?
  23. Changing to a .INTERNET new gTLD?
Subscribe (for free) to receive latest News directly in your email.

.BRANDS : numbers


Friday, June 23, 2017

A ".dash" new gTLD coming?

About.com just announced: "Hi. We're Dotdash. We were About.com".

I don't know the reason for this change but it reminds me that a lot of people secured domain names starting with "dot" before round one of the ICANN new gTLD program to start. This was a way to secure a good domain name before the activation of the extension's first domains. It was a way to use the corresponding name of the extension to start publishing after "reveal day" in July 2012.


There was no application submitted for a .DASH new domain name extension in the first round and the design of this new name added to this new domain name could be a sign that a .DASH new gTLD project is coming... or not.

The .BOND Sunrise Period starts

As published on the Trademark Clearinghouse's calendar, today starts the .BOND Sunrise Period.

WHEN
  • START: Friday, 23 June, 2017 - 16:00;
  • END: Sunday, 23 July, 2017 - 16:00.
OK, so what first comes to your mind when you read this? "James Bond"? Well no: this is the new gTLD application for the Bond University.

I went through the application to learn a little more about what the plan is for this TLD and you will find it below; but while I am here, it is my pleasure to say "hello" to the Bond University's Digital Marketing Manager whose first name is "James" ;-)

WHAT
This is an extract of the new gTLD application submitted to the ICANN:
The .bond gTLD will create a new generation gTLD serving the interests of end users by providing an authoritative Internet space where information, services and resources regarding Bond University’s degrees, courses and events will be closely controlled by Bond University Limited (Bond University). The majority of the anticipated domain name registrations in the .bond gTLD will be used to provide easier access to information for students and staff. A subset of domain names has the potential to be created and used for communicating and marketing the Bond University brand internationally, with internet users assured of brand authenticity.
The .bond gTLD will facilitate greater trust and assurance from internet users connecting with Bond University online, whilst still allowing convenient and efficient interaction.
Bond University’s mission and purpose of the proposed new gTLD share ICANN’s initiatives to promote public interest. Bond University is committed to contribute towards achieving such initiatives in line with ICANN’s Affirmation of Commitments, which includes:
  • consumer trust: the .bond gTLD registry will be operated in a centralised manner with a restrictive registration policy. Registration of domain names will only be available to Bond University and its affiliate entities, at this stage, which will provide added consumer trust that .bond domain names are trustworthy. As .bond domain names are subject to registration standards, policies and procedures under Bond University’s control, this eliminates the possibility of malicious conduct within the .bond domain space;
  • competition: the proposed new gTLD is not intended to instigate competition and consumer choice at the level of registration of domain names among prospective registrants. Instead it is anticipated to contribute to ICANN’s initiatives to promote public interest through its operation focused on promoting consumer trust. Increased trust in the .bond gTLD will drive existing and new top level domain (TLD) registry operators to make improvements in mechanisms to improve consumer trust of their TLDs; and
  • consumer choice: the proposed new gTLD will enable user-driven improvements and innovations assisting Bond University’s marketing efforts through its ability to create new second and third level domain names on demand. These names will provide the consumers with more choices for interacting with Bond University. As Bond University has effective control over the registration and use of domain names under .bond domain space, this will also contribute towards general service innovations on the internet.

    Given the restricted nature of the .bond gTLD, the projected number of registrations are likely to be limited. It is anticipated that about 40 domain names will be registered in the first year. However, over the next few years, the number of registrations is likely to increase to around 100 domain names as Bond University develops and implements new degrees and courses, services and marketing campaigns.

    Bond University does not intend to utilise Internationalized Domain Names (IDNs) at the second level initially. However, as the use of the .bond gTLD evolves, Bond University may wish to utilise IDNs to allow its current and future students to engage with .bond in their native language, creating a more positive user experience and encouraging diversity.

Thursday, June 22, 2017

Round 2 warm up ?

Is it this ICANN working Group's recent request to launch the next round of the ICANN new gTLD program in 2018 which is pushing service providers to publish more?

I noticed more publications recently from:
  1. The Dot Brand Observatory;
  2. Authentic Web Inc;
  3. A back-end registry provider.
Jovenet Consulting will be working with one single service provider for the the future round of the ICANN new gTLD program. If you are interested in working with us, read this. We also updated and simplified this offer.

Tuesday, June 20, 2017

Trust in the next new gTLD round

Potential new gTLD applicants are exposed prior to submitting their application, below is a suggestion to protect them from potential bad behaviors.

This is an email that I sent to an ICANN insider. I am myself a member of several working groups but I was not able to locate the right one to submit this suggestion. I received an answer with the right directions and it appears that this issue is already taken into account, which is a good thing for future applicants...if lobbyists and other ICANN insiders can't block this from being taken into account.

Email sent
Dear "Whoever", 
There is a suggestion that I would like to do for the next AGB* but I have no idea where I should submit it and if there is still time for this.
I faced this problem in round one and I strongly believe that it makes sense to consider it.
I think that new gTLD applicants should be able to submit their application before they have to choose a back-end registry provider. The reason for this is to avoid an idea of a TLD project to go in the ears of another applicant with deeper pockets.
New gTLD applicants are obliged to select a backend registry provider for their application to enter the ICANN validation process. Allowing them to submit without a backend registry (how: I don't know), would increase chances of the applicant to be able to finalize his project.
Trust/Confidentiality is an issue and an application that a backend registry provider will lose to another is just a word pronounced to other potential applicants. Whatever NDA is signed, an applicant is at risk when having to meet several backend registry providers to discuss his project.
It makes sense, for an applicant, to be able to meet with a backend registry, after ICANN has accepted his application. Before that is a high risk.


What is the idea?
The idea is to protect potential new gTLD applicants from speaking too loud and too early; an obligation when consulting potential partners to submit a new gTLD application. Of course, everyone is honest - we all know this - and I am not targeting back-end registry providers here but putting such a solution in place would:
  1. Limit the number of multiple new gTLD applications in the next round (unless it is decided that applications are validated on the basis of first come first served);
  2. Fasten the process to validate applications at ICANN.
If a new gTLD applicant can demonstrate upfront that his intention is to work with one "already ICANN accredited back-end Registry", can't he then contract with him after his application was validated by the ICANN?

Brokers: get prepared!


* "AGB" stands for Applicant Guidebook: the bible to submit a new gTLD application to ICANN.

.BRAND new gTLD Reports are updated once a month.

.BRAND new gTLD Reports are updated once a month.
Cick here !