<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Domainerss &#187; idns</title>
	<atom:link href="http://www.domainerss.com/blog/tag/idns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.domainerss.com/blog</link>
	<description>Hand-Picked Best Of The Domainer Blogs</description>
	<lastBuildDate>Fri, 03 Feb 2012 22:02:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>IDNs: The Next Horizon for GeoDomain Investors</title>
		<link>http://www.domainerss.com/blog/2010/01/idns-the-next-horizon-for-geodomain-investors/</link>
		<comments>http://www.domainerss.com/blog/2010/01/idns-the-next-horizon-for-geodomain-investors/#comments</comments>
		<pubDate>Wed, 27 Jan 2010 15:29:20 +0000</pubDate>
		<dc:creator>Andrew Allemann</dc:creator>
				<category><![CDATA[Feeder]]></category>
		<category><![CDATA[Domain Services]]></category>
		<category><![CDATA[idns]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[by Aaron Krawitz, Gary Males &#38; Patrick Carleton
[Editor's note: this is a guest article about the potential of IDN geo domain names.] 
We’ve long been believers in GeoDomains and continue to be on the lookout for new and lucrative niches, which i...]]></description>
			<content:encoded><![CDATA[<p><span style="background-color:yellow">Link To Full Story:</span> <a href="http://domainnamewire.com/2010/01/27/idns-the-next-horizon-for-geodomain-investors/" target="blank">Domain Name Wire </a></p>

<p><strong>by Aaron Krawitz, Gary Males &amp; Patrick Carleton</strong></p>
<p>[<em>Editor's note: this is a guest article about the potential of IDN geo domain names.</em>] </p>
<p>We’ve long been believers in GeoDomains and continue to be on the lookout for new and lucrative niches, which is why we have each individually made substantial investments in IDN GeoDomains.</p>
<p>With the fog of uncertainty finally lifting over IDNs, now is the ideal time for for geo investors to stake a claim in IDNs where the window of opportunity is quickly closing.</p>
<p>For years, antagonists of non-latin IDNs have focused on the premise that the part to the right of the dot was still in English.  Let’s face it, [non-English] dot [English &quot;com&quot;] never made any sense, and that was the number one reason why many didn’t take a closer look.   </p>
<p>But a few weeks ago, this all changed, as VeriSign finally <a href="http://idnblog.com/2009/12/03/exclusive-qa-chuck-gomes-verisign/">showed its hand</a> and put to bed the rumors of how these half IDNs were going to operate.  In a brief, but game changing interview, Vice President of Policy and Compliance for VeriSign Information Services (VIS) Chuck Gomes spoke of how an existing [non-English] dot [English &quot;com&quot;] could be unlocked so that the domain owner also owns the rights to the same domain but with a localized extension (i.e [the same non-English domain] dot [non-English &quot;com&quot;]).   For example, the owner of the Japanese domain, ニューオーリンズ.com (New Orleans), would also hold the rights to the same keyword with a non-English extension in the corresponding local language, such as ニューオーリンズ.コム.  The characters “コム” are the familiar way to express “com” in Japanese.</p>
<p><em>So what does this mean for GeoDomainers?</em></p>
<p>ICANN’s IDN program aims to deliver on many promises, and the majority of these promises are to native speaking countries. IDNs intrinsically breed nationalistic pride in having one’s own language represented in a domain name, so it makes complete sense that GeoDomains of native cities/towns in their respective languages will be warmly welcomed.</p>
<p><em>What should we make of the competition, the new IDN ccTLDs?</em></p>
<p>Russia’s new .рф extension is a prime example, which, like the existing Japanese ccTLD are reserving all geos for government use.  You can bet there will be mildly interesting informational sites put up on these geos for IDN ccTLDs, but they will be void of any commercial use.  This will clear the way for IDN dot com names to dominate.</p>
<p><em>Where are the opportunities?</em></p>
<p>With only 1 million IDNs registered today, there is ample opportunity, and most old-time IDNers haven’t bought geos with a population under 100,000!</p>
<p>We are still in the early days of the IDN market and geos can be picked up for bargain prices on droplists or even occasionally at reg fee.</p>
<p><em>Aaron Krawitz of <a href="http://idnblog.com">IDNBlog</a> and Gary Males of <a href="http://www.idndemystified.com/">IDNDemystified</a> co-own  IDNDroplist, IDNTools and IDNNewsletter.  Patrick Carleton is Executive Directory of <a href="http://www.associatedcities.com/">Associated Cities</a>.</em></p>
<p></p>

	<hr noshade style="margin:0;height:1px">
	<p>© DomainNameWire.com 2009. </p><p><strong>Review and rate domain name parking companies at</strong>  <a href="http://www.parkingjudge.com">Parking Judge</a>.</p> 

<p>Related posts:<ol><li><a href="http://domainnamewire.com/2009/12/10/telnic-wants-to-release-tel-idns/" rel="bookmark" title="Permanent Link: Telnic Wants to Release .Tel IDNs">Telnic Wants to Release .Tel IDNs</a></li><li><a href="http://domainnamewire.com/2009/02/24/how-the-japanese-avoid-domain-names/" rel="bookmark" title="Permanent Link: How The Japanese Avoid Domain Names">How The Japanese Avoid Domain Names</a></li><li><a href="http://domainnamewire.com/2008/10/20/risks-remain-for-idn-investors/" rel="bookmark" title="Permanent Link: Risks Remain for IDN Investors">Risks Remain for IDN Investors</a></li></ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.domainerss.com/blog/2010/01/idns-the-next-horizon-for-geodomain-investors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

