Find saved network results that mention a domain name or IP address.
Host
IP or domain (required)
Related arguments and description
Find hosts that appear alongside an IP address or domain in cached command results.
Host
IP or domain (required)
Subdomains arguments and description
Find known subdomains in cached command results. This searches the cache and does not perform a live scan.
Host
Domain (required)
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
IP or domain (required)
NS server
DNS server IP or domain (optional)
Type
Port
-port=number (server port, default 53)
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
IP or domain (required)
Protocol
Packet size
-s number (default 56)
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
IP or domain (required)
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
IP or domain (required)
NS server
DNS server IP or domain (optional)
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
IP or domain (required)
Fragmentation
ICMP
TCP
Map IP
Protocol
Port
--udp=number (UDP 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
IP address (required)
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
IP or domain (required)
NS server
@server (optional)
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
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: 2026.10.26 23:51:54/ 4 days 21 hours ago
** server can't find 8.1.6.8.2.4.f.a.0.0.0.0.0.0.0.0.8.1.6.5.9.0.8.3.1.4.e.4.4.0.a.2.ip6.arpa: NXDOMAIN
No results found, please run it to get the result.
Cached: 2026.10.26 23:53:19/ 4 days 21 hours ago
traceroute to 2a04:4e41:3809:5618::af42:8618 (2a04:4e41:3809:5618::af42:8618), 30 hops max, 80 byte packets
1 gateway (fe80::1%eth0) 3.989 ms 4.148 ms 4.130 ms
2 15019.your-cloud.host (2a01:4f8:0:e0c0::340f) 1.422 ms 1.443 ms 1.482 ms
3 * * *
4 spine3-rdev1.cloud1.nbg1.hetzner.com (2a01:4f8:cfff:1::f000:271) 2.695 ms spine3-rdev2.cloud1.nbg1.hetzner.com (2a01:4f8:cfff:1::f000:275) 22.318 ms spine3-rdev1.cloud1.nbg1.hetzner.com (2a01:4f8:cfff:1::f000:271) 2.689 ms
5 core-spine-rdev1.cloud1.nbg1.hetzner.com (2a01:4f8:cfff:1::f000:f021) 1.959 ms 1.973 ms 1.966 ms
6 core11.nbg1.hetzner.com (2a01:4f8:0:3::2a1) 2.091 ms core12.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1e5) 0.752 ms core12.nbg1.hetzner.com (2a01:4f8:0:3::2e1) 0.727 ms
7 juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22e) 0.710 ms 5.062 ms juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22a) 0.623 ms
8 nug-b2-link.ip.twelve99.net (2001:2035:0:146f::1) 0.575 ms nug-b2-link.ip.twelve99.net (2001:2035:0:1e9f::1) 0.632 ms nug-b2-link.ip.twelve99.net (2001:2035:0:146f::1) 0.447 ms
9 hbg-bb2-link.ip.twelve99.net (2001:2034:a:8c::) 28.813 ms 28.874 ms 28.508 ms
10 * * *
11 ldn-b3-link.ip.twelve99.net (2001:2034:a:3c::1) 106.161 ms ldn-b2-link.ip.twelve99.net (2001:2034:a:3ab::1) 106.433 ms ldn-b3-link.ip.twelve99.net (2001:2034:a:3c::1) 105.856 ms
12 ldn-b3-link.ip.twelve99.net (2001:2034:a:3c::1) 106.110 ms ldn-bb1-link.ip.twelve99.net (2001:2034:a:b9::) 28.027 ms 28.034 ms
13 * * *
14 * * *
15 chi-b23-link.ip.twelve99.net (2001:2034:a:37a::1) 107.212 ms 113.337 ms 105.703 ms
16 * * *
17 2a04:4e40:a000:0:db6:d35e:cb55:f5b3 (2a04:4e40:a000:0:db6:d35e:cb55:f5b3) 112.998 ms 113.004 ms 112.672 ms
No results found, please run it to get the result.
traceroute to 2a04:4e41:3809:5618::af42:8618 (2a04:4e41:3809:5618::af42:8618), 30 hops max, 80 byte packets
1 gateway (fe80::1%eth0) 3.989 ms 4.148 ms 4.130 ms
2 15019.your-cloud.host (2a01:4f8:0:e0c0::340f) 1.422 ms 1.443 ms 1.482 ms
3 * * *
4 spine3-rdev1.cloud1.nbg1.hetzner.com (2a01:4f8:cfff:1::f000:271) 2.695 ms spine3-rdev2.cloud1.nbg1.hetzner.com (2a01:4f8:cfff:1::f000:275) 22.318 ms spine3-rdev1.cloud1.nbg1.hetzner.com (2a01:4f8:cfff:1::f000:271) 2.689 ms
5 core-spine-rdev1.cloud1.nbg1.hetzner.com (2a01:4f8:cfff:1::f000:f021) 1.959 ms 1.973 ms 1.966 ms
6 core11.nbg1.hetzner.com (2a01:4f8:0:3::2a1) 2.091 ms core12.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1e5) 0.752 ms core12.nbg1.hetzner.com (2a01:4f8:0:3::2e1) 0.727 ms
7 juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22e) 0.710 ms 5.062 ms juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22a) 0.623 ms
8 nug-b2-link.ip.twelve99.net (2001:2035:0:146f::1) 0.575 ms nug-b2-link.ip.twelve99.net (2001:2035:0:1e9f::1) 0.632 ms nug-b2-link.ip.twelve99.net (2001:2035:0:146f::1) 0.447 ms
9 hbg-bb2-link.ip.twelve99.net (2001:2034:a:8c::) 28.813 ms 28.874 ms 28.508 ms
10 * * *
11 ldn-b3-link.ip.twelve99.net (2001:2034:a:3c::1) 106.161 ms ldn-b2-link.ip.twelve99.net (2001:2034:a:3ab::1) 106.433 ms ldn-b3-link.ip.twelve99.net (2001:2034:a:3c::1) 105.856 ms
12 ldn-b3-link.ip.twelve99.net (2001:2034:a:3c::1) 106.110 ms ldn-bb1-link.ip.twelve99.net (2001:2034:a:b9::) 28.027 ms 28.034 ms
13 * * *
14 * * *
15 chi-b23-link.ip.twelve99.net (2001:2034:a:37a::1) 107.212 ms 113.337 ms 105.703 ms
16 * * *
17 2a04:4e40:a000:0:db6:d35e:cb55:f5b3 (2a04:4e40:a000:0:db6:d35e:cb55:f5b3) 112.998 ms 113.004 ms 112.672 ms