<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: GoDaddy Response to Domain Deletion</title>
	<link>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/</link>
	<description>An Internet Project</description>
	<pubDate>Thu, 20 Nov 2008 15:21:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Domain Name Wire &#187; Blog Archive &#187; GoDaddy Makes Reporting Invalid Whois Easy - The Domain Industry's News Source</title>
		<link>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-117</link>
		<dc:creator>Domain Name Wire &#187; Blog Archive &#187; GoDaddy Makes Reporting Invalid Whois Easy - The Domain Industry's News Source</dc:creator>
		<pubDate>Tue, 13 Mar 2007 15:41:39 +0000</pubDate>
		<guid>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-117</guid>
		<description>[...] other news related to this issue, I came across an article by someone who called GoDaddy support to inquire about the FamilyAlbum.com case: The GoDaddy [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] other news related to this issue, I came across an article by someone who called GoDaddy support to inquire about the FamilyAlbum.com case: The GoDaddy [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-57</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Tue, 06 Mar 2007 17:37:09 +0000</pubDate>
		<guid>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-57</guid>
		<description>@Andrew - Yeah - I understand, but, as I mentioned in my post, these could be two separate issues.

The following is what I get from Internic Whois:
   Domain Name: FAMILYALBUM.COM
   Registrar: GO DADDY SOFTWARE, INC.
   Whois Server: whois.godaddy.com
   Referral URL: http://registrar.godaddy.com
   Name Server: PARK35.SECURESERVER.NET
   Name Server: PARK36.SECURESERVER.NET
   Status: clientRenewProhibited
   Status: clientTransferProhibited
   Status: clientUpdateProhibited
   Status: clientDeleteProhibited
   Updated Date: 05-feb-2007
   Creation Date: 28-may-2002
   Expiration Date: 28-may-2008

I am guessing you are looking at the Updated Date to determine the transfer?</description>
		<content:encoded><![CDATA[<p>@Andrew - Yeah - I understand, but, as I mentioned in my post, these could be two separate issues.</p>
<p>The following is what I get from Internic Whois:<br />
   Domain Name: FAMILYALBUM.COM<br />
   Registrar: GO DADDY SOFTWARE, INC.<br />
   Whois Server: whois.godaddy.com<br />
   Referral URL: <a href="http://registrar.godaddy.com">http://registrar.godaddy.com</a><br />
   Name Server: PARK35.SECURESERVER.NET<br />
   Name Server: PARK36.SECURESERVER.NET<br />
   Status: clientRenewProhibited<br />
   Status: clientTransferProhibited<br />
   Status: clientUpdateProhibited<br />
   Status: clientDeleteProhibited<br />
   Updated Date: 05-feb-2007<br />
   Creation Date: 28-may-2002<br />
   Expiration Date: 28-may-2008</p>
<p>I am guessing you are looking at the Updated Date to determine the transfer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-55</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 06 Mar 2007 16:09:25 +0000</pubDate>
		<guid>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-55</guid>
		<description>Thanks for going the extra mile and calling GoDaddy.  Unfortunately, I think the customer service rep gave a line of B.S.  The situation they are referring to must have been another case.  If you look up the Whois records on FamilyAlbum.com you can verify that this incident happened within the past couple months.  Honestly, it adds more fuel to the fire that they told you this story.</description>
		<content:encoded><![CDATA[<p>Thanks for going the extra mile and calling GoDaddy.  Unfortunately, I think the customer service rep gave a line of B.S.  The situation they are referring to must have been another case.  If you look up the Whois records on FamilyAlbum.com you can verify that this incident happened within the past couple months.  Honestly, it adds more fuel to the fire that they told you this story.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: webjourneyman</title>
		<link>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-42</link>
		<dc:creator>webjourneyman</dc:creator>
		<pubDate>Sun, 04 Mar 2007 13:33:27 +0000</pubDate>
		<guid>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-42</guid>
		<description>Hey, thanks for the comment. I don´t know what inspires such distrust in Godaddy, so far I´ve trusted them with more than a dosen names. Perhaps its that hyper oversell tactic. They really are boarderline sometimes, anyone who has some experience can see that sometimes they are almost trying to fool the customer. I was fooled f.eks. when I three times bought three names together because then I got free anonymousity, or so I thought. It was not untill I recomended godaddy because of this offer that I learned the anon registration is free only for a year. If I´m not careful it will effectively triple the price of my domain names on a yearly basis.</description>
		<content:encoded><![CDATA[<p>Hey, thanks for the comment. I don´t know what inspires such distrust in Godaddy, so far I´ve trusted them with more than a dosen names. Perhaps its that hyper oversell tactic. They really are boarderline sometimes, anyone who has some experience can see that sometimes they are almost trying to fool the customer. I was fooled f.eks. when I three times bought three names together because then I got free anonymousity, or so I thought. It was not untill I recomended godaddy because of this offer that I learned the anon registration is free only for a year. If I´m not careful it will effectively triple the price of my domain names on a yearly basis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Wilsdon</title>
		<link>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-41</link>
		<dc:creator>Nick Wilsdon</dc:creator>
		<pubDate>Sun, 04 Mar 2007 11:54:02 +0000</pubDate>
		<guid>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-41</guid>
		<description>&#62;When he did not respond in 10 days, per ICANN rules and regulations they were required to delete the account.

Hi Mark,

I'm afraid what GoDaddy told here wasn't exactly true. They do *not* mandate that the Registrar/Reseller deletes the domain if the WHOIS information is incorrect. In fact Tucows, choose to suspend the domain for the duration of the registration period. They would then only sell it onto a new customer after 80 days (40 days is the usual redemption period before domains are released into the public pool again). 

I have copied the relevent section of the ICANN rules for you to look at:


http://www.icann.org/announcements/advisory-03apr03.htm

Subsection 3.7.7.2 of the Registrar Accreditation Agreement does not require a registrar to cancel a registration in the event a customer fails to respond within 15 days. The accreditation agreement’s approach of requiring the registrar to retain the right to cancel if the customer fails to respond in 15 days, but not requiring the registrar to exercise that right is intended to give the registrar the flexibility to use good judgment to determine what action should be taken upon a customer’s failure to respond to an inquiry about a Whois inaccuracy. 

So you see here, ICANN do not demand cancellation in this rule, but they give the Registrar/Reseller the right to do it. What the Registrar/Reseller does in the event of inaccurate information was meant to be left to their 'good judgment'. In GoDaddy's case they choose to cancel the domain immediately and resell it to a third party - make of that what you will. 

It's important to realise that this ICANN regulation was originally intended to be used to stop online fraud and cyber-squatting. In these cases false WHOIS info prevented the authorities tracking them down. ICANN gave the Registrars/Resellers the right to cancel the domain to give them some extra teeth here to force these fraudsters to put in their correct information. 

IMHO their intention was not to target legitimate web sites and owners. 

Anyway, great blog - I've added you to my reading list ;) Take care!</description>
		<content:encoded><![CDATA[<p>&gt;When he did not respond in 10 days, per ICANN rules and regulations they were required to delete the account.</p>
<p>Hi Mark,</p>
<p>I&#8217;m afraid what GoDaddy told here wasn&#8217;t exactly true. They do *not* mandate that the Registrar/Reseller deletes the domain if the WHOIS information is incorrect. In fact Tucows, choose to suspend the domain for the duration of the registration period. They would then only sell it onto a new customer after 80 days (40 days is the usual redemption period before domains are released into the public pool again). </p>
<p>I have copied the relevent section of the ICANN rules for you to look at:</p>
<p><a href="http://www.icann.org/announcements/advisory-03apr03.htm">http://www.icann.org/announcements/advisory-03apr03.htm</a></p>
<p>Subsection 3.7.7.2 of the Registrar Accreditation Agreement does not require a registrar to cancel a registration in the event a customer fails to respond within 15 days. The accreditation agreement’s approach of requiring the registrar to retain the right to cancel if the customer fails to respond in 15 days, but not requiring the registrar to exercise that right is intended to give the registrar the flexibility to use good judgment to determine what action should be taken upon a customer’s failure to respond to an inquiry about a Whois inaccuracy. </p>
<p>So you see here, ICANN do not demand cancellation in this rule, but they give the Registrar/Reseller the right to do it. What the Registrar/Reseller does in the event of inaccurate information was meant to be left to their &#8216;good judgment&#8217;. In GoDaddy&#8217;s case they choose to cancel the domain immediately and resell it to a third party - make of that what you will. </p>
<p>It&#8217;s important to realise that this ICANN regulation was originally intended to be used to stop online fraud and cyber-squatting. In these cases false WHOIS info prevented the authorities tracking them down. ICANN gave the Registrars/Resellers the right to cancel the domain to give them some extra teeth here to force these fraudsters to put in their correct information. </p>
<p>IMHO their intention was not to target legitimate web sites and owners. </p>
<p>Anyway, great blog - I&#8217;ve added you to my reading list <img src='http://www.bloglyne.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> Take care!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: robwatts</title>
		<link>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-40</link>
		<dc:creator>robwatts</dc:creator>
		<pubDate>Sun, 04 Mar 2007 08:05:50 +0000</pubDate>
		<guid>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-40</guid>
		<description>Nice perspective Mark.

I happen to think that regardless of the situation, GoDaddy moved way too fast. They also appear to be suggesting that the new owner is nothing short of a ground gliding rattlesnake.

In situations like this I like to believe in the concept of Karma. Lets hope that this ass gets his just rewards and that GoDaddy tighten up procedures to ensure it never happens again.

Personally, I wouldn't use them in a month of sunny Sundays.</description>
		<content:encoded><![CDATA[<p>Nice perspective Mark.</p>
<p>I happen to think that regardless of the situation, GoDaddy moved way too fast. They also appear to be suggesting that the new owner is nothing short of a ground gliding rattlesnake.</p>
<p>In situations like this I like to believe in the concept of Karma. Lets hope that this ass gets his just rewards and that GoDaddy tighten up procedures to ensure it never happens again.</p>
<p>Personally, I wouldn&#8217;t use them in a month of sunny Sundays.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-39</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Sun, 04 Mar 2007 07:24:13 +0000</pubDate>
		<guid>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-39</guid>
		<description>Yeah - you are not kidding there :)</description>
		<content:encoded><![CDATA[<p>Yeah - you are not kidding there <img src='http://www.bloglyne.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LGR</title>
		<link>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-38</link>
		<dc:creator>LGR</dc:creator>
		<pubDate>Sun, 04 Mar 2007 05:10:32 +0000</pubDate>
		<guid>http://www.bloglyne.com/2007/03/03/godaddy-response-to-domain-deletion/#comment-38</guid>
		<description>It is a good reminder that people should make sure their email addresses are up to date on the domain names.</description>
		<content:encoded><![CDATA[<p>It is a good reminder that people should make sure their email addresses are up to date on the domain names.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
