<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [registrars] RE: Credit Card Proposal
I have no problem sharing the analysis section. However, some of the actual
credit card information has been redacted by registrars that have provided
me the information. So the exhibits would likely not be made available.
Moreover, should the FTC should start an investigation this information
(exhibits) would need to stay private.
The one thing I took out of the FTC meeting last week, is that the FTC is
looking for people to help them catch the bad guys. I believe tackling the
credit card problem needs to be done through multiple channels: registrars
employing available safeguards, law enforcement trying to catch the bad
people, and registries helping us with the credit card charge back issue.
This is a problem which needs collective help.
Mike
> -----Original Message-----
> From: Elliot Noss [mailto:enoss@tucows.com]
> Sent: Monday, February 24, 2003 4:02 PM
> To: Michael D. Palage; Michael Brody
> Cc: 'Registrar Constituency'
> Subject: RE: [registrars] RE: Credit Card Proposal
>
>
> Michael P:
>
> Could you please provide us all with a copy of the information you are
> providing to the FTC? It sounds very useful. Thanks in advance.
>
> Regards
>
> Elliot Noss
> Tucows inc.
> 416-538-5494
>
> > -----Original Message-----
> > From: owner-registrars@dnso.org [mailto:owner-registrars@dnso.org]On
> > Behalf Of Michael D. Palage
> > Sent: Monday, February 24, 2003 3:54 PM
> > To: Michael Brody
> > Cc: ross@tucows.com; 'Robert F. Connelly'; 'Registrar Constituency'
> > Subject: [registrars] RE: Credit Card Proposal
> >
> >
> > Michael,
> >
> > Thanks for this input, I have been collective information from
> registrars
> > and this is the one type of fraud I have been trying to document.
> > The other
> > fraud I see is where a series of registrars will be hit up
> > simultaneously, I
> > have seen credit card charge back statements with a whos who of ICANN
> > accredited registrars and resellers listed.
> >
> > If you could share this information with me off-line and
> redacted, I will
> > include it in a compilation of material that I will be providing
> > to the FTC.
> > The fact that someone waits till the last minute raises my
> > suspicion level.
> >
> > One of the issues that Tim at GoDaddy raised, and which I
> > supported, was the
> > need for a lock down in connection with transfers to prevent a fraudster
> > from transferring names and racking up domain name years with
> > stolen credit
> > cards. I still submit that a similar 60 day lock down on initial
> > registrations to prevent fraud should also apply to transfers to prevent
> > similar fraud, absent extenuating circumstances. Unfortunately,
> Tim and I
> > lost this battle :-)
> >
> > Mike
> >
> > > -----Original Message-----
> > > From: Michael Brody [mailto:mbrody@tldsystems.com]
> > > Sent: Monday, February 24, 2003 3:47 PM
> > > To: Michael D. Palage
> > > Cc: ross@tucows.com; 'Robert F. Connelly'; 'Registrar Constituency'
> > > Subject: Re: Credit Card Proposal
> > >
> > >
> > > I hate to muddy the issue here but there is an aspect of cc
> > fraud that we
> > > might be able to address within ourselves.
> > >
> > > The people who commit credit card frud have become more
> > > sophisticated. We
> > > have had instances where a domain was registered with a
> fradulent card.
> > > Aproximately 45 days after the registration we get notice from
> > > the credit.
> > > When we confirm that this is indeed a legitmate chargeback and
> > not an end
> > > user error we then attempt to place the domain on hold.
> > >
> > > At that time we find out that the domain has been transferred
> to another
> > > registrar. Calls to the 'gaining' registrar have been met with
> > > little to no
> > > support.
> > >
> > > If we were to put a system in place to work together on issues
> > > such as these
> > > we might be able to at least partially address the credit card
> > > fraud problem
> > > for issues of this nature.
> > >
> > > Michael
> > >
> >
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|