<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

	<channel>

	<title>&#45; CircleID</title>
	<link>https://www.circleid.com/blogs/</link>
	<description>Postings from  on CircleID</description>
	<dc:language>en</dc:language>
	<dc:rights>Copyright 2026, unless where otherwise noted.</dc:rights>
	<dc:date>2026-04-30T19:14:00+00:00</dc:date>

	
	<item>
		<title> How to Turn a Closed Generic gTLD Into a Restricted One (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20140611_the_case_for_turning_closed_generic_tlds_into_restricted_tlds</guid>
		<link>https://circleid.com/posts20140611_the_case_for_turning_closed_generic_tlds_into_restricted_tlds</link>
		<description><![CDATA[As the New gTLD Program has rolled out over the course of the past few years, the Internet Corporation for Assigned Names and Numbers (ICANN) has made a number of program changes along the way. One of these changes disallows closed, generic gTLD applications, such as Amazon's application for .BOOK. Now, applicants for closed generics must decide how to proceed: whether to open their generic strings to the public, limit registrations to a defined portion of the public, withdraw the application, or sell it. <a href="https://circleid.com/posts20140611_the_case_for_turning_closed_generic_tlds_into_restricted_tlds">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>