User Tools

Site Tools

diy:network-recon

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
diy:network-recon [2024/06/08 03:01] – [ping] Humphrey Boa-Gartdiy:network-recon [2024/08/06 05:48] (current) – external edit 127.0.0.1
Line 3: Line 3:
 So you have decided to investigate a web site. This could be for any of a multitude of reasons, all of which are Irrelevant to the purposes of this article. The point is, this hypothetical site and its staff are asking for it, and you are about to give it to them. So you have decided to investigate a web site. This could be for any of a multitude of reasons, all of which are Irrelevant to the purposes of this article. The point is, this hypothetical site and its staff are asking for it, and you are about to give it to them.
  
-Lets say this site is [[http://scanme.nmap.org|scanme.nmap.org]]. So where to begin? To even start to do anything, you need to run some basic tools to profile where this site intersects with the rest of the internet, and the real world.+Lets say this site is, hypothetically, [[http://scanme.nmap.org|scanme.nmap.org]]. So where to begin? Before you can start to do anything (dox, attack, shut down, etc) you first need to run some basic tools. You have to profile where this site intersects with the rest of the internet, and the real world.
  
-===== Finding IP Addresses & Other Basic Info =====+===== Finding IP Addresses & DNS Info =====
  
-Every machine on the internet has an **IP address**, and every domain name resolves to an IP address. Domain names are only aliases for IP addresses because //whatever.com// is easier to remember than //187.158.173.109//. The inverse is not necessarily true. An IP may have no domain name pointing to it.+Every machine (or **host**) on the internet has an **IP address**, and every domain name resolves to an IP address. Domain names are only aliases for IP addresses because //whatever.com// is easier to remember than //187.158.173.109//. The inverse is not necessarily true. An IP may have no domain name pointing to it.
  
-Also note that several different sites under different domains may share an IP. Furthermore, different subdomains on the **same domain name** may resolve to //different// IP addresses.+Also note that several different sites under different domains **can share an IP**. Furthermore, different subdomains on the **same domain name** can resolve to //different IP addresses//.
  
 There are a handful of basic commands in *nix/Windows/MacOS that can reveal a site's IP address. Note that all of these commands will require [[tools:bash|Terminal]] or [[tools:powershell|PowerShell]]. There are a handful of basic commands in *nix/Windows/MacOS that can reveal a site's IP address. Note that all of these commands will require [[tools:bash|Terminal]] or [[tools:powershell|PowerShell]].
  
-==== ping (Cross-Platform) ====+==== ping ====
  
-The classic ''ping'' command works on pretty much everyone's machine, without having to install anything. It functions by sending an echo request to the IP address or domain name specified, and waiting to receive a reply back. While this command is most useful for diagnosing connection issues, it will also reveal the IP address for a domain:+The classic ''ping'' command works on pretty much everyone's machine, without having to install anything. It functions by sending a simple echo request to the IP address or domain name specified, and waiting to receive a reply back. While this command is most useful for diagnosing connection issues, a ping will also reveal the host IP address for a given domain:
  
   $ ping scanme.nmap.org   $ ping scanme.nmap.org
Line 38: Line 38:
 ==== nslookup ==== ==== nslookup ====
  
-Another commonly bundled command, ''nslookup'' checks DNS records to find the IP address of a given domain:+Another commonly bundled cross-platform command, ''nslookup'' checks DNS records to find the IP address formally associated with a given domain:
  
   $ nslookup scanme.nmap.org   $ nslookup scanme.nmap.org
Line 56: Line 56:
 ==== host ==== ==== host ====
  
-januszeal@sumomo ~ $ host www.google.com www.google.com is an alias for www.l.google.com. www.l.google.com has address 74.125.47.99 www.l.google.com has address 74.125.47.103 www.l.google.com has address 74.125.47.104 www.l.google.com has address 74.125.47.147+Sorry Windows users, but this one is for *nix systems (Unix, Linux, BSD, MacOS). The ''host'' command (much like ''nslookup'') is a quick way look up DNS information on domains and IP addresses: 
 + 
 +  $ host scanme.nmap.org 
 +  scanme.nmap.org has address 45.33.32.156 
 +  scanme.nmap.org has IPv6 address 2600:3c01::f03c:91ff:fe18:bb2f 
 +   
 +  $ host 45.33.32.156 
 +  156.32.33.45.in-addr.arpa domain name pointer scanme.nmap.org. 
 + 
 +Things we already knew. But what if we run ''host'' on the root domain? 
 + 
 +  $ host nmap.org 
 +  nmap.org has address 50.116.1.184 
 +  nmap.org has IPv6 address 2600:3c01:e000:3e6::6d4e:7061 
 +  nmap.org mail is handled by 1 aspmx.l.google.com. 
 +  nmap.org mail is handled by 5 alt1.aspmx.l.google.com. 
 +  nmap.org mail is handled by 5 alt2.aspmx.l.google.com. 
 +  nmap.org mail is handled by 10 aspmx2.googlemail.com. 
 +  nmap.org mail is handled by 10 aspmx3.googlemail.com. 
 +   
 +  $ host 50.116.1.184 
 +  184.1.116.50.in-addr.arpa domain name pointer ack.nmap.org. 
 + 
 +A treasure trove of information. Turns out the Nmap project is using [[https://workspace.google.com|Google Workspace]] to manage their email and who knows what else. Wild!
  
 ==== dig ==== ==== dig ====
  
-chance@AMD64:~$ dig www.google.com+Another popular *nix utility is the ''dig'' command: 
 + 
 +  $ dig scanme.nmap.org 
 + 
 +Which reveals the IP address in the "Answer Section": 
 + 
 +  ;; ANSWER SECTION: 
 +  scanme.nmap.org. 1943 IN A 45.33.32.156 
 + 
 +You can force ''dig'' to use specific DNS servers, instead of your local default. For example, to query [[https://quad9.net|Quad9]] about Nmap, you would run: 
 + 
 +  $ dig @9.9.9.9 scanme.nmap.org 
 + 
 +It can also do reverse DNS lookups: 
 + 
 +  $ dig -x 45.33.32.156 
 +  ... 
 +  ;; QUESTION SECTION: 
 +  ;156.32.33.45.in-addr.arpa. IN PTR 
 +   
 +  ;; ANSWER SECTION: 
 +  156.32.33.45.in-addr.arpa. 300 IN PTR scanme.nmap.org. 
 + 
 +Read more [[https://phoenixnap.com/kb/linux-dig-command-examples|dig command examples]]. 
 + 
 + 
 +===== WHOIS ===== 
 + 
 +[[wp>WHOIS]] is a query and response protocol that is used for querying databases that store an Internet resource's registered users or assignees. These resources include domain names, IP address blocks and autonomous systems, but it is also used for a wider range of other information. The protocol stores and delivers database content in a human-readable format. 
 + 
 +WHOIS lookups are a great way to find out more information about a web site or IP address. They can clue you in to who the target uses for a host or domain registrar, geographic locations, and sometimes even the real-world names & addresses of the site owners or administrators. WHOIS lookups are a necessary fundamental skill for  {{tagpage>recon}} and [[tactics:dox|doxxing]]. 
 + 
 +==== Domain Information ==== 
 + 
 +**WHOIS** lookups are extremely easy to do. That's what the ''whois'' command is for. Every domain registrar runs a WHOIS database for the domains it is hosting. These databases usually contain information about the owner & assigned contacts of the domain, such as email, phone, and street address. Keep in mind that some domain owners will lie about this, which can be grounds for domain suspension, but it is hardly enforced. Some domain owners subscribe to privacy services (such as **Domains by Proxy** or **Withheld for Privacy**) in which case you will have to try another way to get the information.
  
-<<>> DiG 9.5.0-P2 <<>> www.google.com +''whois'' generally doesn't like being run against subdomains, so you will have to point it at the root domain:
-global options +
-printcmd +
-Got answer +
-->>HEADER<<- opcode +
-QUERY, status: NOERROR, id: 48731 +
-flags +
-qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0 +
-QUESTION SECTION +
-www.google.com. IN A +
-ANSWER SECTION +
-www.google.com. 42327 IN CNAME www.l.google.com. www.l.google.com. 94 IN A 209.85.225.103 www.l.google.com. 94 IN A 209.85.225.99 www.l.google.com. 94 IN A 209.85.225.147 www.l.google.com. 94 IN A 209.85.225.104+
  
-Query time +  $ whois nmap.org
-2 msec +
-SERVER +
-10.10.256.1#53(10.10.256.1) +
-WHEN +
-Tue Mar 24 22:30:27 2009 +
-MSG SIZE rcvd +
-126+
  
-===== Web hosting =====+The lengthy results of this command (which we will not paste here) reveal that Nmap does in fact use one of the aforementioned domain privacy services. It also shows that they use [[https://www.dynadot.com|Dynadot]] as a domain registrar, which in turn points to [[https://linode.com|Linode's nameservers]], revealing two more of their service providers.
  
-Every site is being hosted on someone's server. Finding out which company hosts a site is a good way to find out what kind of bandwidth packages they have, etc.+==== More IP Information ====
  
-==== Finding domain name registrar ====+''whois'' can be run against IP addresses as well:
  
-  * go here http://whois.domaintools.com/ +  $ whois 45.33.32.156
-  * Enter the domain name +
-  * look for Registrar +
  
-=== *nix based systems ===+Running ''whois'' against either of Nmap's IP addresses brings up more information about Nmap's host, including the email address to send abuse and DMCA shutdown notices to. (Very exploitable.)
  
-On all *nix based systems it's pretty easy to find out any available details about a domain. That's what the command 'whois' is for. Every domain registrar runs a whois database for the domains it is hosting. Their database usually contains information about the owner of the domain, a technical and an administrative contact including addresses of them (admins doing semi-legal/illegal things may lie on these forms). Some registrars require that the administrative contact is a natural person, not an organization. Some domain owners subscribe to privacy services (such as Domains by Proxy) in which case you will have to try another way to get the information.+===== Browser Based Tools =====
  
-Usage example:+If you don't have access to the command line, there are a handful of sites you can use for DNS & WHOIS lookups in your browser:
  
-  $ whois partyvan.info+  * [[https://whois.domaintools.com|DomainTools]] 
 +  * [[https://lookup.icann.org/en|ICANN Lookup]] 
 +  * [[https://www.whois.com/whois/|Whois.com]] 
 +  * [[https://nslookup.io|NsLookup.io]]
  
-==== Finding host ====+===== More Things You Can Do =====
  
-Once you have an IP address, you can find out who is hosting a site.+Congratulations! You have now done the absolute bare minimum it takes to profile a web site. But what to do with this information? There are several directions in which you can proceed:
  
-  * go here [[https://www.ripe.net/db/whois.html]] +  * You can compile the info you found into [[tactics:dox|a dox file]] for the target. 
-  * enter IP address +  * You can [[arms:nmap|run a port scan]] on the host(s) to further profile the server environment(s) of the target.
-  * look for OrgName +
-  * ??? +
-  * PROFIT!+
  
 {{tag>Tutorials Recon}} {{tag>Tutorials Recon}}
diy/network-recon.1717815662.txt.gz · Last modified: 2024/08/06 05:54 (external edit)

Find this page online at: https://bestpoint.institute/diy/network-recon