No results found, please run it to get the result.
Cached: 2022.03.02 00:08:30/ 2 years 8 months ago
traceroute to amiami.com (113.39.94.212), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 8.019 ms 8.167 ms 8.200 ms
2 14715.your-cloud.host (49.12.137.112) 0.425 ms 0.382 ms 0.392 ms
3 * * *
4 static.88-198-249-57.clients.your-server.de (88.198.249.57) 1.195 ms static.88-198-249-61.clients.your-server.de (88.198.249.61) 1.051 ms static.88-198-249-57.clients.your-server.de (88.198.249.57) 1.374 ms
5 spine12.cloud1.nbg1.hetzner.com (78.47.3.41) 1.125 ms static.213-133-108-149.clients.your-server.de (213.133.108.149) 1.508 ms 0.954 ms
6 static.213-133-112-65.clients.your-server.de (213.133.112.65) 0.534 ms 213-239-239-121.clients.your-server.de (213.239.239.121) 0.386 ms static.213-133-112-69.clients.your-server.de (213.133.112.69) 0.607 ms
7 core0.fra.hetzner.com (213.239.252.21) 4.931 ms 4.675 ms core4.fra.hetzner.com (213.239.245.245) 3.395 ms
8 ULCO01.telstraglobal.net (80.81.193.79) 16.337 ms 16.318 ms 16.282 ms
9 i-1002.ulhc-core02.telstraglobal.net (202.84.178.65) 24.026 ms i-1007.ulcn-core01.telstraglobal.net (202.84.178.53) 16.771 ms i-1002.ulhc-core02.telstraglobal.net (202.84.178.65) 24.044 ms
10 i-10147.unse-core01.telstraglobal.net (202.84.141.145) 86.551 ms i-1022.ulhc-core02.telstraglobal.net (202.84.141.230) 82.220 ms 82.096 ms
11 i-10848.eqnx-core02.telstraglobal.net (202.40.148.97) 150.699 ms i-1.tlot-core02.telstraglobal.net (202.84.252.85) 144.433 ms i-1022.ny8a-core01.telstraglobal.net (202.84.141.229) 91.452 ms
12 i-1.tlot-core02.telstraglobal.net (202.84.252.85) 261.257 ms i-15708.siko-core01.telstraglobal.net (202.84.141.2) 266.393 ms 266.298 ms
13 i-1.tlot-core02.telstraglobal.net (202.84.252.85) 269.828 ms i-15708.siko-core01.telstraglobal.net (202.84.141.2) 261.774 ms i-14205.jtha-core02.telstraglobal.net (202.84.141.201) 261.191 ms
14 i-14205.jtha-core02.telstraglobal.net (202.84.141.201) 252.247 ms 251.736 ms i-93.jtha01.telstraglobal.net (202.84.148.70) 274.419 ms
15 i-14205.jtha-core02.telstraglobal.net (202.84.141.201) 260.849 ms i-93.jtha01.telstraglobal.net (202.84.148.70) 270.723 ms unknown.telstraglobal.net (210.57.59.238) 249.945 ms
16 163.139.36.2 (163.139.36.2) 264.146 ms unknown.telstraglobal.net (210.57.79.126) 251.113 ms 246.333 ms
17 163.139.36.2 (163.139.36.2) 265.082 ms 163.139.77.10 (163.139.77.10) 322.118 ms 163.139.36.2 (163.139.36.2) 260.490 ms
18 163.139.77.10 (163.139.77.10) 318.388 ms 312.358 ms 163.139.36.14 (163.139.36.14) 272.475 ms
19 61.122.118.214 (61.122.118.214) 271.437 ms 221x112x15x94.ap221.ftth.ucom.ne.jp (221.112.15.94) 267.232 ms 61.122.118.214 (61.122.118.214) 271.400 ms
20 221x112x15x90.ap221.ftth.ucom.ne.jp (221.112.15.90) 262.167 ms 259.399 ms 221x240x30x234.ap221.ftth.ucom.ne.jp (221.240.30.234) 274.583 ms
21 58x159x231x146.ap58.ftth.ucom.ne.jp (58.159.231.146) 260.067 ms * *
22 * * 58x159x231x146.ap58.ftth.ucom.ne.jp (58.159.231.146) 271.525 ms
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
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.