Forum Moderators: open
[webmasterworld.com...]
What are these guys looking for by deliberately requesting URLs that don't exist? I find this a bit disturbing. Is it perhaps a hack attempt?
So, are we to add this code as-is to our .htaccess file? I've worked with redirects in this file but not blocking someone.
Options -Indexes
<Limit GET>
SetEnvIf User-Agent Charlotte keep_out
order allow,deny
deny from 209.249.86.
allow from all
deny from env=keep_out
</Limit>
Thanks,
Starhugger
63.148.99.*** - - [22/May/2006:15:18:26 -0700] "GET /%26y%3D029700D88CA97D40%26i%3D41%26c%3D2699%26q%3D02%5ESSHPM
[L7kwz?wvlkpmf?py?u~ee?rjlv¦6&e=utf8&r=2&d=www-en-us&n=89045H1
EOPTK1IPG&s=175&t=&m=407BD303&x=0164DE6A9CD3A7EA HTTP/1.1" 404 1980 "http://www.some-scraper-directory.com" "Mozilla/4.0 (compatible; MSIE 6.1; Windows XP)"
[betaspider.com...]
We are a stealth-mode startup that is indexing the web for a novel application.
Would someone explain what a "stealth-mode startup" is please? ;)
Same IP as mentioned previously.
Amazing how many bots are using 'does not exist' Hosts nowdays.
Courtesy of [dnsstuff.com...] --
IP address: 209.249.86.4
Reverse DNS: charlotte.betaspider.com
Reverse DNS authenticity: [Could be forged: hostname charlotte.betaspider.com does not exist]
Greeeeat... Do you think this kind of thing is a serious enough problem that web hosts will create new security filters to shut out these little creeps? Or, since we're paying for the bandwidth that they chew up, do you think it will be regarded as our problem? I'm just thinking how ISPs and email providers seem to have been forced to invest in anti-spam and anti-virus filters, if only to protect themselves from their service being chewed up by those critters. Just wondering if something like that might happen with creepy-crawly things too. Any thoughts?
Starhugger
I didn't really even know about or notice that aspect until DNS Stuff [dnsstuff.com] started adding "IP Information" as a quick lookup option. Ah, ignorance was bliss:)
And please know that I'm not a network person -- my SysAdmin tends to that and the servers and I do the Web (a good bifurcated arrangement when one's SysAdmin is also one's spouse:) But our entire Class C block (0-255 IP addresses), all of our network addresses, have a nameserver assigned to them. Meaning when you do a lookup even for our unassigned IPs, they exist, they're legit.
So when it comes to what these other guys are doing, beats me. Way I look at it, Bad Guys and/or bot-runners and their ilk know it's one way to hide. Or, giving some the benefit of the doubt, they don't know how nameservice and such works. Either way, I don't want or need that kind of 'visitor' crawling through my stuff.
2.) Re an increasing number of apparent/actual 'forgeries'...
Were I an ISP, I probably wouldn't think twice because the scope of my operations would be such that any of these guys is a flea on the rump of an elephant. And I'd already have loads of security and efficiency kinds of things in place, both software and hardware, so drop-kicking one more iffy IP block into the bit bucket would be more annoyance than anything else.
However, as a site owner, that means an increasing number of visitors (good & bad) won't be able to see my site(s) because more countries and IPs = ISPs, just as good and bad 'users' are increasingly blocked on the e-mail side. To the average site owner, the end result will be probably be negligible, if even noticeable. Alternatively, if controlling site/server access matters a whole lot to, say, a large commercial enterprise, they're already solely or co-located and continuously monitoring/controlling who comes and goes, and who doesn't.
3.) Long, iffily OT (sorry) muse short...
I'm not going to lose any sleep over the 'forgeries,' at least not yet:) Because for myself, the more I pay attention to the jerks, the less I spend time doing that which is remunerative(!) and also which I truly enjoy -- working with clients, building their sites, seeing their plans and dreams and goals realized, hearing them exclaim, "I love it!"
Geeking is like gardening: You're never going to kill every weed, let alone prevent any from coming back. But if all you focus on are the weeds, you lose sight of what's growing right.
And now, I really must scoot and tend to some flowers (& yank a few weeds:)
Amazing how many bots are using 'does not exist' Hosts nowdays.
I looked it up on a differnet IP "looker upper" and came up with "Private Block Address"....not much better.
Was using a really good IP whois site but it went down a few weeks ago. Don't really trust the one that pfui uses as it turns out bad results on geo lookup, i.e. Glasgow, Scotland, Norway (and other erroneous results).
Don't really trust the one that pfui uses as it turns out bad results on geo lookup
geoge's canufly was the BEST.
Not only do we all miss george today, however we will assuredly in the future.
george had built some sub-delegation databases based on local airport names that many of the BIG IP's use. george understood the three letter coding, which to the rest of us looks random.
Thanks to George for your long effort and dedication.
Hope your rest is an enjoyable change of routine.
Don
When I'm researching a bot or a Host/IP and/or to get a look at an iffy site without going there, I use a mix of DNS Stuff, Google, dig, traceroute, and Name Intelligence's Domain Tools [domaintools.com] (formerly Whois Source; whois-dot-sc). They're the ones running:
www.[whois].sc <=brackets added or else BestBBS obfuscates
SurveyBot/2.3 (Whois Source)
Between G and DNS Stuff and DT, I usually get more than enough info to either confirm or allay my suspicions.
(Hmm... Someone should start a thread about bot-lookup techniques. ~Oh, Dan...~ :)