traceroute to 96.110.235.69 (96.110.235.69), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 7.873 ms 7.813 ms 7.841 ms
2 19541.your-cloud.host (168.119.217.134) 0.678 ms 0.651 ms 0.968 ms
3 * * *
4 static.125.14.46.78.clients.your-server.de (78.46.14.125) 30.894 ms 30.883 ms static.121.14.46.78.clients.your-server.de (78.46.14.121) 1.652 ms
5 spine14.cloud1.nbg1.hetzner.com (213.133.114.5) 32.907 ms spine11.cloud1.nbg1.hetzner.com (85.10.250.73) 17.366 ms spine11.cloud1.nbg1.hetzner.com (85.10.246.121) 17.342 ms
6 213-239-239-121.clients.your-server.de (213.239.239.121) 4.184 ms static.213-133-112-65.clients.your-server.de (213.133.112.65) 0.501 ms 7.338 ms
7 core4.fra.hetzner.com (213.239.245.245) 3.640 ms 3.463 ms 3.553 ms
8 * 195.219.223.8 (195.219.223.8) 3.821 ms 3.786 ms
9 * * *
10 * if-ae-55-2.tcore2.pvu-paris.as6453.net (80.231.245.6) 91.745 ms *
11 * * *
12 if-ae-55-4.tcore1.pye-paris.as6453.net (80.231.153.169) 90.941 ms * *
13 * if-ae-3-2.tcore1.l78-london.as6453.net (80.231.154.143) 91.488 ms 95.825 ms
14 if-ae-66-2.tcore3.nto-newyork.as6453.net (80.231.130.106) 92.273 ms 91.299 ms 92.004 ms
15 if-be-2-2.ecore1.n75-newyork.as6453.net (66.110.96.62) 91.100 ms 91.107 ms 90.883 ms
16 if-ae-57-2.tcore1.n75-newyork.as6453.net (66.110.96.58) 91.333 ms 91.514 ms 91.236 ms
17 66.110.96.114 (66.110.96.114) 91.576 ms 91.419 ms 91.199 ms
18 be-3412-cs04.newyork.ny.ibone.comcast.net (96.110.34.45) 94.925 ms be-3112-cs01.newyork.ny.ibone.comcast.net (96.110.34.33) 94.143 ms be-3212-cs02.newyork.ny.ibone.comcast.net (96.110.34.37) 94.257 ms
19 be-1312-cr12.newyork.ny.ibone.comcast.net (96.110.35.138) 95.355 ms be-1212-cr12.newyork.ny.ibone.comcast.net (96.110.35.134) 93.911 ms be-1312-cr12.newyork.ny.ibone.comcast.net (96.110.35.138) 94.270 ms
20 be-304-cr11.newark.nj.ibone.comcast.net (68.86.84.245) 94.696 ms be-302-cr11.newark.nj.ibone.comcast.net (96.110.36.149) 94.459 ms 94.320 ms
21 be-1111-cs01.newark.nj.ibone.comcast.net (96.110.35.65) 94.517 ms be-1311-cs03.newark.nj.ibone.comcast.net (96.110.35.73) 94.333 ms be-1411-cs04.newark.nj.ibone.comcast.net (96.110.35.77) 94.116 ms
22 96.110.42.78 (96.110.42.78) 99.251 ms 96.110.42.70 (96.110.42.70) 98.922 ms 99.272 ms
23 96.216.191.170 (96.216.191.170) 97.323 ms * ae-0-0-sur01.longhill.md.bad.comcast.net (68.85.115.2) 95.342 ms
No results found, please run it to get the result.
Search for references
This is the search mode - you can use it to find references to any host in our cache. Just type the specified host and hit enter or click the button.
Nslookup arguments and description
NSLOOKUP is a programm for querying NS server for a specified domain. This tool is commonly used for detecting the IP address of the domain (A record), but can be used for receiving other NS records. It is very similar to DIG command. Unlike DIG, NSLOOKUP is based on its own resolver library.
Host
Requierd argument, specifies the host about which is querying the information.
NS server
Optional argument, specifies which NS server to query.
Type
Port
Optional argument, specifies the NS server port (53 by default)
Debug
Debug2
Ping arguments and description
PING is the network command, which lets you check whether or not the host is alive and responding. The special protocol ICMP is used for pinging. See RFC 792 for ICMP protocol details. You can find the command arguments below.
Host
Requierd argument, can be an IP or domain name.
Protocol
Packet size
By default it is 56 bytes, which translates into 64 ICMP data bytes (8 bytes of ICMP header are added)
Map IP
MTU
Timestamp
Whois arguments and description
WHOIS searches Whois servers for the object (domain or IP). The special WHOIS protocol is used for querying the Whois servers. See RFC 3912 for the protocol specification. This command is available on all linux systems and has a lot of arguments. The most important argument is host address. See the arguments decription below.
Host
Requierd argument, can be an IP or domain name.
Host arguments and description
HOST is a DNS lookup utility. You can use it to convert names to IP addresses and vice versa. It is similar to DIG and NSLOOKUP. This command is available on all linux distributives. There are several arguments. You can find decription of the arguments below.
Host
Requierd argument, can be an IP or domain name.
NS server
Optional argument, can be an IP or domain of name server
Protocol
Type
All
Verbose mode
Traceroute arguments and description
TRACEROUTE is the network diagnostic command. This command tracks the route packets taken from an IP network on their way to a given host. ICMP or UDP packets are used. See the command arguments below.
Host
Requierd argument, can be an IP or domain name.
Fragmentation
ICMP
TCP
Map IP
Protocol
Port
For UDP specifies the destination port
Geoiplookup arguments and description
GEOIPLOOKUP lets you detect the location of a host. A preparsed WHOIS database is used for detecting the location of IP or domain. There are a lot of independent geoip databases in the Internet, so the same host can have different locations in those databases. GEOIPLOOKUP is not a built-in Linux command. The command has only one argument - host address.
Host
Requierd argument, can be an IP address only
Dig arguments and description
The DIG command is a part of BIND package, available on all linux distributives. It is used for querying Domain Name Servers (DNS) using standard operating system libraries and display answers from these DNS servers. Domain Information Groper (DIG) is useful for troubleshooting DNS issues. You can find DIG arguments below.
Host
Requierd argument, can be an IP or domain name.
NS server
Requierd argument, can be an IP or domain name.
Type
Trace
Tcp
Ignore
AA only
AD flag
CD flag
Show class
Show TTL
Answer
Comments
Recurse
Short
Cmd
Identify
Stats
Authority
Additional
All
Multiline
One SOA
Fail
Best effort
DNSSEC
EDNS ID request
Cached: 2022.07.13 21:21:22/ 1 year 9 months ago Confirmed: 2022.12.01 19:36:30/ 1 year 5 months ago History: 2 records (hide history)
traceroute to 96.110.235.69 (96.110.235.69), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 9.797 ms 9.552 ms 9.697 ms
2 16781.your-cloud.host (49.12.139.252) 0.674 ms 0.747 ms 0.706 ms
3 * * *
4 static.88.198.133.237.clients.your-server.de (88.198.133.237) 1.329 ms static.88.198.133.233.clients.your-server.de (88.198.133.233) 1.683 ms static.88.198.133.237.clients.your-server.de (88.198.133.237) 1.879 ms
5 static.213-133-108-149.clients.your-server.de (213.133.108.149) 1.398 ms spine12.cloud1.nbg1.hetzner.com (78.47.3.45) 1.613 ms spine14.cloud1.nbg1.hetzner.com (213.133.112.109) 3.383 ms
6 213-239-239-121.clients.your-server.de (213.239.239.121) 8.402 ms 213-239-239-141.clients.your-server.de (213.239.239.141) 0.780 ms static.213-133-112-73.clients.your-server.de (213.133.112.73) 7.683 ms
7 juniper5.dc2.nbg1.hetzner.com (213.239.229.162) 0.962 ms juniper5.dc2.nbg1.hetzner.com (213.239.229.166) 0.345 ms 0.458 ms
8 nug-b1-link.ip.twelve99.net (62.115.183.232) 1.021 ms nug-b1-link.ip.twelve99.net (213.248.70.0) 0.813 ms 0.829 ms
9 prs-bb2-link.ip.twelve99.net (62.115.112.214) 15.121 ms 15.134 ms ffm-bb1-link.ip.twelve99.net (62.115.113.146) 3.824 ms
10 rest-bb1-link.ip.twelve99.net (62.115.122.159) 95.819 ms prs-bb1-link.ip.twelve99.net (62.115.123.13) 13.056 ms 12.831 ms
11 ash-b2-link.ip.twelve99.net (62.115.123.123) 96.664 ms ash-bb2-link.ip.twelve99.net (62.115.112.242) 97.589 ms ash-b2-link.ip.twelve99.net (62.115.123.123) 96.620 ms
12 ash-b2-link.ip.twelve99.net (62.115.123.125) 98.486 ms 97.573 ms comcast-ic355279-ash-b2.ip.twelve99-cust.net (62.115.51.194) 95.606 ms
13 be-3411-cs04.beaumeade.va.ibone.comcast.net (96.110.32.133) 96.321 ms comcast-ic355279-ash-b2.ip.twelve99-cust.net (62.115.51.194) 99.165 ms 97.832 ms
14 be-3211-cs02.beaumeade.va.ibone.comcast.net (96.110.32.125) 99.307 ms be-3411-cs04.beaumeade.va.ibone.comcast.net (96.110.32.133) 98.028 ms be-3211-cs02.beaumeade.va.ibone.comcast.net (96.110.32.125) 100.074 ms
15 96.110.40.30 (96.110.40.30) 94.299 ms * *