02.11.2014 Views

untangling_the_web

untangling_the_web

untangling_the_web

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DOClD: 4046925<br />

UNCLASSIFIEDJlFQR QFFIGIAL l:JSE QNLY<br />

possible for users to navigate <strong>the</strong> <strong>web</strong> and which Internet resources <strong>the</strong>se tools<br />

access in order to provide information about domain names and IP addresses.<br />

After <strong>the</strong> DNS, <strong>the</strong> Whois databases maintained by <strong>the</strong> Regional Internet Registries<br />

are <strong>the</strong> second major source of information about Internet addresses. The Whois<br />

databases contain records of IP address registrations. Searches that access <strong>the</strong><br />

Whois databases are generally known as network lookups or network Whois<br />

lookups. In contrast to <strong>the</strong> DNS, <strong>the</strong> five Whois databases-ARIN, APNIC, AfriNIC,<br />

LACNIC, and RIPE-are not distributed on servers across <strong>the</strong> Internet but must be<br />

queried individually. In addition, <strong>the</strong>se databases are designed to search on IP<br />

addresses, not domain names. A different type of tool should be used when<br />

searching on domain names. Unfortunately, to add to <strong>the</strong> confusion, this tool is also<br />

referred to as a Whois lookup!<br />

In order to distinguish this third major resource from "true" Whois lookups, I will call it<br />

domain name (Whois) lookup. Domain name lookups search one or more domain<br />

name registries. Domain name registries are <strong>the</strong> places on <strong>the</strong> Internet where<br />

individuals and organizations go to register a name generally intended to be<br />

associated with a <strong>web</strong>site, e.g., amazon.com. These registries include <strong>the</strong> generic<br />

top-level domain (gTLD) registries for .com, .net, .org, .biz, .info, and a few o<strong>the</strong>r<br />

gTLDs, as well as country code top-level domain (ccTLD) registries, e.g., .uk, .it,<br />

.ru, et al. Domain name (Whois) lookups differ from network Whois lookups in that<br />

<strong>the</strong>y are primarily designed to search on a domain name instead of an IP address.<br />

All of <strong>the</strong> domain lookup tools described here can search more than one domain<br />

registry, and in some cases, will automatically search across all of <strong>the</strong>m.<br />

These are <strong>the</strong> various types of lookups that can be performed to learn more about<br />

Internet addresses.<br />

~ NSLookup-input format: ei<strong>the</strong>r IP address or domain name<br />

Using <strong>the</strong> DNS, a domain name is converted to its IP address (forward DNS<br />

lookup) or an IP address is converted to its host name (reverse DNS lookup).<br />

NSLookup is a UNIX tool that allows anyone using <strong>the</strong> Internet to access <strong>the</strong><br />

DNS and match domain names to IP addresses, or vice versa. Web interface<br />

query forms for NSLookup are very numerous. Although NSLookup doesn't do<br />

anything more than match domain names and IP addresses, this may be all you<br />

need or may give you <strong>the</strong> information you need to keep looking. For example, I<br />

have had domain names I could not match to any IP number using a Whois<br />

search. By running an NSLookup query I have found an IP number that I could<br />

<strong>the</strong>n use to track down registration information about that domain.<br />

The advantage of NSLookup is that, unlike Whois requests, NSLookup queries<br />

can be run from anywhere on <strong>the</strong> Internet because <strong>the</strong> DNS data is not located<br />

in one database on one server but is distributed across a collection of inter-<br />

452 UNCLASSIFIEDllf6R OFFICIAL l:JSE ONLY

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!