Forum Moderators: phranque
:)
Can't find the precise entries made by this IP Number, but it was banned verbatim until just a few weeks ago when another user (just a very couple of numbers in the last block) came along and did the same thing.
It was then that I trimmed back the block to include both numbers.
As I recall both offenders were taking multiple files (ten or more) per second.
Pendanticist.
216.185.57.94
216.185.57.98
216.185.57.102
216.185.57.106
216.185.57.110
216.185.57.134
216.185.57.138
216.185.57.142
216.185.57.146
216.185.57.150
So far, each has only visited about 175 pages, but perhaps this is just the warmup for the onslaught you experienced? For now, I'm continuing to allow access, but I'm keeping a close eye on things...
UB
A reverse listing of the .57 block (if they've got forward DNS wide open, I bet that rear would be too, and so it was) shows nothing registered above 216.185.57.70, which points to lists.buzzplant.com, a host for a christian music promotion company. A few other hosts that seem to be web/email boxes are also on this chunk of address.
Whoever is hitting you doesn't seem to be running a legitimate operation, since they have no hosts listed.
I suppose there is a slim chance that whatever these folks are working on has been altered (after having sprung a bunch of traps, or met the wrath of one who loves paying bandwidth fees....for people). But, I don't think so.
These folks came back several times after their initial ban was in place. They got the hint eventually.
:)
Pendanticist.
What are these 'bad guys' after, and what can they do with it?
It seems our experiences are a bit different, but I have had about 10 visits from this range where they:
So in my experience they are email-harvesters
In response to your question, D_Blackwell, the problem is that there are many bots crawling the web for purposes many of us wouldn't endorse (i.e., gathering email addresses for spamming purposes). Thus, none of us want to facilitate this, let alone pay for the bandwidth it requires, particularly people like myself who have literally millions of pages that could be crawled -- in vain, I might add -- in pursuit of email addresses.
Then I pasted in the address given in the whois info, and found an acaza.com at the same address. A whois on acaza.com showed four name servers that were on the aotech.net domain.
Still no good info on aotech or aotech.net on Google, so I tried a to get a listing of the aotech.net domain (these is usually denied, it is a potential security breach) using host -l aotech.net. This yielded a large list of domains indicating that aotech.net was a hosting company.
Having no forward domains matching, I tried a reverse lookup: host -l 57.185.216.in-addr.arpa, which showed no reverse addresses for the chunk of addresses you want.
Oh, and the same range of addresses is now showing on google in somebody's open web stats, and they've done 310 hits in just one day's worth of traffic spread across 3 domains.
The ARIN data for SSM DC inc has been reported to be invalid. Both companies are in Ohio.
John also did a number of postings on the COBALT site, where he spoke of some ISP billing software and some technical problems with running the COBALT servers.
So, it looks like they're either running something on the side, or they've been duped.
Ah well.
I've just setup a spamtrapping system and crawlers from both IP zones added unique trap addressess for same ( PUMP and DUMP scam) spam mailing list. Ofcourse totally avoiding reading robots.txt at all.
The first is already listed as a spammer:
[spamhaus.org...]
And the second seems a stolen netblock. The sightings of "real" aotech are from 1999, to later become zooga.net. It appears to been a ISP that provided content filtered dialup access. (I wonder why they went titsup..)
They went belly up and now went back to AOtech located in Westerville Ohio.
not sure whats up with them now but they may have held on to a few clients and are not very well supported. acaza.com is run by the same people.
...have a few customers that got burned by them.
to my deny from list in my root .htaccess file.
I have a related question though:
I've blocked a particularly bothersome bot using their IP block in this format:
NB. These numbers are examples;
deny from 123.456.
But I've just received an Email via our contact page, (proving they accessed our site) from the IP. 123.456.78.90
How come?
I thought 123.456.
Would block all IP's beneath the 456. bit?
The Apache docs say that the final full stop (period) SHOULD be included.
Any ideas how they got through to our site?
Colin
For example:
[dnsstuff.com...]