Discovering and defining the network range can
be another important footprinting step to consider. Knowing where the
target’s IP addresses start and stop greatly limits the time you’ll need
to spend figuring out specifics later—provided, of course, your
target operates in their own IP range. If your objective happens to run
services in a cloud (and rest easy, dear reader, we have another entire
chapter dedicated to cloud upcoming), this may prove somewhat
frustrating, but at least you’ll know what you’re up against. One of the
easiest ways to see what range the organization owns or operates
in—at least on a high level—is to make use of freely available
registry information.
For example, suppose you knew the IP address of a WWW
server (easy enough to discover, as you just learned in the previous
sections). If you simply enter that IP address in www.arin.net, the network
range will be shown. Entering the IP address of www.mheducation.com
(54.164.59.97) gives us the entire network range. In this case, the response
displays a range owned and operated by Amazon services, indicating MH Education
is making use of Amazon’s cloud services. ARIN also provides a lot of other
useful information as well, including the administrative and technical point of
contact (POC) for the IP range. In this case, the contacts displayed point us,
again, to Amazon web services POC’s, letting us know MH Education is relying on
Amazon’s security measures and controls (in part) to protect their resources.
Another tool available for network mapping
is traceroute (or tracert hostname on Windows systems),
which is a command-line tool that tracks a packet across the Internet and
provides the route path and transit times. It accomplishes this by
using ICMP ECHO packets (UDP datagrams in Linux versions) to report
information on each “hop” (router) from the source to the destination. The
TTL on each packet increments by one after each hop is hit and
returns, ensuring the response comes back explicitly from that hop and
returns its name and IP address. Using this, an ethical hacker can build
a picture of the network. For example, consider a traceroute command
output from my laptop here in Melbourne, Florida, to a local surf shop
just down the road (names and IPs were changed to protect
the innocent).