ICANN related question...
We have a customer that purchased a domain through a reseller of register.com. The Whois records only point to the actual company and the originating accredited registrar: register.com. Does anyone know of any hints to find out who the reseller is? Apparently Register.com can't supply us with that information. Just in case anyone is wondering: Domain ID:D96747839-LROR Domain Name:GIRLSINCDE.ORG Created On:21-Apr-2003 18:39:46 UTC Last Updated On:20-Nov-2013 22:11:57 UTC Expiration Date:21-Apr-2014 18:39:46 UTC Sponsoring Registrar:Register.com, Inc. (R71-LROR) Status:CLIENT TRANSFER PROHIBITED Registrant ID:F50A8CB8E137E659 Registrant Name:Lori Cooney Registrant Organization:Girls Incorporated of Delaware Sincerely, Eric Tykwinski TrueNet, Inc. P: 610-429-8300 F: 610-429-3222
why bother getting rcom to grovel through the records they should have kept (it happens to reseller model registrars, occasionally i'm asked if i can help a core registrant find their member (reseller)), just do a transfer request to another registrar (i'm not volunteering) and get the registrar-of-record changed. now you know the (gaining) r-of-r, and the (gaining) reseller (if any), and you're free to do whatever else you want. the hammer to use if rcom hangs due to enoresellerrecord is icann complaince, which in time is effective. -e
On 12/6/13, 1:14 PM, ebw@abenaki.wabanaki.net wrote:
why bother getting rcom to grovel through the records they should have kept (it happens to reseller model registrars, occasionally i'm asked if i can help a core registrant find their member (reseller)), just do a transfer request to another registrar (i'm not volunteering) and get the registrar-of-record changed.
now you know the (gaining) r-of-r, and the (gaining) reseller (if any), and you're free to do whatever else you want.
Unfortunately, that won't work, because:
Status:CLIENT TRANSFER PROHIBITED
... means that the domain name is locked against transfers, and someone will first need to login at the existing reseller to unlock it (and probably to get the transfer authorization code, too). To the original poster: Why won't Register.com give you the reseller name? Is it because you're not one of the people listed in their account records? If so, I can't fully blame them; my company (also a registrar, although we don't have resellers) also gives out as little information as possible to "strangers" to discourage social engineering hijacking attempts. Many companies will confirm information but not volunteer it, leading to boring conversations along the lines of "Well, I can't tell you, but can you think of the name of anyone at your company that might have registered the domain name? No... no... no...". Have the person listed in the Register.com records call them and you may get further.
the hammer to use if rcom hangs due to enoresellerrecord is icann complaince, which in time is effective.
Sadly, ICANN compliance will not do a thing for any individual domain name incident. Their mechanism for such things is to pass complaints on to the registrar, even when the registrar IS the problem, as if they're the Better Business Bureau. I've never seen them intervene in an individual domain name case. I once spent a great deal of my time trying to get ICANN compliance to do something in a few egregious cases before realizing that they explicitly do not see that as their role. I'd initially assumed their unhelpfulness was gross incompetence, but it turned out to be a sort of reverse Hanlon's razor. -- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/
On Fri, Dec 6, 2013 at 4:34 PM, Robert L Mathews <lists@tigertech.com>wrote:
now you know the (gaining) r-of-r, and the (gaining) reseller (if any), and you're free to do whatever else you want.
ICANN is one potential recourse against the registrar, if non-cooperative with the registrant; another one is the courts, and finally: there is the court of public opinion.
Unfortunately, that won't work, because:
Status:CLIENT TRANSFER PROHIBITED
... means that the domain name is locked against transfers, and someone will first need to login at the existing reseller to unlock it (and probably to get the transfer authorization code, too).
This is a technical block against transfer, that the losing registrar must not refuse to allow the registrant to remove. http://archive.icann.org/en/transfers/policy-12jul04.htm "Instances when the requested change of Registrar may not be denied include, but are not limited to: ... * Domain name in Registrar Lock Status, unless the Registered Name Holder is provided with the reasonable opportunity and ability to unlock the domain name prior to the Transfer Request. " Sadly, ICANN compliance will not do a thing for any individual domain
name incident. Their mechanism for such things is to pass complaints on to the registrar, even when the registrar IS the problem, as if they're the Better Business Bureau. I've never seen them intervene in an individual domain name case
Perhaps, there need to be some complaints to ICANN about ICANN then. Or to other community entities about an apparent lack of competent authority by ICANN, to even successfully implement their own policies.
Robert L Mathews, Tiger Technologies, http://www.tigertech.net/
-- -JH
On Fri, Dec 06, 2013 at 02:34:07PM -0800, Robert L Mathews wrote:
Sadly, ICANN compliance will not do a thing for any individual domain name incident. Their mechanism for such things is to pass complaints on to the registrar, even when the registrar IS the problem, as if they're the Better Business Bureau. I've never seen them intervene in an individual domain name case.
I have, but usually you can contact the registry before going to ICANN if you're having this problem. Registries will lean on the registrars to behave if there's a problem of this sort. A -- Andrew Sullivan Dyn, Inc. asullivan@dyn.com v: +1 603 663 0448
participants (5)
-
Andrew Sullivan -
ebw＠abenaki.wabanaki.net -
Eric Tykwinski -
Jimmy Hess -
Robert L Mathews