traceroute to jitsi.jca.apc.org (153.127.25.159), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 4.190 ms 4.137 ms 4.161 ms
2 14879.your-cloud.host (49.12.137.207) 0.763 ms 0.788 ms 0.893 ms
3 * * *
4 spine3.cloud1.nbg1.hetzner.com (88.198.252.217) 1.779 ms 1.990 ms 2.028 ms
5 * * *
6 core11.nbg1.hetzner.com (213.239.203.101) 1.828 ms 5.381 ms 5.342 ms
7 juniper5.dc2.nbg1.hetzner.com (213.239.229.166) 6.876 ms juniper4.dc2.nbg1.hetzner.com (213.239.245.26) 0.469 ms juniper5.dc2.nbg1.hetzner.com (213.239.229.162) 0.647 ms
8 nug-b1-link.ip.twelve99.net (62.115.183.232) 0.875 ms nug-b2-link.ip.twelve99.net (62.115.50.222) 3.350 ms 3.155 ms
9 ffm-bb1-link.ip.twelve99.net (62.115.113.146) 3.894 ms 3.745 ms 3.898 ms
10 prs-bb1-link.ip.twelve99.net (62.115.123.13) 12.742 ms 12.246 ms 12.133 ms
11 prs-bb1-link.ip.twelve99.net (62.115.125.118) 14.440 ms prs-bb1-link.ip.twelve99.net (62.115.118.58) 14.679 ms ldn-bb1-link.ip.twelve99.net (62.115.135.24) 23.754 ms
12 ldn-bb1-link.ip.twelve99.net (62.115.135.24) 26.251 ms ldn-b1-link.ip.twelve99.net (62.115.121.27) 19.311 ms 19.412 ms
13 iijamerica-ic-378944.ip.twelve99-cust.net (62.115.183.154) 18.616 ms 18.400 ms ldn-b1-link.ip.twelve99.net (62.115.121.27) 21.250 ms
14 sea001bb00.IIJ.Net (58.138.83.170) 169.723 ms sjc002bb00.IIJ.Net (58.138.83.178) 169.533 ms iijamerica-ic-378944.ip.twelve99-cust.net (62.115.183.154) 21.102 ms
15 tky001bb00.IIJ.Net (58.138.88.129) 247.854 ms tky001bb01.IIJ.Net (58.138.88.133) 237.583 ms sea001bb00.IIJ.Net (58.138.83.170) 171.895 ms
16 tky001ip57.IIJ.Net (58.138.102.110) 236.791 ms tky001ip57.IIJ.Net (58.138.100.18) 247.714 ms tky001bb00.IIJ.Net (58.138.88.81) 251.161 ms
17 tky001ip57.IIJ.Net (58.138.102.102) 250.359 ms tky001ip57.IIJ.Net (58.138.100.18) 250.156 ms tky001ip57.IIJ.Net (58.138.102.110) 251.300 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
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.
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.09.03 03:13:21/ 7 months 26 days ago Confirmed: 2023.09.03 03:15:56/ 7 months 26 days ago History: 2 records (hide history)
traceroute to jitsi.jca.apc.org (153.127.25.159), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 2.731 ms 2.708 ms 2.710 ms
2 14879.your-cloud.host (49.12.137.207) 0.405 ms 0.406 ms 0.464 ms
3 * * *
4 spine3.cloud1.nbg1.hetzner.com (88.198.252.217) 1.230 ms spine4.cloud1.nbg1.hetzner.com (88.198.252.221) 1.307 ms 1.302 ms
5 * * *
6 core11.nbg1.hetzner.com (213.239.239.121) 1.094 ms 0.582 ms 19.070 ms
7 juniper4.dc2.nbg1.hetzner.com (213.239.203.138) 0.504 ms juniper5.dc2.nbg1.hetzner.com (213.239.229.162) 0.837 ms juniper4.dc2.nbg1.hetzner.com (213.239.245.26) 0.630 ms
8 nug-b1-link.ip.twelve99.net (62.115.183.232) 0.800 ms nug-b2-link.ip.twelve99.net (62.115.50.222) 3.448 ms 3.463 ms
9 ffm-bb1-link.ip.twelve99.net (62.115.113.146) 3.973 ms 4.123 ms 3.655 ms
10 * prs-b3-link.ip.twelve99.net (62.115.118.63) 21.808 ms prs-bb1-link.ip.twelve99.net (62.115.123.13) 11.947 ms
11 ldn-bb1-link.ip.twelve99.net (62.115.135.24) 23.142 ms 23.142 ms 23.333 ms
12 ldn-bb1-link.ip.twelve99.net (62.115.135.24) 25.743 ms ldn-b1-link.ip.twelve99.net (62.115.121.27) 18.767 ms 19.221 ms
13 iijamerica-ic-378944.ip.twelve99-cust.net (62.115.183.154) 18.271 ms ldn-b1-link.ip.twelve99.net (62.115.121.27) 21.236 ms 21.081 ms
14 sjc002bb00.IIJ.Net (58.138.83.178) 169.816 ms 169.943 ms 169.534 ms
15 tky001bb00.IIJ.Net (58.138.88.81) 247.908 ms sea001bb00.IIJ.Net (58.138.83.170) 171.845 ms sjc002bb00.IIJ.Net (58.138.83.178) 172.184 ms
16 tky001bb01.IIJ.Net (58.138.88.85) 253.640 ms tky001ip57.IIJ.Net (58.138.100.22) 248.783 ms tky001ip57.IIJ.Net (58.138.100.18) 247.672 ms
17 210.138.107.34 (210.138.107.34) 237.111 ms 248.659 ms 248.780 ms
18 * * 210.138.107.34 (210.138.107.34) 250.514 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *