NoDaddy.com Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  Home    Forum    Help    Login    Register  
*
July 30, 2010, 01:38:44 AM
NoDaddy.com Forums  |  Forum Boards  |  News  |  Topic: News: ICANN to smack down GoDaddy transfer-blocking scheme Advanced search
  0 Members and 1 Guest are viewing this topic. « previous next »
Reply
Pages 1 Go Down
Author
Topic: News: ICANN to smack down GoDaddy transfer-blocking scheme  (Read 11164 times)
« on: April 04, 2008, 10:50:24 AM »
fyodor Offline
NoDaddy.com Webmaster
Global Moderator
Newbie
*****
Posts: 27

View Profile

One of the sleaziest tricks GoDaddy uses to prevent people from moving to better registrars is their whois transfer block.  As noted on NoDaddy.Com, GoDaddy has been known to cancel people's domains when whois isn't kept up to date.  But if you do update your public whois information, GoDaddy imposes a 60-day transfer hold period to prevent you from moving your own domain to a better registrar.  It looks like ICANN is planning an advisory noting that this is a blatant violation of the registrar agreement.  Here is the text of the proposed advisory:

PROPOSED Advisory

Registrar Advisory Concerning the Inter-Registrar Transfer Policy

The purpose of this advisory is to assist ICANN-accredited registrars in
understanding that under the Inter-Registrar Transfer Policy:

   1. Registrars are prohibited from denying a domain name transfer
request based on non-payment of fees for pending or future registration
periods during the Auto-Renew Grace Period; and

   2. A registrant change to Whois information is not a valid basis
for denying a transfer request.

The Inter-Registrar Transfer Policy ("Transfer Policy") was adopted by
ICANN as a consensus policy in 2004 in order to assist domain name
holders in transferring their domain names from one ICANN-accredited
registrar to another upon request. The Transfer Policy is available at
http://www.icann.org/transfers/policy-12jul04.htm.

   1. Pursuant to the Transfer Policy, registrars are prohibited
from denying domain name transfer requests based on non-payment of fees
for pending or future registration periods during the Auto-Renew Grace
Period.

This section of the advisory considers the scenario when a registrar
denies a transfer request made by the registrant during the registration
period after expiration, if the registrant has not paid for renewal.

Pursuant to Section A.3 of the Transfer Policy, registrars are permitted
to deny outgoing transfers of gTLD domain names only in the limited
circumstances specifically enumerated by the Transfer Policy. One of
these circumstances is:

   5. No payment for previous registration period (including credit
card charge-backs) if the domain name is past its expiration date or for
previous or current registration periods if the domain name has not yet
expired. In all such cases, however, the domain name must be put into
"Registrar Hold" status by the Registrar of Record prior to the denial
of transfer.

The Transfer Policy further states that, "Instances when the requested
change in Registrar may not be denied include, but are not limited to:
Nonpayment for a pending or future registration period..."

In those cases where a registrant has paid all past registration fees,
but has not paid for renewal, and the domain name is in the registration
period after expiration, registrars are prohibited from denying a
transfer request, as the registration period after expiration is either
a "pending or future" registration, during which time the Transfer
Policy prohibits denial of transfers on the basis of non-payment.

While issues related to domain name transfers initiated during the Auto
Renew Grace period are under consideration by the GNSO's Transfers
Working Group, ICANN's intention with this advisory is to provide
clarification of existing policy.

Registrars are advised that under the Transfer Policy they may not deny
a transfer request on the basis of non-payment of fees for the
registration period after the expiration date, unless the denial is
based on non-payment for a past registration period. Registrars that
impose policies or procedures on their registrants that are contrary to
this determination are in violation of the Transfer Policy.

   2. A registrant change to Whois information is not a valid
reason to deny a transfer request.

   A registrant's objection to transfer is not valid unless it is
obtained voluntarily.

This section of the advisory considers the scenario when a registrar
requires a registrant to provide consent to deny transfer requests for a
certain period of time (usually 60 days) in order for the registrant to
update its Whois data.

