traceroute to 13.225.169.27 (13.225.169.27), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 4.391 ms 4.349 ms 4.340 ms
2 15045.your-cloud.host (49.12.138.41) 0.669 ms 0.842 ms 0.861 ms
3 * * *
4 spine4.cloud1.nbg1.hetzner.com (88.198.247.133) 1.717 ms spine3.cloud1.nbg1.hetzner.com (88.198.247.129) 1.697 ms 1.697 ms
5 * * *
6 core11.nbg1.hetzner.com (213.239.239.121) 1.371 ms core11.nbg1.hetzner.com (213.239.203.101) 1.061 ms core11.nbg1.hetzner.com (213.239.239.121) 0.888 ms
7 core0.fra.hetzner.com (213.239.252.25) 3.889 ms 6.053 ms 3.390 ms
8 213.198.82.129 (213.198.82.129) 7.256 ms 3.601 ms 3.578 ms
9 ae-4.r20.frnkge13.de.bb.gin.ntt.net (129.250.3.31) 3.687 ms 3.497 ms 3.732 ms
10 ae-0.r21.frnkge13.de.bb.gin.ntt.net (129.250.6.2) 4.597 ms ae-14.r21.londen12.uk.bb.gin.ntt.net (129.250.3.12) 17.111 ms ae-0.r21.frnkge13.de.bb.gin.ntt.net (129.250.6.2) 4.282 ms
11 ae-12.r21.parsfr04.fr.bb.gin.ntt.net (129.250.5.27) 14.222 ms ae-13.r25.asbnva02.us.bb.gin.ntt.net (129.250.2.111) 90.855 ms ae-12.r21.parsfr04.fr.bb.gin.ntt.net (129.250.5.27) 15.047 ms
12 ae-2.r25.lsanca07.us.bb.gin.ntt.net (129.250.3.189) 143.507 ms ae-0.r20.parsfr04.fr.bb.gin.ntt.net (129.250.3.47) 16.725 ms ae-13.r24.asbnva02.us.bb.gin.ntt.net (129.250.6.6) 91.000 ms
13 ae-12.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.3.192) 252.171 ms 248.422 ms 253.658 ms
14 ae-3.r00.tokyjp08.jp.bb.gin.ntt.net (129.250.6.129) 245.822 ms ae-2.r02.tokyjp08.jp.bb.gin.ntt.net (129.250.2.131) 258.414 ms ae-3.r00.tokyjp08.jp.bb.gin.ntt.net (129.250.6.129) 240.464 ms
15 ae-4.r24.sttlwa01.us.bb.gin.ntt.net (129.250.6.177) 143.764 ms ae-21.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.5.77) 247.212 ms ae-0.amazon.tokyjp09.jp.bb.gin.ntt.net (61.120.146.70) 244.780 ms
16 * * *
17 * * ae-0.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.5.22) 250.355 ms
18 ae-0.amazon.tokyjp08.jp.bb.gin.ntt.net (61.120.146.118) 258.558 ms * *
19 * ae-1.amazon.tokyjp09.jp.bb.gin.ntt.net (61.120.146.74) 239.866 ms *
20 * * *
21 * * *
22 * * *
23 server-13-225-169-27.nrt57.r.cloudfront.net (13.225.169.27) 250.388 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: 2023.07.21 06:51:29/ 9 months 8 days ago Confirmed: 2023.07.21 07:19:25/ 9 months 8 days ago History: 4 records (hide history)
traceroute to 13.225.169.27 (13.225.169.27), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 4.281 ms 4.228 ms 4.252 ms
2 15045.your-cloud.host (49.12.138.41) 0.783 ms 0.795 ms 0.835 ms
3 * * *
4 spine4.cloud1.nbg1.hetzner.com (88.198.247.133) 1.743 ms spine3.cloud1.nbg1.hetzner.com (88.198.247.129) 1.685 ms 1.677 ms
5 * * *
6 core12.nbg1.hetzner.com (213.239.239.141) 1.314 ms 0.623 ms core11.nbg1.hetzner.com (213.239.239.121) 4.307 ms
7 core0.fra.hetzner.com (213.239.252.21) 3.686 ms 3.448 ms core0.fra.hetzner.com (213.239.252.25) 11.958 ms
8 213.198.82.129 (213.198.82.129) 3.678 ms 3.856 ms 3.644 ms
9 ae-4.r20.frnkge13.de.bb.gin.ntt.net (129.250.3.31) 4.178 ms 4.151 ms 4.045 ms
10 ae-14.r21.londen12.uk.bb.gin.ntt.net (129.250.3.12) 14.687 ms ae-0.r21.frnkge13.de.bb.gin.ntt.net (129.250.6.2) 5.457 ms 5.457 ms
11 ae-13.r25.asbnva02.us.bb.gin.ntt.net (129.250.2.111) 89.677 ms ae-12.r21.parsfr04.fr.bb.gin.ntt.net (129.250.5.27) 13.405 ms 13.411 ms
12 ae-2.r25.lsanca07.us.bb.gin.ntt.net (129.250.3.189) 145.323 ms ae-13.r24.asbnva02.us.bb.gin.ntt.net (129.250.6.6) 87.718 ms ae-0.r20.parsfr04.fr.bb.gin.ntt.net (129.250.3.47) 14.284 ms
13 ae-14.r21.nwrknj03.us.bb.gin.ntt.net (129.250.4.194) 84.328 ms 84.031 ms 84.102 ms
14 ae-0.r25.snjsca04.us.bb.gin.ntt.net (129.250.3.147) 154.123 ms ae-1.a01.tokyjp09.jp.bb.gin.ntt.net (129.250.7.62) 251.724 ms ae-0.r20.nwrknj03.us.bb.gin.ntt.net (129.250.6.16) 87.531 ms
15 * ae-21.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.5.77) 249.822 ms ae-2.amazon.tokyjp08.jp.bb.gin.ntt.net (61.213.161.50) 255.836 ms
16 ae-13.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.4.143) 244.812 ms ae-0.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.5.22) 252.848 ms ae-13.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.4.143) 239.937 ms
17 ae-0.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.5.22) 243.246 ms * *
18 * * *
19 ae-1.amazon.tokyjp08.jp.bb.gin.ntt.net (61.213.161.46) 247.273 ms ae-2.amazon.tokyjp08.jp.bb.gin.ntt.net (61.213.161.50) 239.869 ms *
20 * * *
21 * * *
22 * * *
23 * * server-13-225-169-27.nrt57.r.cloudfront.net (13.225.169.27) 246.906 ms