Re: Re[6]: [ga] Domain Transfers

["L Gallegos" <jandl@jandl.com>]

I have emailed the person who had the domain fall into the vortex and 
that person may email you personally.  It is not up to me to relate that 
individual's incident here.  Let's just say it was a monumental screw up, 
and not unusual, incident.  

I have received many emails (because of one of my websites) regarding 
domains being lost.  I do not feel it is my privilege to post personal 
information on a public list and will not do so.  However, I cannot 
discount the fact that these incidents do occur and I have followed up on 
many of them just for my own education.

In any case, say what you will, but I know first hand that it happens and 
also know which registrars told me that it could happen and has 
happened AND that there is no guarantee that transfer will be without 
such an incident.  To me, as a registrant, it makes no difference 
whether it is NSI or another registrar that is involved, or which person at 
those registrars are involved or why it happens.  The only thing of 
interest to the registrant is that it DOES happen.

Just because all incidents are not made public on this list, does not 
make it a non issue.  Out of millions of registrants, there are around 900 
subscribed to this list, not all of whom are domain name holders. This is 
a rather small group of people.  It is highly unlikely that registrars will 
make such incidents known here either.  It's not exactly in their best 
interests.

IMO, the bottom line is that in such a case, there has to be a guarantee 
that the domain will, in fact, not be lost to the registrant if transfer is 
initiated - for any reason.

Leah

On 13 Dec 2001, at 18:42, William X Walsh wrote:

> Thursday, Thursday, December 13, 2001, 6:18:19 PM, L Gallegos wrote:
> 
> > Additionally, I have had others relate similar situations to me, but,
> > again, do not report them to this list.  I would not have mentioned this
> > incident had you not made your comment.  IMO, it is not a good idea to
> > make categorical statements such as yours and then not expect to see a
> > refutation of that comment.  I also do not really feel compelled to
> > provide you with specifics on any one incident that may be the basis for
> > possible actions on the part of the parties to it.
> 
> Well, it is really easy to make claims that are not backed up by real
> facts. It is not a good idea to claim that incidents are occuring, and not
> be willing to provide facts to back that claim up.
> 
> As far as I am aware, I have seen no reports of domains lost "in
> transfer" that have not ended up being a case of registrant to
> registrant transfers at NSI.
> 
> I >>HAVE<< seen domains lost during Registrant to Registrant transfers at
> NSI (ala Races.com).  And I've seen people use those cases to mistakenly
> say that Registrar to Registrar transfers are not safe, when in fact this
> was a problem that was internal to NSI, and had nothing to do with the
> Registrar transfer system.  The other time people claim a domain was lost
> in a registrar to registrar transfer is when the domain had already been
> hijacked at the existing registrar, and then the hijacker transferred the
> domain name to another registrar (or reset the billing data and then
> registered the name when it was deleted for non-payment).  Again, this is
> not a problem with Registrar to Registrar transfers, but a problem with
> poor security at the original registrar (which, not surprisingly enough is
> almost always NSI Registrar).
> 
> And I'm aware some claim that Registrars tell them that transfers have
> security issues, but usually that ends up being a case of a C.S. rep who is
> uninformed, misinformed, or a company who is just C.Y.A. so they can blame
> someone else if there is a problem.
> 
> -- 
> Best regards,
> William X Walsh <william@wxsoft.info>
> --
> Webcertificates.info
> SSL Certificates for resellers from $49ea
> 


--
This message was passed to you via the ga-full@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga-full" in the body of the message).
Archives at http://www.dnso.org/archives.html