Section A.3 of the Transfer Policy enumerates nine independent bases
that a registrar may rely on to deny a domain name transfer request.
Registrant updates to Whois contact details is not enumerated as a valid
basis to deny a transfer request in the Transfer Policy. In addition,
ordinary changes to Whois data fields are not evidence of fraud and
therefore not a basis to deny a domain name transfer request.

Pursuant to Section A.3 of the Transfer Policy, registrars are permitted
to deny transfer requests if they have obtained, "6. Express written
objection to the transfer from the Transfer contact. (e.g. - email, fax,
paper document or other processes by which the Transfer Contact has
expressly and voluntarily objected through opt-in means)". While the
language in parenthesis is provided as an example in paragraph
enumerated 6 of Section A.3 of the Transfer Policy, this language is
instructive regarding what types of express written objections were
envisioned as acceptable as a basis to deny a transfer request - only
those objections that are provided expressly and voluntarily.

Subsection 3.7.7.1 of the Registrar Accreditation Agreement ("RAA")
requires registrars to include language in their registration agreements
that obligates registrants to maintain "accurate and reliable contact
details and promptly correct and update them during the term of
the...registration." By agreeing to such language, registrants are under
a strict requirement to update their Whois contact details when they
change. Subsection 3.7.7.2 of the RAA requires registrars to include
language in their registration agreements that authorizes them to cancel
domain name registrations for any willful breach of these obligations.
Accordingly, failure by a registrant to timely update Whois contact
details may result in the cancellation of a domain name.

Registrars that have implemented processes that require registrants to
consent to deny transfer requests in order to update Whois contact
information are not obtaining voluntary express objections and therefore
such objections cannot be used as a basis for denying a transfer
pursuant to Section A.3 of the Transfer Policy.

 Registrars are advised that any express written objections to transfer
obtained by registrars through compulsory means, including express
written objections obtained before allowing registrants to make required
Whois data changes, are involuntary and therefore not a valid basis to
deny transfer requests.

Conclusion

 To ensure compliance with Registrar Accreditation Agreement
requirements, all ICANN-accredited registrars are encouraged to review
their domain name registration transfer processes and relevant domain
name registration documents to make certain they comply with the
Inter-Registrar Transfer Policy. Specifically, registrars' processes and
documents should be consistent with the interpretations set forth in
this advisory regarding Section A.3 of the Transfer Policy pertaining to
the Auto-Renew Grace Period and the type of consent required to deny
transfers.
Logged
 
Reply #1
« on: April 04, 2008, 02:11:54 PM »
Rohan Offline
NoDaddy.com Forums Administrator
Administrator
Full Member
*****
Posts: 225

View Profile WWW

I was just coming over here to post about this...looks like you beat me to it  Grin

http://www.icann.org/announcements/advisory-03apr08.htm
Logged

Hello World!
 
Reply #2
« on: April 04, 2008, 03:40:59 PM »
Yanis Offline
Global Moderator
Sr. Member
*****
Posts: 359

View Profile

Dang. Scooped by the both of you, but glad ICANN is finally (1) doing something as opposed to doing nothing, (2) doing something about this. The 60 day transfer block was a nasty trap that caught many people. One friend updated his details like he's supposed to do, then later found because of the block had to stay with GoDaddy for a whole extra year. Wonder how many millions this tactic has netted GoDaddy over the years. Subliminal message: Class Action Suit. ;-)
Logged
 
Reply #3
« on: April 08, 2008, 10:32:27 PM »
Yanis Offline
Global Moderator
Sr. Member
*****
Posts: 359

View Profile

Popular Geek Newsite Slashdot.org has picked up this story. Hello Slashdotters!

http://tech.slashdot.org/article.pl?no_d2=1&sid=08/04/08/0349253
Logged
 
Reply #4
« on: May 03, 2008, 02:55:01 AM »
Yanis Offline
Global Moderator
Sr. Member
*****
Posts: 359

View Profile

An Update on this story:

DomainWire reports GoDaddy is now complying with the ICANN directive to lift the 60 day transfer locking:

http://domainnamewire.com/2008/04/29/godaddy-allows-transfers-after-whois-changes/
Logged
 
