Jeff Chan wrote:
Another problem is how to automatically distinguish an actual hosting subdomain or redirection site from a wildcarded DNS Address record:
my.pretty.fluffy.bunny.freehostingprovider.com vs random.or.keyed.gibberish.here.spamyisp.biz
I'm not sure why there's any difference for sc.surbl.org:
If an URL is reported as "spamvertized" we want it in a SURBL. Minus the wildcard gibberish. Minus whitelisted SLDs. So you'd first strip the wildcard stuff, i.e. get the IP of the complete URL, strip first part and get the IP of the remaining URL, repeat step 2 until the IPs are different.
This results in here.spamyisp.biz != spamyisp.biz or in spamyisp.biz != biz (because there's no IP for biz).
If spamyisp.biz is whitelisted add here.spamyisp.biz to sc.surbl.org, otherwise add spamyisp.biz.
Same procedure as for say co.uk, or for 3LDs below .cn Patrik's argument...
| Why would the data get *too* large? If the added data | consists of spammy third level domains, wouldn't it be | just as valuable as spammy second level domains? | Listing spammythirdlevel.secondlevel.com wouldn't mean | much more data than listing spammysecondlevel.com would it?
...is IMHO very convincing for SURBLs where all entries are created _and_ deleted automatically like sc.surbl.org
Bye, Frank