well ping can do the IP side of things:
Code:
iMac:~ andrew$ ping google.com
PING google.com (72.14.207.99): 56 data bytes
64 bytes from 72.14.207.99: icmp_seq=0 ttl=243 time=46.494 ms
64 bytes from 72.14.207.99: icmp_seq=1 ttl=243 time=48.853 ms
64 bytes from 72.14.207.99: icmp_seq=2 ttl=243 time=46.143 ms
64 bytes from 72.14.207.99: icmp_seq=3 ttl=243 time=45.305 ms
64 bytes from 72.14.207.99: icmp_seq=4 ttl=243 time=44.511 ms
64 bytes from 72.14.207.99: icmp_seq=5 ttl=243 time=45.666 ms
64 bytes from 72.14.207.99: icmp_seq=6 ttl=243 time=48.832 ms
64 bytes from 72.14.207.99: icmp_seq=7 ttl=243 time=46.140 ms
^X64 bytes from 72.14.207.99: icmp_seq=8 ttl=243 time=47.808 ms
^C
--- google.com ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max/stddev = 44.511/46.639/48.853/1.447 ms
iMac:~ andrew$
dig can get some info too:
Code:
iMac:~ andrew$ dig google.com
; <<>> DiG 9.4.1-P1 <<>> google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39568
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 130 IN A 64.233.167.99
google.com. 130 IN A 72.14.207.99
google.com. 130 IN A 64.233.187.99
;; AUTHORITY SECTION:
google.com. 296061 IN NS ns3.google.com.
google.com. 296061 IN NS ns4.google.com.
google.com. 296061 IN NS ns1.google.com.
google.com. 296061 IN NS ns2.google.com.
;; ADDITIONAL SECTION:
ns1.google.com. 296204 IN A 216.239.32.10
ns2.google.com. 296200 IN A 216.239.34.10
ns3.google.com. 296204 IN A 216.239.36.10
ns4.google.com. 296100 IN A 216.239.38.10
;; Query time: 195 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sun Apr 13 16:26:01 2008
;; MSG SIZE rcvd: 212
iMac:~ andrew$
traceroute will give you the IPs hopped to the destination:
Code:
iMac:~ andrew$ traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 72.14.207.99
traceroute to google.com (72.14.207.99), 64 hops max, 40 byte packets
1 home (192.168.0.1) 1.739 ms 1.525 ms 0.944 ms
2 adsl-69-215-159-254.dsl.milwwi.ameritech.net (69.215.159.254) 11.012 ms 10.591 ms 11.435 ms
3 dist2-vlan50.milwwi.ameritech.net (65.43.19.227) 12.141 ms 11.393 ms 11.645 ms
4 151.164.190.136 (151.164.190.136) 9.810 ms 11.204 ms 11.637 ms
5 bb2-p11-0.milwwi.ameritech.net (151.164.190.98) 11.794 ms 11.013 ms 11.731 ms
6 151.164.93.49 (151.164.93.49) 202.950 ms 66.290 ms 204.988 ms
7 151.164.251.226 (151.164.251.226) 13.979 ms 13.163 ms 13.730 ms
8 216.239.46.246 (216.239.46.246) 13.903 ms 81.997 ms 216.239.46.245 (216.239.46.245) 13.508 ms
9 72.14.236.20 (72.14.236.20) 42.476 ms 209.85.250.110 (209.85.250.110) 42.462 ms 119.469 ms
10 66.249.94.92 (66.249.94.92) 45.192 ms 44.431 ms 72.14.236.183 (72.14.236.183) 47.076 ms
11 66.249.94.50 (66.249.94.50) 52.280 ms 72.14.236.20 (72.14.236.20) 42.220 ms 42.539 ms
12 eh-in-f99.google.com (72.14.207.99) 45.596 ms 44.820 ms 49.359 ms
iMac:~ andrew$
And for locating the owner of a domain:
Code:
iMac:~ andrew$ whois 72.14.207.99
OrgName: Google Inc.
OrgID: GOGL
Address: 1600 Amphitheatre Parkway
City: Mountain View
StateProv: CA
PostalCode: 94043
Country: US
NetRange: 72.14.192.0 - 72.14.255.255
CIDR: 72.14.192.0/18
NetName: GOOGLE
NetHandle: NET-72-14-192-0-1
Parent: NET-72-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.GOOGLE.COM
NameServer: NS2.GOOGLE.COM
NameServer: NS3.GOOGLE.COM
NameServer: NS4.GOOGLE.COM
Comment:
RegDate: 2004-11-10
Updated: 2007-04-10
RTechHandle: ZG39-ARIN
RTechName: Google Inc.
RTechPhone: +1-650-318-0200
RTechEmail: arin-contact@google.com
OrgTechHandle: ZG39-ARIN
OrgTechName: Google Inc.
OrgTechPhone: +1-650-318-0200
OrgTechEmail: arin-contact@google.com
# ARIN WHOIS database, last updated 2008-04-12 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
iMac:~ andrew$
And to find which isp issues the IP address, dig or whois it. For example I am with ATT Milwaukee WI. My IP is 69.215.152.59 :
Code:
iMac:~ andrew$ dig 69.215.152.59
; <<>> DiG 9.4.1-P1 <<>> 69.215.152.59
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8110
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;69.215.152.59. IN A
;; AUTHORITY SECTION:
. 10800 IN SOA A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2008041300 1800 900 604800 86400
;; Query time: 184 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sun Apr 13 16:33:19 2008
;; MSG SIZE rcvd: 106
iMac:~ andrew$ whois 69.215.152.59
AT&T Internet Services SBCIS-SIS80 (NET-69-208-0-0-1)
69.208.0.0 - 69.223.255.255
rback8b.milwwi SBC06921514400020041214123132 (NET-69-215-144-0-1)
69.215.144.0 - 69.215.159.255
# ARIN WHOIS database, last updated 2008-04-12 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
iMac:~ andrew$
Since there are hosting solutions and soforth, it can be difficult without a warrant to get more specific data. And thats fine. If there is an issue with a computer on a particular IP, find out who manages the domain, whois it, and contact the company behind it. If there is a legal problem, have your attorney do the contact. You are better off with the legal side of things covered from the beginning. Trust me, even with good intent, you may end up opening your ass up for a world of woe without the attorney getting involved first.
HTH.
For reference:
http://www.dnsstuff.com/
Bookmarks