PacketExchange

[wilderness]

Class D is irrelevant.
I've 2008 &09 references to ScanSafe in which they were using the Mzima Networks.

69.174.58.zzz - - [10/Apr/2012:20:02:08 +0100] "GET /MyFoldert/MySub/MyPage.html HTTP/1.1" 200 49634 "-" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)"

PacketExchange, Inc NETBLK-PACKETEXCHANGE-V4-07 69.174.0.0 - 69.174.127.255
ScanSafe Inc. MZIMA08-CUST-SCANSAFE04 69.174.58.0 - 69.174.58.255

The images were grabbed on an entirely different and unrelated URL (likely an open proxy).

This page gets regular activity from ranges looking for a way to circumvent other denied ranges.

I'm certainly not allowing access to an PacektExchange.
Although it goes on behind the scenes, this is an open challenge.

[motorhaven]

Question... by blocking Scanscafe is there a risk of blocking legitimate corporate users?

[wilderness]

I'm sure there is, however I'm denying PacketExchange, which ScanSoft utilizes.

[motorhaven]

Okay, I just checked my registration logs. I have a boatload of legitimate users registered from 69.174.0.0 - 69.174.127.255. In 69.174.58.0 - 69.174.58.255 I show 10 legitimate registered users. So I can't block those out, much of my traffic is during business hours from larger corporations. :(

[wilderness]

motorhaven,
We each must determine what is beneficial or detrimental to our own website (s).

If you wish to allow just the ScanSoftRange 69.174.58.?
69\.174\.([0-9]|[1-46-9][0-9]|5[0-79]|1[01][0-9]|12[0-7])\.

[dstiles]

I block both scansafe and packetexchange but I didn't have the 69.174 ranges. Thanks for the heads-up, folks.