Question

From looking at the traceroute underneath, how can I know what city the message city it leaves and what city it lands in Europe?

traceroute: Warning: bbc.uk.com has multiple addresses; using 212.58.244.210

traceroute to bbc.uk.com (212.58.244.210), 64 hops max, 72 byte packets

1 192.168.123.1 (192.168.123.1) 5.746 ms 2.225 ms 2.113 ms

2 192.168.219.1 (192.168.219.1) 260.894 ms 2.280 ms 2.845 ms

3 116.36.195.65 (116.36.195.65) 3.044 ms * 217.889 ms

4 10.204.106.165 (10.204.106.165) 4.215 ms 3.389 ms 3.619 ms

5 1.213.1.149 (1.213.1.149) 3.744 ms 4.277 ms 2.670 ms

6 1.208.1.237 (1.208.1.237) 3.225 ms 23.312 ms 4.090 ms

7 211.60.34.85 (211.60.34.85) 4.267 ms 7.741 ms 3.812 ms

8 1.208.165.133 (1.208.165.133) 4.318 ms 5.339 ms 5.171 ms

9 1.208.144.117 (1.208.144.117) 4.217 ms 4.928 ms 4.199 ms

10 1.208.175.18 (1.208.175.18) 491.287 ms 561.986 ms 342.961 ms

11 210.120.197.178 (210.120.197.178) 146.229 ms 140.608 ms

203.233.52.18 (203.233.52.18) 254.113 ms

12 61.42.234.6 (61.42.234.6) 481.847 ms 151.606 ms 369.450 ms

13 * ae-1-3104.ear2.london2.level3.net (4.69.143.190) 514.351 ms *

14 unknown.level3.net (212.187.139.230) 342.671 ms 362.317 ms 275.201 ms

15 * * *

16 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 441.110 ms 504.967 ms 470.210 ms

17 132.185.255.148 (132.185.255.148) 275.142 ms 274.162 ms 279.260 ms

18 bbc-vip174.telhc.bbc.co.uk (212.58.244.210) 498.278 ms 571.531 ms 616.313 ms

Answer 1

The tracert shows three columns of information -

• First column gives you the hop number
• Second column gives you the location of the current packet, which is the IP address
• Third, Fourth and Fifth column are the ping timing on that IP address

To know the approximate location of each of the IP address you can run the WHOIS tool or you can run the online tool to get the information of each IP address

Here I ran the IP - 192.168.123.1 (Hop number 1) and we can see a lot of information came out.

You can run this for every IP which the packet crosses during the traceroute session to get an idea of how the packet is being moving to its destination

NetRange:       192.168.0.0 - 192.168.255.255
CIDR:           192.168.0.0/16
NetName:        PRIVATE-ADDRESS-CBLK-RFC1918-IANA-RESERVED
NetHandle:      NET-192-168-0-0-1
Parent:         NET192 (NET-192-0-0-0-0)
NetType:        IANA Special Use
OriginAS:
Organization:   Internet Assigned Numbers Authority (IANA)
RegDate:        1994-03-15
Updated:        2013-08-30
Comment:        These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices.  They are only intended for use within a private context  and traffic that needs to cross the Internet will need to use a different, unique address.
Comment:
Comment:        These addresses can be used by anyone without any need to coordinate with IANA or an Internet registry.  The traffic from these addresses does not come from ICANN or IANA.  We are not the source of activity you may see on logs or in e-mail records.  Please refer to http://www.iana.org/abuse/answers
Comment:
Comment:        These addresses were assigned by the IETF, the organization that develops Internet protocols, in the Best Current Practice document, RFC 1918 which can be found at:
Comment:        http://datatracker.ietf.org/doc/rfc1918
Ref:            https://rdap.arin.net/registry/ip/192.168.0.0



OrgName:        Internet Assigned Numbers Authority
OrgId:          IANA
Address:        12025 Waterfront Drive
Address:        Suite 300
City:           Los Angeles
StateProv:      CA
PostalCode:     90292
Country:        US
RegDate:
Updated:        2012-08-31
Ref:            https://rdap.arin.net/registry/entity/IANA


OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName:   ICANN
OrgAbusePhone:  +1-310-301-5820
OrgAbuseEmail:  [email protected]
OrgAbuseRef:    https://rdap.arin.net/registry/entity/IANA-IP-ARIN

OrgTechHandle: IANA-IP-ARIN
OrgTechName:   ICANN
OrgTechPhone:  +1-310-301-5820
OrgTechEmail:  [email protected]
OrgTechRef:    https://rdap.arin.net/registry/entity/IANA-IP-ARIN

IP - 212.58.244.210 (Hop number - 18)

NetRange:       212.0.0.0 - 212.255.255.255
CIDR:           212.0.0.0/8
NetName:        RIPE-NCC-212
NetHandle:      NET-212-0-0-0-1
Parent:          ()
NetType:        Allocated to RIPE NCC
OriginAS:
Organization:   RIPE Network Coordination Centre (RIPE)
RegDate:        1997-11-14
Updated:        2009-03-25
Comment:        These addresses have been further assigned to users in
Comment:        the RIPE NCC region. Contact information can be found in
Comment:        the RIPE database at http://www.ripe.net/whois
Ref:            https://rdap.arin.net/registry/ip/212.0.0.0

ResourceLink:  https://apps.db.ripe.net/search/query.html
ResourceLink:  whois.ripe.net


OrgName:        RIPE Network Coordination Centre
OrgId:          RIPE
Address:        P.O. Box 10096
City:           Amsterdam
StateProv:
PostalCode:     1001EB
Country:        NL
RegDate:
Updated:        2013-07-29
Ref:            https://rdap.arin.net/registry/entity/RIPE

ReferralServer:  whois://whois.ripe.net
ResourceLink:  https://apps.db.ripe.net/search/query.html

OrgTechHandle: RNO29-ARIN
OrgTechName:   RIPE NCC Operations
OrgTechPhone:  +31 20 535 4444
OrgTechEmail:  [email protected]
OrgTechRef:    https://rdap.arin.net/registry/entity/RNO29-ARIN

OrgAbuseHandle: ABUSE3850-ARIN
OrgAbuseName:   Abuse Contact
OrgAbusePhone:  +31205354444
OrgAbuseEmail:  [email protected]
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE3850-ARIN

Thanks