> Generally speaking whois queries is a poor way to determine > domain age, at least for client applications. The whois > infrastructure is simply not designed to support the volume of > queries required, even if locally cached. Other problems: > > 1. Inconsistent record formats > 2. Rate limits much lower than the number of domains registered > or kited/tasted each day. http://www.bobparsons.com/DomainKiting.html > 3. Unavailability of whois for some TLDs > > A centralized server would be better, but still subject to some > of the problems above. > > As a general concept domain age is a pretty good measurement of > spam potential, but it's by no means 100%. As others have noted > the false positive potential is pretty high.
Ok. Why not combine an age check with Hardin's "spam-friendly registar" plugin? I mean, a brand-new domain from a SFR (Spam-friendly registar) is really bad (scores 5?). A brand-new domain from a non-SFR is not that bad (scores 1?). I guess that domain age and registar neck should be two different informations to be (somehow) combined. Giampaolo > > Jeff C. > -- > Jeff Chan > mailto:[EMAIL PROTECTED] > http://www.surbl.org/ >
