<?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>Product Domains &#187; techcrunch</title>
	<atom:link href="http://www.productdomains.com/tag/techcrunch/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.productdomains.com</link>
	<description></description>
	<lastBuildDate>Mon, 10 Oct 2011 13:20:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Is TechCrunch Cybersquatting And Redirecting A Twitter Typo Domain?</title>
		<link>http://www.productdomains.com/2009/10/01/is-techcrunch-cybersquatting-and-redirecting-a-twitter-typo-domain/</link>
		<comments>http://www.productdomains.com/2009/10/01/is-techcrunch-cybersquatting-and-redirecting-a-twitter-typo-domain/#comments</comments>
		<pubDate>Thu, 01 Oct 2009 17:01:01 +0000</pubDate>
		<dc:creator>Product Domains</dc:creator>
				<category><![CDATA[All]]></category>
		<category><![CDATA[cybersquatting]]></category>
		<category><![CDATA[techcrunch]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[typo domain]]></category>

		<guid isPermaLink="false">http://www.productdomains.com/?p=186</guid>
		<description><![CDATA[	<style type="text/css">
		</style>
Typo domains come in a variety of forms but one of the most common besides misspellings is &#8220;www&#8221; added to the actual domain such as: wwwtwitter.com notice that it&#8217;s all one word, which is the domain that is redirecting to TechCrunch. According to a whois lookup the domain is registered GoDaddy, created 11/04/2007 with an [...]]]></description>
			<content:encoded><![CDATA[	<style type="text/css">
		</style><p><img class="alignnone size-full wp-image-185" title="techcrunch-twitter-typo" src="http://www.productdomains.com/wp-content/uploads/2009/10/techcrunch-twitter-typo.jpg" alt="techcrunch-twitter-typo" width="600" height="300" /></p>
<p>Typo domains come in a variety of forms but one of the most common besides misspellings is &#8220;www&#8221; added to the actual domain such as: <a href="http://www.wwwtwitter.com" target="_blank">wwwtwitter.com</a> notice that it&#8217;s all one word, which is the domain that is redirecting to TechCrunch. According to a <a href="http://whois.domaintools.com/wwwtwitter.com" target="_blank">whois lookup</a> the domain is registered GoDaddy, created 11/04/2007 with an expiration of 11/04/2014. It also has Domains by Proxy privacy protection and is also sitting on GoDaddy&#8217;s name servers meaning that the redirect is setup within the owners GoDaddy domain control panel.</p>
<p>The term twitter is trademarked and should be easy for Twitter to get via UDRP, but the question remains. Does TechCrunch, who frequently blogs about the company own this domain or is it someone else that owns the domain and is doing the redirecting?</p>
<p>Either way it doesn&#8217;t reflect well on domainers.</p>
<p><strong>Update:</strong><br />
Six days after this was published TechCrunch wrote <a href="http://www.techcrunch.com/2009/10/07/wwwtwitter-com-best-website-ever/" target="_blank">their own post</a> on the topic.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.productdomains.com/2009/10/01/is-techcrunch-cybersquatting-and-redirecting-a-twitter-typo-domain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HP Launches DreamScreen, Doesn&#8217;t Own DreamScreen.com</title>
		<link>http://www.productdomains.com/2009/09/23/hp-launches-dreamscreen-doesnt-own-dreamscreen-com/</link>
		<comments>http://www.productdomains.com/2009/09/23/hp-launches-dreamscreen-doesnt-own-dreamscreen-com/#comments</comments>
		<pubDate>Thu, 24 Sep 2009 02:01:14 +0000</pubDate>
		<dc:creator>Product Domains</dc:creator>
				<category><![CDATA[All]]></category>
		<category><![CDATA[dreamscreen]]></category>
		<category><![CDATA[hp]]></category>
		<category><![CDATA[techcrunch]]></category>

		<guid isPermaLink="false">http://www.productdomains.com/?p=125</guid>
		<description><![CDATA[	<style type="text/css">
		</style>
Was reading TechCrunch and came across their review of the new HP DreamScreen that others have compared to the elusive Apple Tablet. Needless to say thier review isn&#8217;t very positive about the product and after doing a quick whois look up HP doesn&#8217;t own the domain DreamScreen.com either. You&#8217;d think HP would learn from the [...]]]></description>
			<content:encoded><![CDATA[	<style type="text/css">
		</style><p><img class="alignnone size-full wp-image-126" title="dreamscreen" src="http://www.productdomains.com/wp-content/uploads/2009/09/dreamscreen.jpg" alt="dreamscreen" width="600" height="300" /></p>
<p>Was reading <a href="http://www.techcrunch.com/2009/09/23/the-hp-dreamscreen-not-so-dreamy/" target="_blank">TechCrunch</a> and came across their review of the new <a href="http://h71036.www7.hp.com/hho/us/en/pclc/articles/series-dreamscreen.html" target="_blank">HP DreamScreen</a> that others have compared to the elusive Apple Tablet. Needless to say thier review isn&#8217;t very positive about the product and after doing a quick <a href="http://whois.domaintools.com/dreamscreen.com" target="_blank">whois look up</a> HP doesn&#8217;t own the domain DreamScreen.com either. You&#8217;d think HP would learn from the mistakes of their competitor Dell after the whole <a href="http://www.thedomains.com/2009/04/13/dell-refused-to-spend-750-a-month-on-adamocom/" target="_blank">Adamo.com debacle</a> a few months ago.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.productdomains.com/2009/09/23/hp-launches-dreamscreen-doesnt-own-dreamscreen-com/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

