<?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: Monitoring Whois Searches</title>
	<atom:link href="http://www.elliotsblog.com/monitoring-whois-searches-9474/feed" rel="self" type="application/rss+xml" />
	<link>http://www.elliotsblog.com/monitoring-whois-searches-9474</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>Thu, 09 Feb 2012 21:08:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stephen Douglas</title>
		<link>http://www.elliotsblog.com/monitoring-whois-searches-9474#comment-15947</link>
		<dc:creator>Stephen Douglas</dc:creator>
		<pubDate>Fri, 20 Nov 2009 14:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/?p=4004#comment-15947</guid>
		<description>Hi El Silver,

Your article brings us back to the story I&#039;m writing about Domain Industry scandals.  Doesn&#039;t this article you wrote jog your memory of NetSol&#039;s buying every domain searched for within their system and then offering to sell it BACK to the person later for the maximum price (I think it&#039;s $35 a year)? Their official statement was &quot;we&#039;re protecting the domain for you so it isn&#039;t lost in domain tasting.&quot;

Your readers can either post on my current blog article asking for stories and opinions on the &quot;worst domain industry scandal&quot;, regardless if it was blown up in the media or not. I just need a real name and their stories. The submitters can remain anonymous if they request it. They can also tell their story by emailing me if they prefer (successclick [at] gmail.com).

my blog: http://www.successclick.com

thx for your help on this!</description>
		<content:encoded><![CDATA[<p>Hi El Silver,</p>
<p>Your article brings us back to the story I&#8217;m writing about Domain Industry scandals.  Doesn&#8217;t this article you wrote jog your memory of NetSol&#8217;s buying every domain searched for within their system and then offering to sell it BACK to the person later for the maximum price (I think it&#8217;s $35 a year)? Their official statement was &#8220;we&#8217;re protecting the domain for you so it isn&#8217;t lost in domain tasting.&#8221;</p>
<p>Your readers can either post on my current blog article asking for stories and opinions on the &#8220;worst domain industry scandal&#8221;, regardless if it was blown up in the media or not. I just need a real name and their stories. The submitters can remain anonymous if they request it. They can also tell their story by emailing me if they prefer (successclick [at] gmail.com).</p>
<p>my blog: <a href="http://www.successclick.com" rel="nofollow">http://www.successclick.com</a></p>
<p>thx for your help on this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dluzional</title>
		<link>http://www.elliotsblog.com/monitoring-whois-searches-9474#comment-15945</link>
		<dc:creator>Dluzional</dc:creator>
		<pubDate>Fri, 20 Nov 2009 11:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/?p=4004#comment-15945</guid>
		<description>When one uses a Whois provider, there&#039;s usually some terms involved in governing that use isn&#039;t there?

They may be violating their own TOS or Privacy policy&#039;s

The usual Whois terminology reads like this:

you agree to these terms of usage and limitations of warranty. In particular, you agree not to use this data to allow, enable, or otherwise make possible,
dissemination or collection of this data, in part or in its entirety, for any purpose, such as the transmission of unsolicited advertising and and solicitations of any kind, including spam. You further agree not to use this data to enable high volume, automated or robotic electronic
processes designed to collect or compile this data for any purpose, including mining this data for your own personal or commercial purposes.

This seems geared for the &quot;user&quot; only but from a little bit of research the whois provider has to have an agreement with ICANN or someone in order to solicit to you.
That agreement wherever it is seems to never be displayed anywhere.

Seems that each Whois provider creates their own terms which circumvents the baseline rules for the whois, but doesn&#039;t have any reference whatsoever to those rules/terms/policy.

Regardless of who the provider is, it&#039;s a practise that goes on time and time again, and I doubt there is anything that anyone can do about it.</description>
		<content:encoded><![CDATA[<p>When one uses a Whois provider, there&#8217;s usually some terms involved in governing that use isn&#8217;t there?</p>
<p>They may be violating their own TOS or Privacy policy&#8217;s</p>
<p>The usual Whois terminology reads like this:</p>
<p>you agree to these terms of usage and limitations of warranty. In particular, you agree not to use this data to allow, enable, or otherwise make possible,<br />
dissemination or collection of this data, in part or in its entirety, for any purpose, such as the transmission of unsolicited advertising and and solicitations of any kind, including spam. You further agree not to use this data to enable high volume, automated or robotic electronic<br />
processes designed to collect or compile this data for any purpose, including mining this data for your own personal or commercial purposes.</p>
<p>This seems geared for the &#8220;user&#8221; only but from a little bit of research the whois provider has to have an agreement with ICANN or someone in order to solicit to you.<br />
That agreement wherever it is seems to never be displayed anywhere.</p>
<p>Seems that each Whois provider creates their own terms which circumvents the baseline rules for the whois, but doesn&#8217;t have any reference whatsoever to those rules/terms/policy.</p>
<p>Regardless of who the provider is, it&#8217;s a practise that goes on time and time again, and I doubt there is anything that anyone can do about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.elliotsblog.com/monitoring-whois-searches-9474#comment-15942</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Fri, 20 Nov 2009 08:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/?p=4004#comment-15942</guid>
		<description>It&#039;s call spam, welcome to the internet!</description>
		<content:encoded><![CDATA[<p>It&#8217;s call spam, welcome to the internet!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.elliotsblog.com/monitoring-whois-searches-9474#comment-15935</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Thu, 19 Nov 2009 22:42:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/?p=4004#comment-15935</guid>
		<description>Real shame that your friend is a domain investor and is using NSI. . . he should know better. :)</description>
		<content:encoded><![CDATA[<p>Real shame that your friend is a domain investor and is using NSI. . . he should know better. <img src='http://www.elliotsblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.elliotsblog.com/monitoring-whois-searches-9474#comment-15928</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 19 Nov 2009 19:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliotsblog.com/?p=4004#comment-15928</guid>
		<description>...or perhaps how Network Solutions shows other people what whois searches have been performed.  Not a big fan of that, either.</description>
		<content:encoded><![CDATA[<p>&#8230;or perhaps how Network Solutions shows other people what whois searches have been performed.  Not a big fan of that, either.</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 3/10 queries in 0.005 seconds using memcached

Served from: www.elliotsblog.com @ 2012-02-09 17:19:01 -->
