-----Original Message-----
From: First Last [mailto:c01n0p@yahoo.com]
Sent: Sunday, July 17, 2005 11:50 AM
To: pen-test@securityfocus.com
Subject: list of address that you don't want to scan

FYI...

Original site link -
http://professionalsecuritytester.com/modules.php?name=News&file=article&sid=70

IP address you should NOT scan
Posted by cdupuis on Thursday, April 01 @ 09:38:09 CST Contributed by cdupuis

The Government Security website at
http://www.governmentsecurity.org has produced a nice list of IP address you should be aware of as a tester.
They are mostly government agencies addresses and could quickly get you in trouble if you would scan them by mistake.

Click on Read More... below see the whole list

Enjoy!

Clement

--------------------------------------------------------------------------------
With kindly thanks to Mountainman, the list of dangerosly ranges is updated again!!!
-------------------------------------------------

RANGE 6
6.* - Army Information Systems Center

RANGE 7
7.*.*.* Defense Information Systems Agency, VA

RANGE 11
11.*.*.* DoD Intel Information Systems, Defense Intelligence Agency, Washington DC

RANGE 21
21. - US Defense Information Systems Agency

RANGE 22
22.* - Defense Information Systems Agency

RANGE 24
24.198.*.*

RANGE 25
25.*.*.* Royal Signals and Radar Establishment, UK

RANGE 26
26.* - Defense Information Systems Agency

RANGE 29
29.* - Defense Information Systems Agency

RANGE 30
30.* - Defense Information Systems Agency

RANGE 49
49.* - Joint Tactical Command

RANGE 50
50.* - Joint Tactical Command

RANGE 55
55.* - Army National Guard Bureau

RANGE 55
55.* - Army National Guard Bureau

RANGE 62
62.0.0.1 - 62.30.255.255 Do not scan!

RANGE 64
64.70.*.* Do not scan
64.224.* Do not Scan
64.225.* Do not scan
64.226.* Do not scan

RANGE 128
128.37.0.0 Army Yuma Proving Ground
128.38.0.0 Naval Surface Warfare Center
128.43.0.0 Defence Research Establishment-Ottawa 128.47.0.0 Army Communications Electronics Command 128.49.0.0 Naval Ocean Systems Center 128.50.0.0 Department of Defense 128.51.0.0 Department of Defense 128.56.0.0 U.S. Naval Academy 128.60.0.0 Naval Research Laboratory 128.63.0.0 Army Ballistics Research Laboratory 128.80.0.0 Army Communications Electronics Command 128.98.0.0 - 128.98.255.255 Defence Evaluation and Research Agency 128.102.0.0 NASA Ames Research Center 128.149.0.0 NASA Headquarters 128.154.0.0 NASA Wallops Flight Facility 128.155.0.0 NASA Langley Research Center 128.156.0.0 NASA Lewis Network Control Center 128.157.0.0 NASA Johnson Space Center 128.158.0.0 NASA Ames Research Center 128.159.0.0 NASA Ames Research Center 128.160.0.0 Naval Research Laboratory 128.161.0.0 NASA Ames Res... [ Read More (4.7k in body) ]

Sites you should never *ever* scan

At the end of the day, Google's Davidson says that his biggest worry is not for Google but for the prospect of bringing fresh innovation to the Internet. After all, if worse comes to worst, Google can pay AT&T or BellSouth to maintain its role as the Internet's dominant search engine. But the bright young start-up with the next big innovative idea won't have that option.

This is exactly my concern.

Who really gets hurt by 'prioritization' of the Internet

Very cool ...

A matrix giving the traffic volumes between origin and destination in a network has tremendously potential utility for network capacity planning and management.

Unfortunately, traffic matrices are generally unavailable in large operational IP networks. On the other hand, link load measurements are readily available in IP networks.

In this paper, we propose a new method for practical and rapid inference of traffic matrices in IP networks from link load measurements, augmented by readily available network and routing configuration information.

We apply and validate the method by computing backbone-router to backbone-router traffic matrices on a large operational tier-1 IP network -- a problem an order of magnitude larger than any other comparable method has tackled. The results show that the method is remarkably fast and accurate, delivering the traffic matrix in under five seconds.

Fast Accurate Computation of Large-Scale IP Traffic Matrices from Link Loads

Developers are just beginning to understand the meaning of personal time. Most obvious is calendars, scheduling, events, resource allocation over time (aka project management). But there are also less obvious ways time matters in software: how people work and think over time; how human relationships, article relevance, and purchase intentions and other commercial considerations change over time; how time patterns infuse a variety of applications; and how a sense of timing can improve the utility of everything from search results to social-network-driven tools.

The online world needs to get better at time-stamping content and activities and at standards for representing time and events - both times and durations, and all the patterns in time: speed, decay, growth, recurrence, (changing) frequency of events.

MemeStreams is a gold mine of untapped timing information.

When 2.0: Time and Timing