<?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: Argument to Remove Registrant Search Tool</title>
	<atom:link href="http://www.elliotsblog.com/argument-to-remove-registrant-search-tool/feed" rel="self" type="application/rss+xml" />
	<link>http://www.elliotsblog.com/argument-to-remove-registrant-search-tool</link>
	<description>Domain blog featuring domain investing strategy, domain valuation, and domain development commentary from Elliot Silver, founder of Top Notch Domains, LLC.</description>
	<lastBuildDate>Fri, 10 Feb 2012 01:30:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Search</title>
		<link>http://www.elliotsblog.com/argument-to-remove-registrant-search-tool#comment-8118</link>
		<dc:creator>Search</dc:creator>
		<pubDate>Sat, 10 Jan 2009 22:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/index.php/2007/11/21/argument-to-remove-registrant-search-tool/#comment-8118</guid>
		<description>Search your &quot;full name&quot; in Google to see how domaintools is exposing domainers to fraud and other possible scams and making false accusations about how many domains we own. Domaintools sucks big time and is breaking the law with these false accusations about domain owners.</description>
		<content:encoded><![CDATA[<p>Search your &#8220;full name&#8221; in Google to see how domaintools is exposing domainers to fraud and other possible scams and making false accusations about how many domains we own. Domaintools sucks big time and is breaking the law with these false accusations about domain owners.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.elliotsblog.com/argument-to-remove-registrant-search-tool#comment-8116</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Sat, 10 Jan 2009 21:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/index.php/2007/11/21/argument-to-remove-registrant-search-tool/#comment-8116</guid>
		<description>Time to revisit this Elliot with a new article. Domaintools hacking is causing huge privacy concerns for domain owners, would be nice to know if we request our names removed from the site are they under any legal obligation to do so or not.

Also does anyone know who we should contact at Google to complain about the hacked customer domain owner information being indexed.

I am in the process also of raising the issue with Godaddy Legal counsel. They need to protect domain owners better.</description>
		<content:encoded><![CDATA[<p>Time to revisit this Elliot with a new article. Domaintools hacking is causing huge privacy concerns for domain owners, would be nice to know if we request our names removed from the site are they under any legal obligation to do so or not.</p>
<p>Also does anyone know who we should contact at Google to complain about the hacked customer domain owner information being indexed.</p>
<p>I am in the process also of raising the issue with Godaddy Legal counsel. They need to protect domain owners better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wildhippy</title>
		<link>http://www.elliotsblog.com/argument-to-remove-registrant-search-tool#comment-757</link>
		<dc:creator>wildhippy</dc:creator>
		<pubDate>Wed, 21 Nov 2007 23:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/index.php/2007/11/21/argument-to-remove-registrant-search-tool/#comment-757</guid>
		<description>&lt;p&gt;This discussion brings up an interesting technical problem, and one which Jay&#039;s tool or any other tool like it has to address.  The problem is, given a set of data points about an individual or company, in what ways and to what extent do two sets have to be similar in order to establish identity?  There would presumably need to be some weighting of certain data points over others.  But the idea of &quot;identity&quot; is a somewhat fuzzy one when it comes to whois records, and it is not obvious how &quot;sensitive&quot; a tool like Jay&#039;s needs to be to variations on personal data.  On the one had, you don&#039;t want the tool to miss too many domains for minor reasons (like misspellings or a changed phone number), but on the other hand, you really don&#039;t want it identifying too many domains as owned by the same person.  Perhaps there should be a confidence score associated with each domain grouped together -- how confident the tool is that the domain is owned by the same entity.&lt;/p&gt;
&lt;p&gt;In my own case, registrant search claims that I own about 34 domains, whereas I really own about 12 (I&#039;m not a domainer.)  I have used some of my information to register domains on behalf of clients etc, so that is presumably where some of this data comes from.  I also have a relatively common name.      I&#039;m sure Jay has people working on calibrating this tool.&lt;/p&gt;


&lt;strong&gt;***UPDATED BY ELLIOT***&lt;/strong&gt;

Also, as I understand it, the tool also counts some prior registrations that were in the database.  Maybe you don&#039;t own some of those names anymore?
</description>
		<content:encoded><![CDATA[<p>This discussion brings up an interesting technical problem, and one which Jay&#8217;s tool or any other tool like it has to address.  The problem is, given a set of data points about an individual or company, in what ways and to what extent do two sets have to be similar in order to establish identity?  There would presumably need to be some weighting of certain data points over others.  But the idea of &#8220;identity&#8221; is a somewhat fuzzy one when it comes to whois records, and it is not obvious how &#8220;sensitive&#8221; a tool like Jay&#8217;s needs to be to variations on personal data.  On the one had, you don&#8217;t want the tool to miss too many domains for minor reasons (like misspellings or a changed phone number), but on the other hand, you really don&#8217;t want it identifying too many domains as owned by the same person.  Perhaps there should be a confidence score associated with each domain grouped together &#8212; how confident the tool is that the domain is owned by the same entity.</p>
<p>In my own case, registrant search claims that I own about 34 domains, whereas I really own about 12 (I&#8217;m not a domainer.)  I have used some of my information to register domains on behalf of clients etc, so that is presumably where some of this data comes from.  I also have a relatively common name.      I&#8217;m sure Jay has people working on calibrating this tool.</p>
<p><strong>***UPDATED BY ELLIOT***</strong></p>
<p>Also, as I understand it, the tool also counts some prior registrations that were in the database.  Maybe you don&#8217;t own some of those names anymore?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ms Domainer</title>
		<link>http://www.elliotsblog.com/argument-to-remove-registrant-search-tool#comment-756</link>
		<dc:creator>Ms Domainer</dc:creator>
		<pubDate>Wed, 21 Nov 2007 22:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/index.php/2007/11/21/argument-to-remove-registrant-search-tool/#comment-756</guid>
		<description>&lt;p&gt;On the other hand, the victim could make a claim that since the domain is registered in the TM holder&#039;s name, then that domain should be transferred to the victim&#039;s account.&lt;/p&gt;
&lt;p&gt;A WIPO claim could be filed and sent to the perp&#039;s account, and when he/she doesn&#039;t respond, the victim would win, no? &lt;/p&gt;
&lt;p&gt;Google would have a great case here.&lt;/p&gt;
&lt;p&gt;If anything, Jay&#039;s tool ought to be enhanced to include email addresses as an important distinguishing field. Instead of saying, &quot;Mr. Pibbs owns at least 120 other domains,&quot; the message could say, &quot;XXXXX@XXXX.com owns at least 120 other domains.&quot; Thus, in a search by the victim (Google, in this case), they would know immediately that this isn&#039;t their email address and could pursue the transfer of the domain to their account.    &lt;/p&gt;
&lt;p&gt;Whether Jay or someone else develops this tool, dissenters are not likely to stop its further development and implementation.&lt;/p&gt;
&lt;p&gt;That genie left the bottle long ago, I&#039;m afraid.&lt;/p&gt;
&lt;p&gt;It&#039;s just a matter of who develops the tool and how it is used. And Jay seems like a straight arrow fellow who shares many of your concerns about how the tool could hurt domainers. But instead of beating up the messenger, maybe it&#039;s time to look inward on how one does business and then come up with ideas on how the tool could be developed into a positive way to enhance the reputation of this business, which, quite frankly, is viewed by outsiders in the same light as phishing and pharming.&lt;/p&gt;
&lt;p&gt;Best,&lt;/p&gt;
&lt;p&gt;Ms Domainer&lt;/p&gt;


&lt;strong&gt;***UPDATED BY ELLIOT***&lt;/strong&gt;

Jay&#039;s tool does that because you can look up by email address, city, state, company name....etc... you can search for just about anything. 
 
All I am saying is that I would hate to have questionable names appear to be registered by my company, since someone could compile a list using a company name.  Although you could flesh it out, that would take far too much time.  It would be a shame to see a list of a company&#039;s domain names include a name that isn&#039;t theirs, but was registered in their name by an unauthorized party. </description>
		<content:encoded><![CDATA[<p>On the other hand, the victim could make a claim that since the domain is registered in the TM holder&#8217;s name, then that domain should be transferred to the victim&#8217;s account.</p>
<p>A WIPO claim could be filed and sent to the perp&#8217;s account, and when he/she doesn&#8217;t respond, the victim would win, no? </p>
<p>Google would have a great case here.</p>
<p>If anything, Jay&#8217;s tool ought to be enhanced to include email addresses as an important distinguishing field. Instead of saying, &#8220;Mr. Pibbs owns at least 120 other domains,&#8221; the message could say, &#8220;XXXXX@XXXX.com owns at least 120 other domains.&#8221; Thus, in a search by the victim (Google, in this case), they would know immediately that this isn&#8217;t their email address and could pursue the transfer of the domain to their account.    </p>
<p>Whether Jay or someone else develops this tool, dissenters are not likely to stop its further development and implementation.</p>
<p>That genie left the bottle long ago, I&#8217;m afraid.</p>
<p>It&#8217;s just a matter of who develops the tool and how it is used. And Jay seems like a straight arrow fellow who shares many of your concerns about how the tool could hurt domainers. But instead of beating up the messenger, maybe it&#8217;s time to look inward on how one does business and then come up with ideas on how the tool could be developed into a positive way to enhance the reputation of this business, which, quite frankly, is viewed by outsiders in the same light as phishing and pharming.</p>
<p>Best,</p>
<p>Ms Domainer</p>
<p><strong>***UPDATED BY ELLIOT***</strong></p>
<p>Jay&#8217;s tool does that because you can look up by email address, city, state, company name&#8230;.etc&#8230; you can search for just about anything. </p>
<p>All I am saying is that I would hate to have questionable names appear to be registered by my company, since someone could compile a list using a company name.  Although you could flesh it out, that would take far too much time.  It would be a shame to see a list of a company&#8217;s domain names include a name that isn&#8217;t theirs, but was registered in their name by an unauthorized party.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sahar Sarid</title>
		<link>http://www.elliotsblog.com/argument-to-remove-registrant-search-tool#comment-744</link>
		<dc:creator>Sahar Sarid</dc:creator>
		<pubDate>Wed, 21 Nov 2007 16:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/index.php/2007/11/21/argument-to-remove-registrant-search-tool/#comment-744</guid>
		<description>Great observation Elliot. Nice.</description>
		<content:encoded><![CDATA[<p>Great observation Elliot. Nice.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic (Feed is rejected)
Page Caching using disk: enhanced
Database Caching 4/10 queries in 0.005 seconds using memcached

Served from: www.elliotsblog.com @ 2012-02-09 20:38:39 -->
