216.217.36.130

stupid user or bot?

[coyote]

Below is something I found in my error log. In the three years my site has been up I've never seen anything like it. Appears to be either a malfunctional bot or user trying to view headers.

[Wed Aug 27 18:33:08 2003] [error] [client 216.217.36.130] Invalid URI in request GET somepage.html HTTP/1.1
[Wed Aug 27 18:57:07 2003] [error] [client 216.217.36.130] Invalid URI in request GET somephoto.jpg HTTP/1.1
[Wed Aug 27 18:57:07 2003] [error] [client 216.217.36.130] Invalid URI in request GET somephotothumbnail.jpg HTTP/1.1
[Wed Aug 27 18:57:10 2003] [error] [client 216.217.36.130] Invalid URI in request GET sitelogo.gif\214 HTTP/1.1

All of the above files exist and "Invalid URI" is not how my log renders 404s; the 214 is certainly not a part of logo's file name.

216.217.36.128 - 216.217.36.159 owned by SonicWALL out of Sunnyvale, CA (just like our friends at bundy.infomaxinc.com)

coyote

[netcommr]

it looks like a business line from New Edge, dsl or t1 service routed through Transedge, so the requests could be human or software generated

[coyote]

The DNS lookup I did on the IP resolved to SonicWALL (global.sonicwall.com).
The website doesn't respond, and I've never heard of an ISP with that name.

It seems suspicious to me.

coyote

[wilderness]

Content Filtering Service

sonicwall dot com

came up instantly.

[coyote]

wilderness,

I kept getting an "Internal Server Error" when I typed the address into my browser. Though the site may have users behind firewalls - like myself - blocked.

coyote