Reply #5
« on: May 03, 2008, 09:01:32 AM »
Rohan Offline
NoDaddy.com Forums Administrator
Administrator
Full Member
*****
Posts: 225

View Profile WWW

An Update on this story:

DomainWire reports GoDaddy is now complying with the ICANN directive to lift the 60 day transfer locking:

http://domainnamewire.com/2008/04/29/godaddy-allows-transfers-after-whois-changes/


Way cool.  After almost two years since my initial incident with the 60-day lock they finally fix it. 
Logged

Hello World!
 
Reply #6
« on: June 06, 2008, 08:29:57 PM »
fyodor Offline
NoDaddy.com Webmaster
Global Moderator
Newbie
*****
Posts: 27

View Profile

Supposedly GoDaddy no longer enforces the transfer embargo after the ICANN smackdown, but GoDaddy still CLAIMS to users that they won't be able to transfer the domain.  I have some test domains at GoDaddy, and today I tried to update the whois information as a test.  As soon as you click "OK" to apply your changes, a new checkbox still appears saying:

"For security purposes I authorize the rejection of all transfer requests for all selected domain names for a period of 60 days from the date of this Registrant Name Change."

It still refuses to allow the change unless I "agree" to the restriction by checking the box.  If you tell users that they won't be able to transfer, that is almost as bad as actually enforcing the provision.  After all, users are unlikely to spend the $$ to transfer their domain if GoDaddy has told them they need to wait 2 months first.  And by then, they may have to renew and thus get another transfer hold.

GoDaddy will probably argue that they just forgot to remove the warning or lack the technical competence.  That is BS.  ICANN is a notoriously slow and inefficient organization, but even they considered GoDaddy's behavior so egregious that they needed to issue a warning.  Yet GoDaddy continues to flout ICANN whenever they think they can get away with it.
Logged
 
Reply #7
« on: June 07, 2008, 10:02:40 PM »
Yanis Offline
Global Moderator
Sr. Member
*****
Posts: 359

View Profile

Some brilliant research there, Fyodor. This is almost a story in its own right. Let's find an official point of complaint at ICANN and get a response.  ICANN have been uncharacteristically pro-active of late, so lets see if they will prosecute him this time? ICANN have been pushing to remove themselves from US Government oversight. If ICANN don't demonstrate an ability to crack down on domain registrars who flaunt their regulations, it'll look pretty bad.

The story of GoDaddy "lifting" the 60 day transfer restriction was reported on http://Slashdot.org . I wonder what they would think if they learned GoDaddy continuing to flaunt it, this time by deceiving customers? Very stupid on GoDaddy's part, because this would mean more bad publicity.

Meanwhile thus GoDaddy customer noticed they time the check-your-WHOIS notices with their renewal notices. If a customer takes the bait and modifies their WHOIS, they get the 60 day lock and you are forced to renew with GoDaddy anyway.

Quote
I noticed in 2008 every time I get a "Important Notice Regarding Your Domain Name(s)" from Godaddy regarding WHOIS info it's followed by a renewal notice the same day of a few days later.

Now if you used Godaddy before you know what happens when you follow their instructions. You can't transfer the domain out for another 60 days so if you domain is up for renewal you're screwed if you want to transfer out. Before 2008 I use to only get that notice maybe one per year.

3/18/2008 1:00 PM accountupdate@godaddy.com
3/19/2008 7:21 AM Renewals@godaddy.com

4/1/2008 12:21 AM accountupdate@godaddy.com
4/8/2008 4:20 AM Renewals@godaddy.com

6/5/2008 10:44 PM accountupdate@godaddy.com
6/5/2008 5:37 AM Renewals@godaddy.com
http://www.webhostingtalk.com/showthread.php?t=698845
« Last Edit: June 08, 2008, 04:00:41 PM by Yanis » Logged
 
Reply Print  Pages 1 Go Up
NoDaddy.com Forums  |  Forum Boards  |  News  |  Topic: News: ICANN to smack down GoDaddy transfer-blocking scheme « previous next »
Jump to: