traceroute to 99.84.66.42 (99.84.66.42), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 3.871 ms 3.852 ms 3.859 ms
2 18533.your-cloud.host (168.119.217.103) 1.576 ms 1.590 ms 1.637 ms
3 * * *
4 spine6.cloud1.nbg1.hetzner.com (78.46.29.189) 2.669 ms spine5.cloud1.nbg1.hetzner.com (78.46.29.185) 3.362 ms spine6.cloud1.nbg1.hetzner.com (78.46.29.189) 2.684 ms
5 * * *
6 core12.nbg1.hetzner.com (213.239.239.141) 2.203 ms 0.476 ms core11.nbg1.hetzner.com (213.239.239.121) 0.475 ms
7 juniper4.dc2.nbg1.hetzner.com (213.239.245.26) 0.524 ms juniper5.dc2.nbg1.hetzner.com (213.239.229.166) 0.648 ms juniper5.dc2.nbg1.hetzner.com (213.239.229.162) 0.500 ms
8 nug-b2-link.ip.twelve99.net (62.115.50.222) 3.292 ms nug-b1-link.ip.twelve99.net (213.248.70.0) 0.683 ms 0.572 ms
9 ffm-bb1-link.ip.twelve99.net (62.115.140.202) 3.717 ms * *
10 prs-bb1-link.ip.twelve99.net (62.115.123.13) 12.011 ms * ldn-bb2-link.ip.twelve99.net (62.115.122.161) 28.318 ms
11 * ldn-bb1-link.ip.twelve99.net (62.115.135.24) 24.976 ms nyk-bb1-link.ip.twelve99.net (62.115.112.244) 97.540 ms
12 nyk-bb2-link.ip.twelve99.net (62.115.113.20) 96.134 ms palo-b24-link.ip.twelve99.net (62.115.118.121) 165.283 ms palo-b24-link.ip.twelve99.net (62.115.138.117) 165.638 ms
13 palo-b24-link.ip.twelve99.net (62.115.138.111) 163.248 ms palo-b24-link.ip.twelve99.net (62.115.122.36) 163.239 ms palo-b24-link.ip.twelve99.net (62.115.138.111) 162.942 ms
14 amazon-ic-375415.ip.twelve99-cust.net (62.115.161.41) 180.015 ms 178.660 ms 179.467 ms
15 amazon-ic-375415.ip.twelve99-cust.net (62.115.161.41) 177.625 ms * 176.612 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * server-99-84-66-42.hio50.r.cloudfront.net (99.84.66.42) 179.015 ms 185.260 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: 2024.06.07 00:17:35/ 3 months 11 days ago Confirmed: 2024.07.29 08:53:22/ 1 month 18 days ago History: 2 records (hide history)
traceroute to 99.84.66.42 (99.84.66.42), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 4.025 ms 4.014 ms 4.005 ms
2 15779.your-cloud.host (49.12.139.42) 0.774 ms 0.778 ms 0.773 ms
3 * * *
4 spine4.cloud1.nbg1.hetzner.com (88.198.252.205) 1.434 ms 1.983 ms spine3.cloud1.nbg1.hetzner.com (88.198.252.201) 1.510 ms
5 * * *
6 core12.nbg1.hetzner.com (213.239.239.141) 1.222 ms 0.655 ms core11.nbg1.hetzner.com (213.239.239.121) 0.519 ms
7 juniper6.dc2.nbg1.hetzner.com (213.239.245.74) 0.734 ms juniper6.dc2.nbg1.hetzner.com (213.239.245.78) 0.493 ms 0.850 ms
8 nug-b1-link.ip.twelve99.net (213.248.70.0) 1.057 ms nug-b1-link.ip.twelve99.net (62.115.183.232) 1.168 ms nug-b1-link.ip.twelve99.net (213.248.70.0) 1.291 ms
9 prs-bb2-link.ip.twelve99.net (62.115.112.214) 14.598 ms ffm-bb1-link.ip.twelve99.net (62.115.113.146) 4.206 ms 4.302 ms
10 prs-b6-link.ip.twelve99.net (62.115.125.117) 190.179 ms 189.806 ms prs-b3-link.ip.twelve99.net (62.115.118.63) 178.353 ms
11 ldn-bb1-link.ip.twelve99.net (62.115.135.24) 24.003 ms 23.994 ms 24.374 ms
12 hbg-bb3-link.ip.twelve99.net (62.115.123.77) 204.718 ms prs-bb1-link.ip.twelve99.net (62.115.135.25) 187.406 ms hbg-bb3-link.ip.twelve99.net (62.115.123.77) 204.641 ms
13 hbg-bb3-link.ip.twelve99.net (62.115.123.77) 207.597 ms nyk-bb2-link.ip.twelve99.net (62.115.113.20) 103.760 ms hbg-bb3-link.ip.twelve99.net (62.115.123.77) 206.979 ms
14 port-b3-link.ip.twelve99.net (62.115.115.25) 175.561 ms nyk-bb2-link.ip.twelve99.net (62.115.113.20) 111.841 ms port-b3-link.ip.twelve99.net (62.115.115.25) 176.384 ms
15 ash-bb2-link.ip.twelve99.net (62.115.112.242) 200.650 ms nyk-bb2-link.ip.twelve99.net (62.115.113.20) 117.291 ms amazon-ic-375415.ip.twelve99-cust.net (62.115.161.41) 185.009 ms
16 rest-bb1-link.ip.twelve99.net (62.115.122.159) 194.697 ms ldn-bb2-link.ip.twelve99.net (62.115.120.238) 196.006 ms nyk-bb1-link.ip.twelve99.net (62.115.141.245) 183.308 ms
17 nyk-b1-link.ip.twelve99.net (62.115.135.131) 184.314 ms * *
18 amazon-ic-375415.ip.twelve99-cust.net (62.115.161.41) 200.560 ms * *
19 port-b3-link.ip.twelve99.net (62.115.115.25) 200.355 ms palo-b24-link.ip.twelve99.net (62.115.138.111) 170.049 ms *
20 * * *
21 * port-b3-link.ip.twelve99.net (62.115.115.25) 185.817 ms *
22 * * *
23 server-99-84-66-42.hio50.r.cloudfront.net (99.84.66.42) 176.580 ms 175.921 ms *