traceroute to 52.217.16.150 (52.217.16.150), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 7.278 ms 7.353 ms 7.355 ms
2 16781.your-cloud.host (49.12.139.252) 0.697 ms 0.708 ms 0.882 ms
3 * * *
4 static.88.198.133.237.clients.your-server.de (88.198.133.237) 1.429 ms 1.726 ms 1.677 ms
5 spine14.cloud1.nbg1.hetzner.com (213.133.112.109) 2.510 ms spine14.cloud1.nbg1.hetzner.com (213.133.113.69) 2.522 ms spine12.cloud1.nbg1.hetzner.com (78.47.3.45) 1.563 ms
6 213-239-239-121.clients.your-server.de (213.239.239.121) 1.163 ms static.213-133-112-69.clients.your-server.de (213.133.112.69) 0.836 ms 213-239-239-121.clients.your-server.de (213.239.239.121) 0.448 ms
7 juniper5.dc2.nbg1.hetzner.com (213.239.229.166) 2.105 ms juniper4.dc2.nbg1.hetzner.com (213.239.203.138) 0.585 ms 0.592 ms
8 nug-b1-link.ip.twelve99.net (62.115.183.232) 1.191 ms nug-b1-link.ip.twelve99.net (213.248.70.0) 1.073 ms nug-b2-link.ip.twelve99.net (62.115.50.222) 3.519 ms
9 prs-bb2-link.ip.twelve99.net (62.115.112.214) 15.154 ms ffm-bb1-link.ip.twelve99.net (62.115.113.146) 3.647 ms 3.510 ms
10 rest-bb1-link.ip.twelve99.net (62.115.122.159) 96.820 ms prs-bb1-link.ip.twelve99.net (62.115.123.13) 12.794 ms rest-bb1-link.ip.twelve99.net (62.115.122.159) 96.262 ms
11 ash-b2-link.ip.twelve99.net (62.115.123.123) 96.617 ms ash-bb2-link.ip.twelve99.net (62.115.112.242) 94.810 ms 99.683 ms
12 vadata-svc077201-lag003749.ip.twelve99-cust.net (62.115.63.81) 96.323 ms ash-b2-link.ip.twelve99.net (62.115.123.125) 97.338 ms 97.442 ms
13 vadata-ic333118-ash-b2.ip.twelve99-cust.net (62.115.11.183) 97.386 ms vadata-ic333120-ash-b2.ip.twelve99-cust.net (62.115.11.249) 98.398 ms vadata-ic333119-ash-b2.ip.twelve99-cust.net (213.248.92.171) 98.439 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 s3-1.amazonaws.com (52.217.16.150) 96.298 ms 96.326 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 04:03:50/ 1 year 9 months ago Confirmed: 2022.07.13 04:05:20/ 1 year 9 months ago History: 2 records (hide history)
traceroute to 52.217.16.150 (52.217.16.150), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 8.532 ms 8.580 ms 8.589 ms
2 16781.your-cloud.host (49.12.139.252) 0.584 ms 0.648 ms 0.818 ms
3 * * *
4 static.88.198.133.233.clients.your-server.de (88.198.133.233) 1.526 ms 1.925 ms 1.906 ms
5 spine13.cloud1.nbg1.hetzner.com (213.133.112.105) 1.941 ms 2.199 ms static.213-133-108-149.clients.your-server.de (213.133.108.149) 1.729 ms
6 static.213-133-112-81.clients.your-server.de (213.133.112.81) 3.277 ms static.213-133-112-85.clients.your-server.de (213.133.112.85) 2.796 ms 213-239-239-141.clients.your-server.de (213.239.239.141) 2.740 ms
7 juniper4.dc2.nbg1.hetzner.com (213.239.203.138) 0.456 ms 0.358 ms 0.353 ms
8 nug-b2-link.ip.twelve99.net (62.115.50.222) 3.707 ms nug-b1-link.ip.twelve99.net (213.248.70.0) 0.770 ms nug-b1-link.ip.twelve99.net (62.115.183.232) 0.653 ms
9 ffm-bb1-link.ip.twelve99.net (62.115.113.146) 4.034 ms prs-bb2-link.ip.twelve99.net (62.115.112.214) 14.988 ms ffm-bb1-link.ip.twelve99.net (62.115.113.146) 3.741 ms
10 rest-bb1-link.ip.twelve99.net (62.115.122.159) 96.941 ms * prs-bb1-link.ip.twelve99.net (62.115.123.13) 12.960 ms
11 ash-bb2-link.ip.twelve99.net (62.115.112.242) 94.901 ms 97.605 ms ash-b2-link.ip.twelve99.net (62.115.123.123) 96.822 ms
12 ash-b2-link.ip.twelve99.net (62.115.123.125) 98.611 ms 98.549 ms 98.422 ms
13 vadata-ic333118-ash-b2.ip.twelve99-cust.net (62.115.11.183) 104.039 ms vadata-svc077202-lag003838.ip.twelve99-cust.net (62.115.63.85) 99.368 ms vadata-svc077201-lag003749.ip.twelve99-cust.net (62.115.63.81) 99.314 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 s3-1.amazonaws.com (52.217.16.150) 99.244 ms 99.424 ms 96.409 ms