The point is that MP3.com would have most likely realized the domain had expired if the .com wildcard did not exist. Instead, the domain kept resolving and user's of MP3.com became confused, "why did I end up at this sitefinder site?".
Sitefinder never redirected mp3s.com to mp3.com. It appears that mp3.com has https://artists.mp3s.com set up to redirect to http://genres.mp3.com/music/ (I just tried it). I would assume that mp3.com has some type of server monitoring in place, probably something very basic that pings the domain--if so, the domain mp3s.com never stopped responding to requests so it went unnoticed. The domain mp3s.com was in an expired state for 10 days without anyone noticing. On Thu, 9 Oct 2003, Jeff Godin wrote: > On Thu, Oct 09, 2003 at 10:44:24AM -0700, [EMAIL PROTECTED] wrote: > > Looks like an example of one of the problems caused by Verisign's > > Sitefinder: > > > > Fallout from Sitefinder > > http://tint.blognation.us/archives/2003_10.html#000011 > > I fail to see how sitefinder was causing an issue in this case. > > The facts as I've read them indicate that mp3s.com was not renewed, > and when it was removed from the COM. zone, mp3s.com now > matched the wildcard, and resulted in web traffic being directed to > sitefinder. > > The URL referenced above seems to allege that sitefinder was > transparently redirecting mp3s.com to mp3.com until the wildcard was > removed, with no "hey, welcome to sitefinder, did you really mean to > reach one of these addresses instead" page in between. > > This allegation seem to be contrary to the facts claimed in the > article from The Register. > > Am I missing something here? > > -jeff > > -- > Jeff Godin <[EMAIL PROTECTED]> > Jedin Technologies > -- "If Verisign is the 'Value of Trust', then trust ain't worth *ANYTHING* any more." - me <=> ASK and you shall receive <=>
