spamislame wrote:
That's great, but there are, on average, 20,000 or more per day of these domains.
ns1.pandachine.com is the nameserver. Just a quick search comes up with all these domains depending on it, likely only a small part of the total, since I easily found one not on the list just by matching the pattern of the domain names:
Quote:
nyugewc.be NS ns1.pandachine.com
nyugewd.be NS ns1.pandachine.com
lykasf.be NS ns1.pandachine.com
lykasm.be NS ns1.pandachine.com
nyugewm.be NS ns1.pandachine.com
nyugewn.be NS ns1.pandachine.com
nyugewq.be NS ns1.pandachine.com
nyugewt.be NS ns1.pandachine.com
lykasv.be NS ns1.pandachine.com
nyugeww.be NS ns1.pandachine.com
nyugewy.be NS ns1.pandachine.com
lykasz.be NS ns1.pandachine.com
nyugewz.be NS ns1.pandachine.com
hreesf.im NS ns1.pandachine.com
hreesf.org.im NS ns1.pandachine.com
hrees.org.im NS ns1.pandachine.com
hreesv.org.im NS ns1.pandachine.com
hreesf.com.im NS ns1.pandachine.com
hrees.com.im NS ns1.pandachine.com
hreesv.com.im NS ns1.pandachine.com
hreesf.co.im NS ns1.pandachine.com
hrees.co.im NS ns1.pandachine.com
hreesv.co.im NS ns1.pandachine.com
hrees.im NS ns1.pandachine.com
hreesf.net.im NS ns1.pandachine.com
hrees.net.im NS ns1.pandachine.com
hreesv.net.im NS ns1.pandachine.com
hreesv.im NS ns1.pandachine.com
pandachine.com NS ns1.pandachine.com
The list for ns2.pandachine.com comes up with the same domains, even though dnsstuff traversal doesn't return that result. Perhaps they thought they'd be clever and let us blackhole the one without inactivating the other, or maybe they swap off. I'm not sure why dnsstuff misses it:
Quote:
Looking up at the 2 nyugewy.be. parent servers:
Server Response Time
ns1.davies-estates.com [67.202.107.79] Timeout
ns1.pandachine.com [0.0.0.0] Timeout
When I try an alternate lookup I get
Quote:
dig: couldn't get address for 'ns1.pandachine.com': not found
ns2.pandachine.com isn't responding when I check that way, either.
They've done the same with the other nameserver, too, and since it's still alive, you can query it:
Quote:
; <<>> DiG 9.3.2 <<>> @ns1.davies-estates.com lykasz.be A
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36548
;; flags: qr aa rd; QUERY: 1, ANSWER: 15, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;lykasz.be. IN A
;; ANSWER SECTION:
lykasz.be. 1800 IN A 196.217.221.240
lykasz.be. 1800 IN A 201.43.94.97
lykasz.be. 1800 IN A 201.92.93.89
lykasz.be. 1800 IN A 201.172.137.233
lykasz.be. 1800 IN A 41.251.26.102
lykasz.be. 1800 IN A 95.65.187.65
lykasz.be. 1800 IN A 118.171.133.110
lykasz.be. 1800 IN A 119.95.219.202
lykasz.be. 1800 IN A 125.202.254.181
lykasz.be. 1800 IN A 189.18.151.58
lykasz.be. 1800 IN A 190.25.74.65
lykasz.be. 1800 IN A 190.35.186.15
lykasz.be. 1800 IN A 190.161.75.6
lykasz.be. 1800 IN A 190.163.65.177
lykasz.be. 1800 IN A 190.209.12.55
;; AUTHORITY SECTION:
lykasz.be. 1800 IN NS ns1.davies-estates.com.
lykasz.be. 1800 IN NS ns2.davies-estates.com.
;; ADDITIONAL SECTION:
ns1.davies-estates.com. 1800 IN A 94.23.177.147
ns2.davies-estates.com. 1800 IN A 122.197.244.37
;; Query time: 13 msec
;; SERVER: 94.23.177.147#53(94.23.177.147)
;; WHEN: Tue Dec 1 23:22:08 2009
;; MSG SIZE rcvd: 353
The ns.2 nameserver doesn't show up in dnsstuff. That's the sort of detail Xin Net will miss, too.
.im is Isle of Mann. They appear to be shutting these down much more promptly than .be (Belgium).
The other question is are the phishers really
paying for 20,000 domains a day with their own money? If not, it doesn't matter how many they registered in bulk; if they stiffed the registrar by paying with someone else's paypal account, the registrar will probably suspend them in bulk, too.