.blog

From ICANNWiki
Jump to: navigation, search
Status: Delegated
Manager: Automattic
Registry: Knock Knock WHOIS There, LLC
Registry Backend: Nominet
Type: Generic
Category: Technology
nTLDStats
Registrations: 89,335
Parked Domains: 26,925
Parked Domain %: 30.14 %
Important Dates
Delegation: 18 May 2016
General Availability: 21 November 2016

More Information: NTLDStatsLogo.png

.blog is a new gTLD delegated to the Root Zone in ICANN's new gTLD expansion program on 18 May 2016.[1] The registry is managed by Automattic, operator of Wordpress. The company purchased Primer Nivel's application and won the auction for the domain, paying $19 million. ICANN approved the reassignment of .blog from Primer Nivel to Knock Knock WHOIS (Automattic) on April 29th, 2016. [2]

Aormer pplicants

  1. Radix (Personals TLD Inc.), partnering with ARI Registry Services for backend registry functioning. Radix has applied for 31 new gTLDs.[3][4]
  2. Top Level Domain Holdings Ltd., using its own Minds + Machines subsidiary for registry services. Blog is one of 68 applications that the company has filed on its own behalf. This applicant submitted a Public Interest Commitment, which can be downloaded here.
  3. Top Level Design, submitted 10 total applications.
  4. Afilias[5]
  5. BET Inc., John Kane of Afilias is listed as the contact person.
  6. Google (Charleston Road Registry Inc.), The search engine giant applied for 101 new gTLDs.[6]
  7. Donuts (Corn Shadow, LLC), Donuts applied for a total of 307 new gTLDs and invested $56 million just for application fees.[7] This applicant submitted a Public Interest Commitment, which can be downloaded here.
  8. Merchant Law Group LLP, Mr. Brendon James Ralfe is the main contact person for the company

Google

Google's application was issued a GAC Early Warning from the representative of Australia and GAC Chair, Heather Dryden. The warning system is noted as a strong recommendation on behalf of national governments to the ICANN Board that a given TLD application should be denied as it stands. Applicants are encouraged to work with objecting GAC members.[8]

The warning states that the applicant is "seeking exlcusive access to a common generic string .. that relates to a broad market sector," which Ms. Dryden notes could have unintended consequences and a negative impact on competition.[9]

Radix

Radix received a GAC Early Warning as an entire applicant, where each one of the applicants was flagged by the U.S. Government. This seems to be the only time a portfolio applicant had all of their applications warned. The issue does not deal with the technical capabilities or thematic content of their applications, but rather the inclusion of an email address associated with the US' Federal Bureau of Investigation. It seems that Radix included correspondence with this address as a recommendation with each of their applications.[10]

Name Collision Issues

In October 2013 ICANN released their final assessment and mitigation plan for the Name Collision issue that was facing the New gTLD program. On 18 November 2013, ICANN announced the applied-for strings that were eligible for an alternative path towards delegation that would allow applicants to proceed without waiting for further mitigation research and plans to be published. 25 strings, including .blog, were not eligible for the alternative path, and will have to wait for more plans to be published before continuing towards delegation.[11]

References

  1. Delegated Strings
  2. Wordpress Reveals it Bought .BLOG. DomainIncite. Retrieved 09 Jan 2016.
  3. Directi Invest Over $30 Million & Applies For 31 New gTLD’s: Including: .Law, .Web, .Bank, .Shop
  4. Technology
  5. Afilias Bringing Hundreds of New Top Level Domains to the Internet
  6. Online Marketing Firm fishbat Inc., Breaks Down the ICANN gTLD Announcement
  7. Donuts Inc eye popping list of 307 new top-level domains
  8. GAC Early Warning, NewgTLDS.ICANN.org Retrieved 25 Nov 2012
  9. Blog AU, GACweb.ICANN.org
  10. RadixReg. GACweb.ICANN.org Retrieved 27 Nov 2012
  11. Announcement 17 Nov 13, ICANN.org Retrieved 20 Feb 2014