ICANN Signals Get-Tough Action On Registrar
The Register reports that ICANN senior vice president of services Kurt Pritz has posted a blog entry containing a letter to Glenn Stansbury, VP of operations at Registerfly, threatening to revoke Registerfly's domain accreditation unless the company gets its act together in the next 15 days.
ICANN has significant authority over these matters.
It would appear that ICANN is quite uncomfortable with the fact that Registerfly's recently resigned CEO has a suit pending against him that alleges corporate spending on escorts and liposuction- allegedly at the cost of the company's operations and its domain-holding customers.
ICANN's tough stance appears to be an acceleration of the agency's usual hands-off practice in disputes between a registrar and domain holders.
Here's what the letter says about these "breaches;"
Failure to provide authorization info codes
- A complainant stated that he requested AuthInfo codes for four Registered Names
(NAMES REDACTED) but that Registerfly did not provide the codes, despite the lapse of over five days.
- b. A complainant stated that he requested AuthInfo codes for fifteen Registered
Names (NAMES REDACTED) but that Registerfly did not provide the requested codes within one week of the request.
- c. A complainant stated that she requested an AuthInfo code for her Registered
Name (NAME REDACTED), but that Registerfly ignored the request for at least six days and never issued an AuthInfo code.
- d. A gomplainant stated that she requested AuthInfo codes for both of her Registered Names (NAMES REDACTED) on 12 February 2007, but that as of 19 February 2007, Registerfly had not provided any AuthInfo codes.
- e. A complainant stated that as of 22 January 2007, Registerfly had not responded to his 12 January 2007 requests for AuthInfo codes to transfer his Registered Names (NAMES REDACTED).
2. Failure to unlock names
- a. A complainant stated that several times since 4 February 2007 he requested that his domain name (NAME REDACTED) be unlocked, but that Registerfly did not act on these requests, causing the transfer to be denied.
- b. A complainant stated that on 15 February 2007 he requested that his Registered Names (NAMES REDACTED) be unlocked, but that Registerfly reported that it could notunlock the domains. The domain names remain locked to date.
"Registerfly’s demonstrated failure to follow the Inter-Registrar Transfer Policy is not simply a violation of the RAA. It also frustrates and impedes ICANN’s stated purpose in providing a “straightforward procedure for domain name holders to transfer their names from one ICANN-accredited registrar to another should they wish to do so,” the note says. (See
"Each registrar’s compliance with these procedures is essential for this Consensus Policy to work as anticipated. Violations of this policy by Registerfly, as those outlined above, harm both the customer and other registrars. Registerfly’s violation of the Transfer Policy provides an independent ground for termination of Registerfly’s accreditation, if all such violations are not cured within 15 days of this notice.
Related Tags: icann, ICANN, domain, registerfly, Registerfly
- Related Entries
Listed below are links to sites that reference ICANN Signals Get-Tough Action On Registrar:
TrackBack URL for ICANN Signals Get-Tough Action On Registrar: