Dean and all, Dean Robb wrote: > At 16:07 1/28/99 -0800, you wrote: > >hello Anthony, > > > >If you'd been catching his earlier messages, he goes beyond those trivial > >thing we would normally just consider basic software operations. He wants > >to authenticate content, unless I'm mistaken. All those things you talk > >about are already being done, with the possible exception of the name > >server check. In addition, he wants physical addresses to be checked and > >individuals to be authenticated. > > Please don't misconstrue what I've said. I've said it plainly. I don't > know how to say it any more plainly. SPOT CHECK the registrations to > validate the data. That's all. Fine Dean, check away! Be proactive. Do it yourself. > I listed sending a confirmation email to > see if it bounces, I listed nameserver verification. I also advocate at > least checking random addresses and phone numbers for accuracy. Checking for phone numbers may be considered a evasion of privacy. > What is so > terribly hard about making sure that the phone numbers in the registration > are at least composed of NUMBERS and not letters? This would be reasonable. Be my guest. Check them yourself. > > > There is no way on this Earth that NSI checks the veracity of ANY data in > the registration. I'm forever seeing people complaining that WhoIs shows > someone using their nameservers, seeing impossible phone numbers, > impossible email addresses. This may be true indeed is likely true in some cases. > > > You yourself refer to these kinds of checks as "basic software operations". > This begs the question: If they are so simple, why aren't they being > done? In Feb 1998: > > Total domains checked: 1401150 > Domains with NO good nameservers (all responded non-auth): 236008 > Domains with NO good nameservers (some timed out): 107482 > Domains with at least one bad non-auth (but most/all answering):99211 > > Bringing that into percentages, about 17% of all domains in COM have > NO good nameservers listed. If one adds in the nameservers that timed > out, that number goes up to 25%, and adding in domains with at > least one bad nameserver brings the number up to 32% of the domains > in .com that have bad nameserver info registered. > > Source: Dalvenjah FoxFire as posted to RS-TALK, Mar 98. > > This is only for the nameservers and is a few hundred thousand > registrations ago. I see it as a problem. And a problem than can be > solved relatively easily. Than put together your own checking system with some specialized scripts and do it yourself. > > > Other fairly easy to fix problem, phone #: > > Global Sports Connection S.A (BETMAKER-DOM) > C.CTRAL y 1 ra.Av. 8 > San Jose, Costa Rica > CR > > Domain Name: BETMAKER.COM > > Administrative Contact: > Hale, Michael (MH3358) [EMAIL PROTECTED] > (506) 231-3470 > Technical Contact, Zone Contact: > Biehl, Juan (JB4247) [EMAIL PROTECTED] > (506)2565811 (FAX) (506)2220331 > Billing Contact: > Barrett, Scott (SB2703) [EMAIL PROTECTED] > 317.847.8099 (FAX) 317.841.8215 > > Now, it doesn't take a real complicated program to match area codes with > supposed locations. If it were done, it would be discovered that 506 is > New Brunswick, Canada and not Costa Rica. Well this doesn't wash at all. This person could be using any one of several phone numbers that he may have as a contact number, where he may reside somewhere else and use call forwarding to another number. > > > Two easy to solve problems. So why aren't they being done? If they can't > do all the registrations, how about SOME of the registrations? Why don't you do it if you are so interested and sell it as a service. > > > Microsoft Windows(tm): How much hair did you want to tear out today? > > Dean Robb > PC-EASY computer services > (757) 495-EASY [3279] > > Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail [EMAIL PROTECTED] Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 __________________________________________________ To receive the digest version instead, send a blank email to [EMAIL PROTECTED] To SUBSCRIBE forward this message to: [EMAIL PROTECTED] To UNSUBSCRIBE, forward this message to: [EMAIL PROTECTED] Problems/suggestions regarding this list? Email [EMAIL PROTECTED] ___END____________________________________________
