<?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: Is GoDaddy violating ICANN’s transfer policy?</title>
	<atom:link href="http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/feed/" rel="self" type="application/rss+xml" />
	<link>http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/</link>
	<description>News and Views for the Domain Name Industry</description>
	<lastBuildDate>Mon, 15 Mar 2010 13:14:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ED</title>
		<link>http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/comment-page-1/#comment-461816</link>
		<dc:creator>ED</dc:creator>
		<pubDate>Sun, 16 Aug 2009 23:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/#comment-461816</guid>
		<description>2009 and this is STILL an issue. Everyone needs o keep an eye out for this.</description>
		<content:encoded><![CDATA[<p>2009 and this is STILL an issue. Everyone needs o keep an eye out for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/comment-page-1/#comment-2306</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Tue, 25 Apr 2006 13:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/#comment-2306</guid>
		<description>You may recall I tried to take advantage of a $4.00 RegisterFly transfer promotion and had 58 names blocked.  RegisterFly then kept the cash in their holding account!

I called and emailed GoDaddy several times and eventually agreed to disagree.  Next time I&#039;ll try the president too!  Well done, Editor, for your perseverance on this issue.



</description>
		<content:encoded><![CDATA[<p>You may recall I tried to take advantage of a $4.00 RegisterFly transfer promotion and had 58 names blocked.  RegisterFly then kept the cash in their holding account!</p>
<p>I called and emailed GoDaddy several times and eventually agreed to disagree.  Next time I&#8217;ll try the president too!  Well done, Editor, for your perseverance on this issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: max</title>
		<link>http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/comment-page-1/#comment-2202</link>
		<dc:creator>max</dc:creator>
		<pubDate>Fri, 21 Apr 2006 17:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/#comment-2202</guid>
		<description>GODaddy, Network Solutions, and many other registrars also violate another issue;

They make you renew your domain prior to a transfer, this is a violation according to ICANN. This question is posted at the ICANN website;

www.icann.org/compliance/


My domain name has just expired. Can my registrar require me to pay for a renewal before I can transfer to a new registrar?

No. Your new registrar of choice can initiate a transfer request on an expired domain name once they receive the required authorization from you. Expiration or nonrenewal of a domain name is not a valid reason for denial of a transfer request.

Note that if the registrar has already begun the deletion process on the domain name and its status shows it to be within a 30-day Redemption Grace Period, the name must be .restored. by your current registrar before it can be transferred. 

Registrars MUST place a domain in active status if the registrant chooses to transfer, even after a domain is expired.

</description>
		<content:encoded><![CDATA[<p>GODaddy, Network Solutions, and many other registrars also violate another issue;</p>
<p>They make you renew your domain prior to a transfer, this is a violation according to ICANN. This question is posted at the ICANN website;</p>
<p><a href="http://www.icann.org/compliance/" rel="nofollow">http://www.icann.org/compliance/</a></p>
<p>My domain name has just expired. Can my registrar require me to pay for a renewal before I can transfer to a new registrar?</p>
<p>No. Your new registrar of choice can initiate a transfer request on an expired domain name once they receive the required authorization from you. Expiration or nonrenewal of a domain name is not a valid reason for denial of a transfer request.</p>
<p>Note that if the registrar has already begun the deletion process on the domain name and its status shows it to be within a 30-day Redemption Grace Period, the name must be .restored. by your current registrar before it can be transferred. </p>
<p>Registrars MUST place a domain in active status if the registrant chooses to transfer, even after a domain is expired.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Editor</title>
		<link>http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/comment-page-1/#comment-2148</link>
		<dc:creator>Editor</dc:creator>
		<pubDate>Fri, 14 Apr 2006 02:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/#comment-2148</guid>
		<description>Dave, thanks for the post.  I don&#039;t see anything about the transfer denials in the link you sent...</description>
		<content:encoded><![CDATA[<p>Dave, thanks for the post.  I don&#8217;t see anything about the transfer denials in the link you sent&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Zan</title>
		<link>http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/comment-page-1/#comment-2147</link>
		<dc:creator>Dave Zan</dc:creator>
		<pubDate>Thu, 13 Apr 2006 22:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/#comment-2147</guid>
		<description>The WHOIS thing is actually already being addressed:

http://icann.org/announcements/announcement-18jan06.htm

One person actually complained to ICANN about this. A few days later, someone from GD apologized to the customer for the &quot;mistake&quot;, and told him to resume moving out.

GD and other registrars may &quot;force&quot; registrants to agree to whatever&#039;s stated in their service agreements. But ICANN still has the final say.</description>
		<content:encoded><![CDATA[<p>The WHOIS thing is actually already being addressed:</p>
<p><a href="http://icann.org/announcements/announcement-18jan06.htm" rel="nofollow">http://icann.org/announcements/announcement-18jan06.htm</a></p>
<p>One person actually complained to ICANN about this. A few days later, someone from GD apologized to the customer for the &#8220;mistake&#8221;, and told him to resume moving out.</p>
<p>GD and other registrars may &#8220;force&#8221; registrants to agree to whatever&#8217;s stated in their service agreements. But ICANN still has the final say.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Editor</title>
		<link>http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/comment-page-1/#comment-2146</link>
		<dc:creator>Editor</dc:creator>
		<pubDate>Wed, 12 Apr 2006 13:50:35 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/#comment-2146</guid>
		<description>Interesting viewpoint, mannyd.  I&#039;ve never heard anyone that thought &quot;initial registration period&quot; means the period after changes are made to contact data...interesting thought.

With regards to GoDaddy&#039;s size, being big doesn&#039;t relieve you from your duty to serve your customers fairly.

Don&#039;t get me wrong, I&#039;m a fan of GoDaddy and have over 100 domains there.  But I think this issue needs to be addressed.  I&#039;ll try to get to the bottom of it at Domain Roundtable next week since reps of both ICANN and GoDaddy will be there.</description>
		<content:encoded><![CDATA[<p>Interesting viewpoint, mannyd.  I&#8217;ve never heard anyone that thought &#8220;initial registration period&#8221; means the period after changes are made to contact data&#8230;interesting thought.</p>
<p>With regards to GoDaddy&#8217;s size, being big doesn&#8217;t relieve you from your duty to serve your customers fairly.</p>
<p>Don&#8217;t get me wrong, I&#8217;m a fan of GoDaddy and have over 100 domains there.  But I think this issue needs to be addressed.  I&#8217;ll try to get to the bottom of it at Domain Roundtable next week since reps of both ICANN and GoDaddy will be there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mannyd</title>
		<link>http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/comment-page-1/#comment-2145</link>
		<dc:creator>mannyd</dc:creator>
		<pubDate>Wed, 12 Apr 2006 06:06:09 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2006/04/11/is-godaddy-violating-icann%e2%80%99s-transfer-policy/#comment-2145</guid>
		<description>I wish ICAAN would actually address the impications of changing the whois information. It would clarify this whole transfer situation. It is up to your take however. 

ICANN Transfer Policy Section 3. Obligations of the Registrar of Record

A domain name is in the first 60 days of an initial registration period.

To me, that means whenever you update the registration information (whois, contact information, whatever you want to call it), it starts a new initial registration period. Because you are essentially creating a new registrant for the domain. Maybe the big question is... What is your interpretation of initial registration? It is just after registering a new domain, renewals and transfer completions? Maybe the big contention is whenever you update the registrant contact type, it starts it over. For example, when there is a change of account push of a domain from one account to another. It is a change of registrant and would invoke that policy. What do you all think of this?

From the Go Daddy Group Side (GD+WWD), they have the most domain registrations. Could the domain manager system really be smart enough to determine whether a small change in the whois was drastic enought to warrant Evidence of fraud or Reasonable dispute over the identity of the Registered Name Holder or Administrative Contact? It could be hard to program that. So it is up to them to have a humans look at each whois that is changed at the whims of the domain owner to verify such a thing? Basically, the domain managing system can&#039;t be everything to everyone. When that whois is updated. Boom! New 60 day period. To protect the customer from losing the domain or hinder them from moving away? It is all your point of view. I do not find that transfers are too hard away from GD and WWD. They are one of the few registrars that actually let you accept/deny the transfer yourself earlier to expedite it rather than wait for the 5-7 day autoaccept. I hope to see some more POVs! :P</description>
		<content:encoded><![CDATA[<p>I wish ICAAN would actually address the impications of changing the whois information. It would clarify this whole transfer situation. It is up to your take however. </p>
<p>ICANN Transfer Policy Section 3. Obligations of the Registrar of Record</p>
<p>A domain name is in the first 60 days of an initial registration period.</p>
<p>To me, that means whenever you update the registration information (whois, contact information, whatever you want to call it), it starts a new initial registration period. Because you are essentially creating a new registrant for the domain. Maybe the big question is&#8230; What is your interpretation of initial registration? It is just after registering a new domain, renewals and transfer completions? Maybe the big contention is whenever you update the registrant contact type, it starts it over. For example, when there is a change of account push of a domain from one account to another. It is a change of registrant and would invoke that policy. What do you all think of this?</p>
<p>From the Go Daddy Group Side (GD+WWD), they have the most domain registrations. Could the domain manager system really be smart enough to determine whether a small change in the whois was drastic enought to warrant Evidence of fraud or Reasonable dispute over the identity of the Registered Name Holder or Administrative Contact? It could be hard to program that. So it is up to them to have a humans look at each whois that is changed at the whims of the domain owner to verify such a thing? Basically, the domain managing system can&#8217;t be everything to everyone. When that whois is updated. Boom! New 60 day period. To protect the customer from losing the domain or hinder them from moving away? It is all your point of view. I do not find that transfers are too hard away from GD and WWD. They are one of the few registrars that actually let you accept/deny the transfer yourself earlier to expedite it rather than wait for the 5-7 day autoaccept. I hope to see some more POVs! <img src='http://domainnamewire.com/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
