<?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>Netsearch Direct &#187; Domain Parking</title>
	<atom:link href="http://www.netsearchdirect.com/blog/tag/domain-parking/feed" rel="self" type="application/rss+xml" />
	<link>http://www.netsearchdirect.com</link>
	<description>Define your web presence.</description>
	<lastBuildDate>Sun, 05 Feb 2012 14:03:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Typosquating &#8211; Dell Weighs In</title>
		<link>http://www.netsearchdirect.com/blog/seo/typosquating-dell-weighs-in?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=typosquating-dell-weighs-in</link>
		<comments>http://www.netsearchdirect.com/blog/seo/typosquating-dell-weighs-in#comments</comments>
		<pubDate>Mon, 03 Dec 2007 17:00:24 +0000</pubDate>
		<dc:creator>Rob Sterling</dc:creator>
				<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[Domain Parking]]></category>
		<category><![CDATA[Domian Tasting]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[MSN]]></category>
		<category><![CDATA[typosquating]]></category>
		<category><![CDATA[Yahoo]]></category>

		<guid isPermaLink="false">http://www.netsearchdirect.com/blog/seo/typosquating-dell-weighs-in.html</guid>
		<description><![CDATA[This is one of my hot topics that I follow. I have been watching for well over a year, maybe two, and it is building momentum and getting more press on a regular basis. My theory is that ad serving provider, Googleâ„¢ and Yahoo, have huge liability exposure to this as they profit directly from [...]]]></description>
			<content:encoded><![CDATA[<p>This is one of my hot  topics that I follow.  I have been watching for well over a year, maybe two, and  it is building momentum and getting more press on a regular basis.</p>
<p>My theory is that ad  serving provider, Googleâ„¢ and Yahoo, have huge liability exposure to this as  they profit directly from the sale of ads on these sites.<br />
<strong> Dell Takes Cybersquatters to Court</strong><br />
<em> PC Maker Alleges Domain Registrars Profited on &#8216;Confusingly Similar&#8217; Names</em></p>
<p><em>By Brian Krebs<br />
washingtonpost.com Staff Writer<br />
Wednesday, November 28, 2007; 4:06 PM</em></p>
<p><em>Personal computer giant Dell Inc. is pursuing a major &#8220;cybersquatting&#8221; lawsuit against several companies that buy and sell Web site addresses, alleging that the entities earned millions of dollars from Internet traffic intended for Dell and dozens of other Fortune 500 companies.</em></p>
<p><a href="http://www.washingtonpost.com/wp-dyn/content/article/2007/11/28/AR2007112801679.html?hpid=moreheadlines" title="http://www.washingtonpost.com/wp-dyn/content/article/2007/11/28/AR2007112801679.html?hpid=moreheadlines">Dell  Takes Cybersquatters to Court</a><br />
Washington Post &#8211; United  States<br />
The Washington Post examined  <strong>Google&#8217;s</strong> connection to the  <strong>typosquatting</strong> industry in a story  published in April 2006. <strong>Google</strong>  maintains that it specifically <strong>&#8230;</strong><br />
<a href="http://news.google.com/news?hl=en&amp;ncl=http://www.washingtonpost.com/wp-dyn/content/article/2007/11/28/AR2007112801679.html%3Fhpid%3Dmoreheadlines" title="http://news.google.com/news?hl=en&amp;ncl=http://www.washingtonpost.com/wp-dyn/content/article/2007/11/28/AR2007112801679.html?hpid=moreheadlines">See all stories on this topic</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.netsearchdirect.com/blog/seo/typosquating-dell-weighs-in/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

