Jorey Bump a écrit : > Justin Piszcz wrote, at 12/20/2008 05:43 AM: >> $ whois linendim.com >> >> Record created on: 2008-12-15 11:45:30.0 >> Domain Expires on: 2009-12-15 11:45:31.0 >> >> A 1-second life domain name. > > What do you mean? The domain expires in one year and a second from its > creation date.
he meant that the domain has been created a few days ago, and so "should not start sending too much mail". Such argument must be used with caution. Few years ago, I have worked on a (social net style) project and marketing decided to chose a new name. The new domain thus started sending a lot of mail few days after it was registered. The same caution is needed when trying to detect domains that only started sending mail recently. Trying to use the age (be it "whois age" of "date of first mail") is not very "practical". it may be used while investigating on a suspicious domain. > >> First, is there an existing policy server out there that checks how many >> days old a domain is? > > If so, it would probably end up working a lot like greylisting. You'd > get a similar effect scoring with the SpamCop dnsbl, since it penalizes > fresh domains. > >> I know there is an RHSBL for it but this seems rather odd, if the domain >> has expired/etc it would be nice to filter on these statistics.. > > True. There's no reason to accept mail from a long-expired domain (but > your example hasn't expired). > > > [BTW, there appears to be a problem with the DNS for your domain, > lucidpixels.com. Your nameservers are not responding.] > he has only one name server (75.144.35.66) and it is not responding. he should setup a secondary NS, as recommended by the RFCs...
