No results found, please run it to get the result.
No results found, please run it to get the result.
No results found, please run it to get the result.
No results found, please run it to get the result.
No results found, please run it to get the result.
Cached: 2023.05.26 04:23:47/ 11 months 3 days ago
traceroute to 2600:387:f:611b::5 (2600:387:f:611b::5), 30 hops max, 80 byte packets
1 fe80::%eth0 (fe80::%eth0) 4.603 ms 4.582 ms 4.594 ms
2 15045.your-cloud.host (2a01:4f8:0:e0c0::3429) 0.810 ms 0.848 ms 0.931 ms
3 * * *
4 2a01:4f8:0:e0c0::a129 (2a01:4f8:0:e0c0::a129) 8.424 ms 2a01:4f8:0:e0c0::a12d (2a01:4f8:0:e0c0::a12d) 1.812 ms 2a01:4f8:0:e0c0::a129 (2a01:4f8:0:e0c0::a129) 8.421 ms
5 * * *
6 core12.nbg1.hetzner.com (2a01:4f8:0:3::2a1) 12.535 ms 0.879 ms core31.hel1.hetzner.com (2a01:4f8:0:3::2e1) 0.850 ms
7 2a01:4f8:0:3::3a (2a01:4f8:0:3::3a) 0.932 ms juniper3.rz2.hetzner.de (2a01:4f8:0:3::3e) 0.443 ms juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22e) 0.346 ms
8 * ae79.edge8.Frankfurt1.Level3.net (2001:1900:5:2:2::6955) 4.253 ms *
9 * ffm-bb1-v6.ip.twelve99.net (2001:2034:1:6b::1) 3.647 ms 3.967 ms
10 att-level3-10G.edge1.Washington12.Level3.net (2001:1900:4:3::19e) 103.778 ms 105.937 ms prs-bb1-v6.ip.twelve99.net (2001:2034:1:be::1) 14.401 ms
11 ash-bb2-v6.ip.twelve99.net (2001:2034:1:74::1) 101.509 ms 102.468 ms 102.421 ms
12 * cgcil21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:205) 163.620 ms *
13 wshdc82crs.ipv6.att.net (2001:1890:ff:ffff:12:122:135:102) 169.247 ms dvmco22crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:77) 166.087 ms wshdc82crs.ipv6.att.net (2001:1890:ff:ffff:12:122:135:102) 167.974 ms
14 slkut21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:46) 158.763 ms * 163.586 ms
15 slkut22crs.ipv6.att.net (2001:1890:ff:ffff:12:122:30:22) 158.512 ms cgcil21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:205) 170.132 ms 170.069 ms
16 dvmco22crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:77) 166.966 ms 165.811 ms 164.114 ms
17 * slkut21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:46) 171.073 ms 169.894 ms
18 2600:387:f:611b::5 (2600:387:f:611b::5) 165.644 ms 181.081 ms slkut22crs.ipv6.att.net (2001:1890:ff:ffff:12:122:30:22) 165.508 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.05.26 04:23:47/ 11 months 3 days ago
traceroute to 2600:387:f:611b::5 (2600:387:f:611b::5), 30 hops max, 80 byte packets
1 fe80::%eth0 (fe80::%eth0) 4.603 ms 4.582 ms 4.594 ms
2 15045.your-cloud.host (2a01:4f8:0:e0c0::3429) 0.810 ms 0.848 ms 0.931 ms
3 * * *
4 2a01:4f8:0:e0c0::a129 (2a01:4f8:0:e0c0::a129) 8.424 ms 2a01:4f8:0:e0c0::a12d (2a01:4f8:0:e0c0::a12d) 1.812 ms 2a01:4f8:0:e0c0::a129 (2a01:4f8:0:e0c0::a129) 8.421 ms
5 * * *
6 core12.nbg1.hetzner.com (2a01:4f8:0:3::2a1) 12.535 ms 0.879 ms core31.hel1.hetzner.com (2a01:4f8:0:3::2e1) 0.850 ms
7 2a01:4f8:0:3::3a (2a01:4f8:0:3::3a) 0.932 ms juniper3.rz2.hetzner.de (2a01:4f8:0:3::3e) 0.443 ms juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22e) 0.346 ms
8 * ae79.edge8.Frankfurt1.Level3.net (2001:1900:5:2:2::6955) 4.253 ms *
9 * ffm-bb1-v6.ip.twelve99.net (2001:2034:1:6b::1) 3.647 ms 3.967 ms
10 att-level3-10G.edge1.Washington12.Level3.net (2001:1900:4:3::19e) 103.778 ms 105.937 ms prs-bb1-v6.ip.twelve99.net (2001:2034:1:be::1) 14.401 ms
11 ash-bb2-v6.ip.twelve99.net (2001:2034:1:74::1) 101.509 ms 102.468 ms 102.421 ms
12 * cgcil21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:205) 163.620 ms *
13 wshdc82crs.ipv6.att.net (2001:1890:ff:ffff:12:122:135:102) 169.247 ms dvmco22crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:77) 166.087 ms wshdc82crs.ipv6.att.net (2001:1890:ff:ffff:12:122:135:102) 167.974 ms
14 slkut21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:46) 158.763 ms * 163.586 ms
15 slkut22crs.ipv6.att.net (2001:1890:ff:ffff:12:122:30:22) 158.512 ms cgcil21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:205) 170.132 ms 170.069 ms
16 dvmco22crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:77) 166.966 ms 165.811 ms 164.114 ms
17 * slkut21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:28:46) 171.073 ms 169.894 ms
18 2600:387:f:611b::5 (2600:387:f:611b::5) 165.644 ms 181.081 ms slkut22crs.ipv6.att.net (2001:1890:ff:ffff:12:122:30:22) 165.508 ms