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: 2022.11.30 16:11:26/ 1 year 4 months ago
traceroute to 2a03:2880:f01f:6:face:b00c:0:3 (2a03:2880:f01f:6:face:b00c:0:3), 30 hops max, 80 byte packets
1 fe80::%eth0 (fe80::%eth0) 3.870 ms 3.848 ms 3.827 ms
2 19541.your-cloud.host (2a01:4f8:0:e0c0::5549) 0.428 ms 0.408 ms 0.444 ms
3 * * *
4 2a01:4f8:0:e0c0::a211 (2a01:4f8:0:e0c0::a211) 1.419 ms 2a01:4f8:0:e0c0::a215 (2a01:4f8:0:e0c0::a215) 1.120 ms 1.117 ms
5 spine14.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a285) 1.173 ms spine12.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1b5) 1.201 ms spine12.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1ad) 1.252 ms
6 2a01:4f8:0:e0c0::a259 (2a01:4f8:0:e0c0::a259) 2.419 ms 2.034 ms core11.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1f9) 10.568 ms
7 juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22a) 0.526 ms 0.374 ms juniper4.dc2.nbg1.hetzner.com (2a01:4f8:0:3::26) 0.440 ms
8 ae12-498.nbg40.core-backbone.com (2a01:4a0:1338:16c::1) 0.626 ms ae12-499.nbg40.core-backbone.com (2a01:4a0:1338:80::1) 0.407 ms ae12-500.nbg40.core-backbone.com (2a01:4a0:1338:1ae::1) 0.449 ms
9 ae1-2014.nbg60.core-backbone.com (2a01:4a0:0:2014::2) 0.848 ms 0.717 ms 0.710 ms
10 ae5-2015.nbg20.core-backbone.com (2a01:4a0:0:2015::2) 1.067 ms 1.012 ms 0.965 ms
11 ae1-2003.fra20.core-backbone.com (2a01:4a0:0:2003::4) 3.828 ms 3.565 ms 3.591 ms
12 ae2-2025.fra30.core-backbone.com (2a01:4a0:0:2025::31) 4.196 ms 3.934 ms 3.908 ms
13 ae1-2075.par10.core-backbone.com (2a01:4a0:0:2075::20) 13.077 ms 13.088 ms 13.045 ms
14 * * *
15 po101.asw01.cdg1.tfbnw.net (2620:0:1cff:dead:beef::4bc2) 13.057 ms 13.014 ms po101.asw03.cdg1.tfbnw.net (2620:0:1cff:dead:beef::69fe) 12.972 ms
16 po213.psw03.cdg2.tfbnw.net (2620:0:1cff:dead:beef::c83) 13.072 ms po216.psw01.cdg2.tfbnw.net (2620:0:1cff:dead:beef::a11) 13.118 ms po212.psw01.cdg2.tfbnw.net (2620:0:1cff:dead:beef::87d) 13.170 ms
17 po6.msw1aw.01.cdg2.tfbnw.net (2a03:2880:f01f:ffff::131) 13.114 ms po4.msw1au.01.cdg2.tfbnw.net (2a03:2880:f01f:ffff::c5) 13.095 ms po7.msw1ax.01.cdg2.tfbnw.net (2a03:2880:f01f:ffff::167) 13.153 ms
18 xx-fbcdn6-shv-01-cdg2.fbcdn.net (2a03:2880:f01f:6:face:b00c:0:3) 13.146 ms 13.020 ms 12.992 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.11.30 16:11:26/ 1 year 4 months ago
traceroute to 2a03:2880:f01f:6:face:b00c:0:3 (2a03:2880:f01f:6:face:b00c:0:3), 30 hops max, 80 byte packets
1 fe80::%eth0 (fe80::%eth0) 3.870 ms 3.848 ms 3.827 ms
2 19541.your-cloud.host (2a01:4f8:0:e0c0::5549) 0.428 ms 0.408 ms 0.444 ms
3 * * *
4 2a01:4f8:0:e0c0::a211 (2a01:4f8:0:e0c0::a211) 1.419 ms 2a01:4f8:0:e0c0::a215 (2a01:4f8:0:e0c0::a215) 1.120 ms 1.117 ms
5 spine14.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a285) 1.173 ms spine12.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1b5) 1.201 ms spine12.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1ad) 1.252 ms
6 2a01:4f8:0:e0c0::a259 (2a01:4f8:0:e0c0::a259) 2.419 ms 2.034 ms core11.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1f9) 10.568 ms
7 juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22a) 0.526 ms 0.374 ms juniper4.dc2.nbg1.hetzner.com (2a01:4f8:0:3::26) 0.440 ms
8 ae12-498.nbg40.core-backbone.com (2a01:4a0:1338:16c::1) 0.626 ms ae12-499.nbg40.core-backbone.com (2a01:4a0:1338:80::1) 0.407 ms ae12-500.nbg40.core-backbone.com (2a01:4a0:1338:1ae::1) 0.449 ms
9 ae1-2014.nbg60.core-backbone.com (2a01:4a0:0:2014::2) 0.848 ms 0.717 ms 0.710 ms
10 ae5-2015.nbg20.core-backbone.com (2a01:4a0:0:2015::2) 1.067 ms 1.012 ms 0.965 ms
11 ae1-2003.fra20.core-backbone.com (2a01:4a0:0:2003::4) 3.828 ms 3.565 ms 3.591 ms
12 ae2-2025.fra30.core-backbone.com (2a01:4a0:0:2025::31) 4.196 ms 3.934 ms 3.908 ms
13 ae1-2075.par10.core-backbone.com (2a01:4a0:0:2075::20) 13.077 ms 13.088 ms 13.045 ms
14 * * *
15 po101.asw01.cdg1.tfbnw.net (2620:0:1cff:dead:beef::4bc2) 13.057 ms 13.014 ms po101.asw03.cdg1.tfbnw.net (2620:0:1cff:dead:beef::69fe) 12.972 ms
16 po213.psw03.cdg2.tfbnw.net (2620:0:1cff:dead:beef::c83) 13.072 ms po216.psw01.cdg2.tfbnw.net (2620:0:1cff:dead:beef::a11) 13.118 ms po212.psw01.cdg2.tfbnw.net (2620:0:1cff:dead:beef::87d) 13.170 ms
17 po6.msw1aw.01.cdg2.tfbnw.net (2a03:2880:f01f:ffff::131) 13.114 ms po4.msw1au.01.cdg2.tfbnw.net (2a03:2880:f01f:ffff::c5) 13.095 ms po7.msw1ax.01.cdg2.tfbnw.net (2a03:2880:f01f:ffff::167) 13.153 ms
18 xx-fbcdn6-shv-01-cdg2.fbcdn.net (2a03:2880:f01f:6:face:b00c:0:3) 13.146 ms 13.020 ms 12.992 ms