<?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: Whois History Important Part of Domain Due Diligence</title>
	<atom:link href="http://domainnamewire.com/2009/05/28/whois-history-important-part-of-domain-due-diligence/feed/" rel="self" type="application/rss+xml" />
	<link>http://domainnamewire.com/2009/05/28/whois-history-important-part-of-domain-due-diligence/</link>
	<description>News and Views for the Domain Name Industry</description>
	<lastBuildDate>Sat, 20 Mar 2010 22:02:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew Allemann</title>
		<link>http://domainnamewire.com/2009/05/28/whois-history-important-part-of-domain-due-diligence/comment-page-1/#comment-414985</link>
		<dc:creator>Andrew Allemann</dc:creator>
		<pubDate>Mon, 01 Jun 2009 01:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=6538#comment-414985</guid>
		<description>Patrick, I appreciate all comments that are well-informed like yours.  The only ones I don&#039;t like are those that literally say something like &quot;your stupid&quot; :)</description>
		<content:encoded><![CDATA[<p>Patrick, I appreciate all comments that are well-informed like yours.  The only ones I don&#8217;t like are those that literally say something like &#8220;your stupid&#8221; <img src='http://domainnamewire.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick McDermott</title>
		<link>http://domainnamewire.com/2009/05/28/whois-history-important-part-of-domain-due-diligence/comment-page-1/#comment-414946</link>
		<dc:creator>Patrick McDermott</dc:creator>
		<pubDate>Sun, 31 May 2009 23:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=6538#comment-414946</guid>
		<description>&quot;I also don’t know that ICANN would let them limit access to that information, since they are required to provide ‘free access’.&quot;

Andrew,

I don&#039;t want to beat this horse to death and as you said your original reason for this blog post has nothing to do with the big left tuen it&#039;s made.

For the record I can appreciate having access to the WhoIs archives but I do hate to see it used against domainers in UDRPs just by virtue of someone owning lots of domains.

That said, the issue goes beyond someone&#039;s right to &quot;free access&quot; to WhoIs.

DT is actually compiling and selling that WhoIs data.

That is not just access.

Anyway lets get this topic back on track
and let Versign (or whomever) decide if what DT is doing violates their terms and if they want to do something about it.

I hope you&#039;ll continue blogging about the various DT tools you find useful without reservation despite my intrusive comments which I do hope you consider friendly participatory retorts.</description>
		<content:encoded><![CDATA[<p>&#8220;I also don’t know that ICANN would let them limit access to that information, since they are required to provide ‘free access’.&#8221;</p>
<p>Andrew,</p>
<p>I don&#8217;t want to beat this horse to death and as you said your original reason for this blog post has nothing to do with the big left tuen it&#8217;s made.</p>
<p>For the record I can appreciate having access to the WhoIs archives but I do hate to see it used against domainers in UDRPs just by virtue of someone owning lots of domains.</p>
<p>That said, the issue goes beyond someone&#8217;s right to &#8220;free access&#8221; to WhoIs.</p>
<p>DT is actually compiling and selling that WhoIs data.</p>
<p>That is not just access.</p>
<p>Anyway lets get this topic back on track<br />
and let Versign (or whomever) decide if what DT is doing violates their terms and if they want to do something about it.</p>
<p>I hope you&#8217;ll continue blogging about the various DT tools you find useful without reservation despite my intrusive comments which I do hope you consider friendly participatory retorts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Allemann</title>
		<link>http://domainnamewire.com/2009/05/28/whois-history-important-part-of-domain-due-diligence/comment-page-1/#comment-414864</link>
		<dc:creator>Andrew Allemann</dc:creator>
		<pubDate>Sun, 31 May 2009 20:52:59 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=6538#comment-414864</guid>
		<description>@ Dave Zan -

Right, what I&#039;m saying is I&#039;m not sure if ICANN would allow VeriSign to limit access to whois.  I think you&#039;re right, it&#039;s VeriSign who gets to decide whether DT violates &lt;em&gt;their&lt;/em&gt; terms.  But then you also have the registrars, which is where the actual registrant data is held in the &#039;thin whois&#039; model.  I also don&#039;t know that ICANN would let them limit access to that information, since they are required to provide &#039;free access&#039;.  My guess is it&#039;s never been directly addressed with ICANN, but I&#039;d love to hear from someone who may have some insight into that.</description>
		<content:encoded><![CDATA[<p>@ Dave Zan -</p>
<p>Right, what I&#8217;m saying is I&#8217;m not sure if ICANN would allow VeriSign to limit access to whois.  I think you&#8217;re right, it&#8217;s VeriSign who gets to decide whether DT violates <em>their</em> terms.  But then you also have the registrars, which is where the actual registrant data is held in the &#8216;thin whois&#8217; model.  I also don&#8217;t know that ICANN would let them limit access to that information, since they are required to provide &#8216;free access&#8217;.  My guess is it&#8217;s never been directly addressed with ICANN, but I&#8217;d love to hear from someone who may have some insight into that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Zan</title>
		<link>http://domainnamewire.com/2009/05/28/whois-history-important-part-of-domain-due-diligence/comment-page-1/#comment-414747</link>
		<dc:creator>Dave Zan</dc:creator>
		<pubDate>Sun, 31 May 2009 14:48:35 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=6538#comment-414747</guid>
		<description>&lt;blockquote&gt;I have no idea if VeriSign is allowed to limit access to whois&lt;/blockquote&gt;

Andrew, also from VeriSign&#039;s TOS as Patrick mentioned:

&lt;blockquote&gt;VeriSign reserves the right to restrict your access to the Whois database in its sole discretion to ensure operational stability. VeriSign may restrict or terminate your access to the Whois database for failure to abide by these terms of use.&lt;/blockquote&gt;

I could be wrong, but DT doesn&#039;t exactly use &quot;electronic processes that are high-volume and automated&quot; like, say, what Verio did in their later suit by Register.com. Besides, it&#039;s VeriSign who gets to decide whether DT violates their terms or not, despite how others interpret VeriSign&#039;s TOS.</description>
		<content:encoded><![CDATA[<blockquote><p>I have no idea if VeriSign is allowed to limit access to whois</p></blockquote>
<p>Andrew, also from VeriSign&#8217;s TOS as Patrick mentioned:</p>
<blockquote><p>VeriSign reserves the right to restrict your access to the Whois database in its sole discretion to ensure operational stability. VeriSign may restrict or terminate your access to the Whois database for failure to abide by these terms of use.</p></blockquote>
<p>I could be wrong, but DT doesn&#8217;t exactly use &#8220;electronic processes that are high-volume and automated&#8221; like, say, what Verio did in their later suit by Register.com. Besides, it&#8217;s VeriSign who gets to decide whether DT violates their terms or not, despite how others interpret VeriSign&#8217;s TOS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Allemann</title>
		<link>http://domainnamewire.com/2009/05/28/whois-history-important-part-of-domain-due-diligence/comment-page-1/#comment-414009</link>
		<dc:creator>Andrew Allemann</dc:creator>
		<pubDate>Sat, 30 May 2009 03:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=6538#comment-414009</guid>
		<description>Patrick, the idea behind this post was how DT&#039;s historical whois can protect you from buying a stolen domain.  So there&#039;s one benefit we wouldn&#039;t have without DT.  I also use historical whois to find sploggers who are ripping off my content and hiding behind whois privacy.  They sometimes had an open whois record in the past.

I have no idea if VeriSign is allowed to limit access to whois, and if so what constitutes &quot;high volume&quot; or &quot;automated&quot;.  I do know that registrars have to provide &#039;free&#039; access to whois information.  I haven&#039;t read any of their contracts with ICANN.  If VeriSign had a problem with this, they would have addressed it.  My guess is open access to whois helps VeriSign, as many people who use whois data register domain names based on it.</description>
		<content:encoded><![CDATA[<p>Patrick, the idea behind this post was how DT&#8217;s historical whois can protect you from buying a stolen domain.  So there&#8217;s one benefit we wouldn&#8217;t have without DT.  I also use historical whois to find sploggers who are ripping off my content and hiding behind whois privacy.  They sometimes had an open whois record in the past.</p>
<p>I have no idea if VeriSign is allowed to limit access to whois, and if so what constitutes &#8220;high volume&#8221; or &#8220;automated&#8221;.  I do know that registrars have to provide &#8216;free&#8217; access to whois information.  I haven&#8217;t read any of their contracts with ICANN.  If VeriSign had a problem with this, they would have addressed it.  My guess is open access to whois helps VeriSign, as many people who use whois data register domain names based on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick McDermott</title>
		<link>http://domainnamewire.com/2009/05/28/whois-history-important-part-of-domain-due-diligence/comment-page-1/#comment-414006</link>
		<dc:creator>Patrick McDermott</dc:creator>
		<pubDate>Sat, 30 May 2009 03:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=6538#comment-414006</guid>
		<description>&quot;If you visit Internic WhoIs and type in
“DomainNameWire.com? which I did , you’ll receive this notice:&quot;
--

I left off this link by error:
http://snurl.com/WhoIsDNW</description>
		<content:encoded><![CDATA[<p>&#8220;If you visit Internic WhoIs and type in<br />
“DomainNameWire.com? which I did , you’ll receive this notice:&#8221;<br />
&#8211;</p>
<p>I left off this link by error:<br />
<a href="http://snurl.com/WhoIsDNW" rel="nofollow">http://snurl.com/WhoIsDNW</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick McDermott</title>
		<link>http://domainnamewire.com/2009/05/28/whois-history-important-part-of-domain-due-diligence/comment-page-1/#comment-414004</link>
		<dc:creator>Patrick McDermott</dc:creator>
		<pubDate>Sat, 30 May 2009 03:13:19 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=6538#comment-414004</guid>
		<description>&quot;But I don’t think DT violates the spirit of what whois was meant to be — a way to know who owns a particular domain name.&quot;


Andrew,

DT is doing a lot more than letting you &quot;know who owns a particular domain name&quot;.

That might be a true statement for domains registered at their Registrar(s).

But they have gone far beyond that.

They are compiling WhoIs data across the board.

I only used GoDaddy as an example. Every Registrar that I have seen has the same terms and conditions as Godaddy.

GoDaddy didn&#039;t create those terms.

If you visit Internic WhoIs and type in 
&quot;DomainNameWire.com? which I did , you&#039;ll receive this notice:

Terms of Use excerpts:

&quot;TERMS OF USE: You are not authorized to access or query our Whois database through the use of electronic processes that are high-volume and automated except as reasonably necessary to register domain names or modify existing registrations&quot;
--
&quot;the Data in VeriSign Global Registry 
Services&#039;...Whois database is provided ...
information purposes only,...&quot;
----
&quot;By submitting a Whois query, you agree to abide by the following terms of use:
You agree that..The compilation, repackaging, dissemination or other use of this Data is expressly prohibited without the prior written consent of VeriSign.&quot;
--

Andrew,

These are Verisisn&#039;s terms not GoDaddy&#039;s.

Do you really believe DT obtained &quot;written consent&quot;?
--

&quot;Many of the systems you and I use in day-to-day domaining rely on automated querying of whois&quot;

Yes Andrew, but there is a BIG difference.

You are not performing such activity with the purpose of  compiling, repackaging, or disseminating the WhoIs info for commercial profit.
--

&quot;I would also argue that domain tools has been good for the domain industry&quot;

For the domain industry or for them?

Fire can keep you warm of burn you to death.

Water is needed for life, fun to swim in but can also drown a four year old child.

Yes, DT&#039;s WhoIs info service is good if you want to find out what domains Frank Schilling owns or anyone else&#039;s domain portfolio.

But nefarious parties that want to take your domain(s) can also use the info against you
in UDRP or court filings.

DT does not distinguish between good usage of
the WhoIs data or bad usage.
--

&quot;...but I think we’d be worse off without it.&quot;

Only if you&#039;re lucky.</description>
		<content:encoded><![CDATA[<p>&#8220;But I don’t think DT violates the spirit of what whois was meant to be — a way to know who owns a particular domain name.&#8221;</p>
<p>Andrew,</p>
<p>DT is doing a lot more than letting you &#8220;know who owns a particular domain name&#8221;.</p>
<p>That might be a true statement for domains registered at their Registrar(s).</p>
<p>But they have gone far beyond that.</p>
<p>They are compiling WhoIs data across the board.</p>
<p>I only used GoDaddy as an example. Every Registrar that I have seen has the same terms and conditions as Godaddy.</p>
<p>GoDaddy didn&#8217;t create those terms.</p>
<p>If you visit Internic WhoIs and type in<br />
&#8220;DomainNameWire.com? which I did , you&#8217;ll receive this notice:</p>
<p>Terms of Use excerpts:</p>
<p>&#8220;TERMS OF USE: You are not authorized to access or query our Whois database through the use of electronic processes that are high-volume and automated except as reasonably necessary to register domain names or modify existing registrations&#8221;<br />
&#8211;<br />
&#8220;the Data in VeriSign Global Registry<br />
Services&#8217;&#8230;Whois database is provided &#8230;<br />
information purposes only,&#8230;&#8221;<br />
&#8212;-<br />
&#8220;By submitting a Whois query, you agree to abide by the following terms of use:<br />
You agree that..The compilation, repackaging, dissemination or other use of this Data is expressly prohibited without the prior written consent of VeriSign.&#8221;<br />
&#8211;</p>
<p>Andrew,</p>
<p>These are Verisisn&#8217;s terms not GoDaddy&#8217;s.</p>
<p>Do you really believe DT obtained &#8220;written consent&#8221;?<br />
&#8211;</p>
<p>&#8220;Many of the systems you and I use in day-to-day domaining rely on automated querying of whois&#8221;</p>
<p>Yes Andrew, but there is a BIG difference.</p>
<p>You are not performing such activity with the purpose of  compiling, repackaging, or disseminating the WhoIs info for commercial profit.<br />
&#8211;</p>
<p>&#8220;I would also argue that domain tools has been good for the domain industry&#8221;</p>
<p>For the domain industry or for them?</p>
<p>Fire can keep you warm of burn you to death.</p>
<p>Water is needed for life, fun to swim in but can also drown a four year old child.</p>
<p>Yes, DT&#8217;s WhoIs info service is good if you want to find out what domains Frank Schilling owns or anyone else&#8217;s domain portfolio.</p>
<p>But nefarious parties that want to take your domain(s) can also use the info against you<br />
in UDRP or court filings.</p>
<p>DT does not distinguish between good usage of<br />
the WhoIs data or bad usage.<br />
&#8211;</p>
<p>&#8220;&#8230;but I think we’d be worse off without it.&#8221;</p>
<p>Only if you&#8217;re lucky.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
