Are Existing gTLD Registrations Suffering From New gTLDs?

Could .net be one of a number of gTLDs suffering from the success of new gTLDs? As of 30 June 2014, Verisign noted in their Domain Name Industry Brief there were 15.2 million .net domains under management (DUM). But according to the latest figures provided by RegistrarStats, there are now 14,998,404 DUMs.

Could .net be one of a number of gTLDs suffering from the success of new gTLDs? As of 30 June 2014, Verisign noted in their Domain Name Industry Brief there were 15.2 million .net domains under management (DUM). But according to the latest figures provided by RegistrarStats, there are now 14,998,404 DUMs.Domain Incite were the first to report on .net DUMs seeming to be suffering. But looking at other gTLDs it seems it is not the only one to see a decline in registration numbers over the past 12 months or so. The .biz, .pro, .tel and .mobi gTLDs, as well as the ccTLD for the United States (.us), all appear to have all suffered declines in registration numbers over the last 12 months. The .biz, .tel and .mobi TLDs seem to have been particularly hard hit. The .org gTLD seems to have plateaued its DUMs and not seen any significant increase for close to two years.While some of the older gTLDs have been haemorrhaging DUMs for some time. For example, .info has also seen a significant decline in DUMs from a peak of over 8 million around December 2011 to around 4.8 million now. And .name DUMs peaked around 2009 and have been in freefall ever since.But it seems the decline in registrations for .net, .biz, .us and .mobi, and maybe others, has coincided with the release of new gTLDs.

ICANN: .name Registry Agreement Renewal

ICANN logoPurpose (Brief): ICANN is posting today for public comment Verisign’s proposed agreement for renewal of the 2007 .name Registry Agreement. This proposal is a result of discussions between ICANN and VeriSign, and will be considered by the ICANN Board after public comment

ICANN logoPurpose (Brief): ICANN is posting today for public comment Verisign’s proposed agreement for renewal of the 2007 .name Registry Agreement. This proposal is a result of discussions between ICANN and VeriSign, and will be considered by the ICANN Board after public comment. The current agreement will expire on 15 August 2012. Public comment may be submitted through 02 August 2012.

Public Comment Box Link: www.icann.org/en/news/public-comment/name-renewal-2012-03jul12-en.htm

Forum Announcement: Comment Period Opens on 3 July 2012

This ICANN announcement was sourced from:
www.icann.org/en/news/announcements/announcement-03jul12-en.htm

ICANN: Public Comment: Numbers & Hyphens in .NAME Domain Names

ICANN logoICANN is today opening a public comment period on a proposed amendment from VeriSign Information Services, Inc. to Appendices 6 and 11 of the .NAME Registry Agreement

ICANN logoICANN is today opening a public comment period on a proposed amendment from VeriSign Information Services, Inc. to Appendices 6 and 11 of the .NAME Registry Agreement.

On 25 August 2010, ICANN posted for public information a request submitted by VeriSign through the Registry Services Evaluation Process to offer numeric-only and numbers & hyphens domain names under .NAME. The VeriSign proposal is available at icann.org/en/registries/rsep/#2010010.

As provided for by existing consensus policy, ICANN has undertaken a preliminary determination on whether the proposal might raise significant competition, security or stability issues. ICANN’s determination [PDF, 80 KB] is that the proposal does not raise such issues in .NAME.

Implementation of the proposal would require an amendment to Appendices 6 and 11 of the .NAME Registry Agreement. A copy of the proposed amendment is available here: icann.org/en/tlds/agreements/name/proposed-name-amendment-15sep10-en.pdf [PDF, 55 KB].

Comments on the proposed amendment submitted to name-numbers-and-hyphens-domains@icann.org will be considered until 16 Oct 2010 23:59 UTC. Comments may be viewed at forum.icann.org/lists/name-numbers-and-hyphens-domains/.

This ICANN announcement was sourced from:
icann.org/en/announcements/announcement-3-16sep10-en.htm