<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: GoDaddy Allowing Obvious TM Violations For Sale At TDNAM</title>
	<atom:link href="http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 14:15:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Taking the risk with TM domains, Not for me! &#124; Domain News</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5467</link>
		<dc:creator>Taking the risk with TM domains, Not for me! &#124; Domain News</dc:creator>
		<pubDate>Sun, 01 Jun 2008 20:24:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5467</guid>
		<description>[...] was a recent post on&#160;TheDomains.com blog about TDNAM.com offering TM domains for sale recently and I wanted to add in my 2 cents about [...]</description>
		<content:encoded><![CDATA[<p>[...] was a recent post on&nbsp;TheDomains.com blog about TDNAM.com offering TM domains for sale recently and I wanted to add in my 2 cents about [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5393</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 28 May 2008 16:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5393</guid>
		<description>Richard

We understand the daily drop lists are published by Verisign and not controlled by any drop service.

We know that the pool &quot;hot list&quot; is based on the number of backorder requests.  However the list is only 20 names so certainly someone could go in and make sure disneymovies.com or similar clearly infringing name is not included on the &quot;Hot List&quot;

The fact that the &quot;Hot List&quot; names are the most backordered ones, means there are a lot of people backordering the domain, not just the one cilent trading customers marks.

Likewise NameJet.com could block those names appearing on their &quot;most backordered page&quot;.

Yes the domains will still drop but there is no need to advertise it.

As far as Godaddy is concerned, the original post by Mr. Castello, talked about not drop names but domains that were offered for sale by their owners that were clear trademark infringements and made the point, that they should self police and have a policy of not allowing such domains to be sold through their system.

I would urge pool.com to adopt such a policy for their resale system.</description>
		<content:encoded><![CDATA[<p>Richard</p>
<p>We understand the daily drop lists are published by Verisign and not controlled by any drop service.</p>
<p>We know that the pool &#8220;hot list&#8221; is based on the number of backorder requests.  However the list is only 20 names so certainly someone could go in and make sure disneymovies.com or similar clearly infringing name is not included on the &#8220;Hot List&#8221;</p>
<p>The fact that the &#8220;Hot List&#8221; names are the most backordered ones, means there are a lot of people backordering the domain, not just the one cilent trading customers marks.</p>
<p>Likewise NameJet.com could block those names appearing on their &#8220;most backordered page&#8221;.</p>
<p>Yes the domains will still drop but there is no need to advertise it.</p>
<p>As far as Godaddy is concerned, the original post by Mr. Castello, talked about not drop names but domains that were offered for sale by their owners that were clear trademark infringements and made the point, that they should self police and have a policy of not allowing such domains to be sold through their system.</p>
<p>I would urge pool.com to adopt such a policy for their resale system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Schreier</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5392</link>
		<dc:creator>Richard Schreier</dc:creator>
		<pubDate>Wed, 28 May 2008 16:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5392</guid>
		<description>I think there are a couple of points that should be clarified for everyone.  

First, the daily &quot;list&quot; of deleting domains for com/net is published by Verisign and is subsequently made available to potential customers through websites like Pool.com as well as the other drop catchers.  It&#039;s a public list.  And ALL buyers have access to it including those who have legitimate trademark interests.

Second, Pool.com (and I suspect the same is true for the other drop catchers) publish a short list, or sometimes referred to as a hotlist, that often reflects the most popular domains as represented by the preferences of their customers.  With a few exceptions, we only attempt to grab domains for which our customers have placed backorders.

Third, the issue is not whether Pool.com or GoDaddy or anyone in a position to register domain names should allow the registration of domain names that may be contested by a trademark holder.  Organizations like Pool.com or GoDaddy do not have the legal right to arbitrate trademark issues.

And finally, there are many organizations that offer brand protection services to their customers.  Some are clients of Pool.com and they WANT to see when their clients marks appear in a domain drop so they can proactively manage the possible results.  The same would be true for any domain freely available that is registered through any commercail registrar.</description>
		<content:encoded><![CDATA[<p>I think there are a couple of points that should be clarified for everyone.  </p>
<p>First, the daily &#8220;list&#8221; of deleting domains for com/net is published by Verisign and is subsequently made available to potential customers through websites like Pool.com as well as the other drop catchers.  It&#8217;s a public list.  And ALL buyers have access to it including those who have legitimate trademark interests.</p>
<p>Second, Pool.com (and I suspect the same is true for the other drop catchers) publish a short list, or sometimes referred to as a hotlist, that often reflects the most popular domains as represented by the preferences of their customers.  With a few exceptions, we only attempt to grab domains for which our customers have placed backorders.</p>
<p>Third, the issue is not whether Pool.com or GoDaddy or anyone in a position to register domain names should allow the registration of domain names that may be contested by a trademark holder.  Organizations like Pool.com or GoDaddy do not have the legal right to arbitrate trademark issues.</p>
<p>And finally, there are many organizations that offer brand protection services to their customers.  Some are clients of Pool.com and they WANT to see when their clients marks appear in a domain drop so they can proactively manage the possible results.  The same would be true for any domain freely available that is registered through any commercail registrar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taking the risk with TM domains, Not for me! : Dot Weekly</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5389</link>
		<dc:creator>Taking the risk with TM domains, Not for me! : Dot Weekly</dc:creator>
		<pubDate>Wed, 28 May 2008 10:12:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5389</guid>
		<description>[...] was a recent post on&#160;TheDomains.com blog about TDNAM.com offering TM domains for sale recently and I wanted to add in my 2 cents about [...]</description>
		<content:encoded><![CDATA[<p>[...] was a recent post on&nbsp;TheDomains.com blog about TDNAM.com offering TM domains for sale recently and I wanted to add in my 2 cents about [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David J Castello</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5388</link>
		<dc:creator>David J Castello</dc:creator>
		<pubDate>Wed, 28 May 2008 04:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5388</guid>
		<description>You made an excellent point about non-domainers seeing a name like DisneyStudio.com for sale on TDNAM.com and believing it must be OK to buy names like that because of GoDaddy&#039;s worldwide branding.</description>
		<content:encoded><![CDATA[<p>You made an excellent point about non-domainers seeing a name like DisneyStudio.com for sale on TDNAM.com and believing it must be OK to buy names like that because of GoDaddy&#8217;s worldwide branding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5386</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 28 May 2008 02:25:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5386</guid>
		<description>David

Nice coverage although I could have lived without the picture.

After we posted on this, I watched the Indy 500 which was basically a 3 1/2 hour commercial for Godaddy, which strikes at the heart of my comment regarding their appeal to non-domainers</description>
		<content:encoded><![CDATA[<p>David</p>
<p>Nice coverage although I could have lived without the picture.</p>
<p>After we posted on this, I watched the Indy 500 which was basically a 3 1/2 hour commercial for Godaddy, which strikes at the heart of my comment regarding their appeal to non-domainers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David J Castello</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5385</link>
		<dc:creator>David J Castello</dc:creator>
		<pubDate>Wed, 28 May 2008 00:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5385</guid>
		<description>Ron Jackson posted about it:
http://www.dnjournal.com/archive/lowdown/2008/dailyposts/05-27-08.htm</description>
		<content:encoded><![CDATA[<p>Ron Jackson posted about it:<br />
<a href="http://www.dnjournal.com/archive/lowdown/2008/dailyposts/05-27-08.htm" rel="nofollow">http://www.dnjournal.com/archive/lowdown/2008/dailyposts/05-27-08.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MsDomainer</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5384</link>
		<dc:creator>MsDomainer</dc:creator>
		<pubDate>Tue, 27 May 2008 23:19:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5384</guid>
		<description>These are companies that can sniff out and snap up all the dropping premium domains, so no one will ever convince me that OBVIOUS TM domains can&#039;t be identified and kicked out.

Yes, these obvious TM domains ought to be snapped up and, yes, given to the company holding the TM. To buy or sell an obvious TM infringing domain is both illegal and ethically wrong.

Selling a known TM domain for profit is especially regugnant; perhaps if the registrar (who should know better) were required to refund the buyer  in case of a UDRP, you&#039;d probably see this problem solved and fast.

On second thought, perhaps these cybersquatters and greedy domain registrars (who hide behind legalese TOS) deserve each other.</description>
		<content:encoded><![CDATA[<p>These are companies that can sniff out and snap up all the dropping premium domains, so no one will ever convince me that OBVIOUS TM domains can&#8217;t be identified and kicked out.</p>
<p>Yes, these obvious TM domains ought to be snapped up and, yes, given to the company holding the TM. To buy or sell an obvious TM infringing domain is both illegal and ethically wrong.</p>
<p>Selling a known TM domain for profit is especially regugnant; perhaps if the registrar (who should know better) were required to refund the buyer  in case of a UDRP, you&#8217;d probably see this problem solved and fast.</p>
<p>On second thought, perhaps these cybersquatters and greedy domain registrars (who hide behind legalese TOS) deserve each other.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5383</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 27 May 2008 21:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5383</guid>
		<description>I agree close call on blueray but not bang on.

I didn&#039;t buy it or bid on it</description>
		<content:encoded><![CDATA[<p>I agree close call on blueray but not bang on.</p>
<p>I didn&#8217;t buy it or bid on it</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Tonetti</title>
		<link>http://www.thedomains.com/2008/05/24/godaddy-allowing-obvious-tm-violations-for-sale-at-tdnam/comment-page-1/#comment-5382</link>
		<dc:creator>Jeffrey Tonetti</dc:creator>
		<pubDate>Tue, 27 May 2008 20:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=603#comment-5382</guid>
		<description>Blu-Ray is the trademark......So I may be wrong on that one, but still a close call</description>
		<content:encoded><![CDATA[<p>Blu-Ray is the trademark&#8230;&#8230;So I may be wrong on that one, but still a close call</p>
]]></content:encoded>
	</item>
</channel>
</rss>
