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: 2022.10.25 08:17:02/ 3 years 11 months ago
** server can't find d.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.f.0.8.0.2.0.0.0.7.8.3.0.0.0.6.2.ip6.arpa: NXDOMAIN
No results found, please run it to get the result.
Cached: 2022.10.24 01:48:23/ 4 years ago
traceroute to 2600:387:2:80f::3d (2600:387:2:80f::3d), 30 hops max, 80 byte packets
1 fe80::%eth0 (fe80::%eth0) 9.319 ms 8.790 ms 9.322 ms
2 13700.your-cloud.host (2a01:4f8:0:e0c0::2e44) 0.475 ms 0.498 ms 0.474 ms
3 * * *
4 2a01:4f8:0:e0c0::a0f9 (2a01:4f8:0:e0c0::a0f9) 1.410 ms 2a01:4f8:0:e0c0::a0fd (2a01:4f8:0:e0c0::a0fd) 1.391 ms 1.782 ms
5 spine11.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1ed) 1.321 ms spine14.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a27d) 1.668 ms spine14.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a275) 1.417 ms
6 core11.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1e1) 11.282 ms 10.852 ms core12.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1e5) 0.517 ms
7 juniper4.dc2.nbg1.hetzner.com (2a01:4f8:0:3::10a) 0.482 ms juniper4.dc2.nbg1.hetzner.com (2a01:4f8:0:3::26) 3.300 ms juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22a) 0.476 ms
8 nug-b1-link.ip.twelve99.net (2001:2000:3080:1e9f::1) 0.804 ms nug-b2-link.ip.twelve99.net (2001:2035:0:2540::1) 0.458 ms nug-b1-link.ip.twelve99.net (2001:2000:3080:146f::1) 0.759 ms
9 prs-bb2-v6.ip.twelve99.net (2001:2034:1:c1::1) 16.074 ms 15.955 ms ffm-bb1-v6.ip.twelve99.net (2001:2034:1:6b::1) 3.455 ms
10 rest-bb1-v6.ip.twelve99.net (2001:2034:1:73::1) 93.080 ms prs-bb1-v6.ip.twelve99.net (2001:2034:1:be::1) 14.074 ms 13.876 ms
11 ash-bb2-v6.ip.twelve99.net (2001:2034:1:74::1) 99.874 ms 100.142 ms 99.778 ms
12 wshdc82crs.ipv6.att.net (2001:1890:ff:ffff:12:122:135:102) 113.175 ms * 118.281 ms
13 wshdc82crs.ipv6.att.net (2001:1890:ff:ffff:12:122:135:102) 118.275 ms 2001:1890:ff:ffff:12:122:135:250 (2001:1890:ff:ffff:12:122:135:250) 116.239 ms 117.627 ms
14 attga21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:2:29) 116.973 ms 2001:1890:ff:ffff:12:122:135:250 (2001:1890:ff:ffff:12:122:135:250) 116.306 ms 119.179 ms
15 attga21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:2:29) 117.498 ms 118.305 ms 120.184 ms
16 2001:1890:ff:ffff:12:83:170:17 (2001:1890:ff:ffff:12:83:170:17) 122.383 ms 121.445 ms 119.591 ms
17 2600:300:2020:105::1 (2600:300:2020:105::1) 118.906 ms 118.289 ms 2600:300:2020:2920::2 (2600:300:2020:2920::2) 110.918 ms
18 2600:300:2020:2920::2 (2600:300:2020:2920::2) 122.247 ms 113.498 ms 2600:387:2:80f::3d (2600:387:2:80f::3d) 114.218 ms
No results found, please run it to get the result.
Cached: 2022.10.24 01:48:23/ 4 years ago
traceroute to 2600:387:2:80f::3d (2600:387:2:80f::3d), 30 hops max, 80 byte packets
1 fe80::%eth0 (fe80::%eth0) 9.319 ms 8.790 ms 9.322 ms
2 13700.your-cloud.host (2a01:4f8:0:e0c0::2e44) 0.475 ms 0.498 ms 0.474 ms
3 * * *
4 2a01:4f8:0:e0c0::a0f9 (2a01:4f8:0:e0c0::a0f9) 1.410 ms 2a01:4f8:0:e0c0::a0fd (2a01:4f8:0:e0c0::a0fd) 1.391 ms 1.782 ms
5 spine11.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1ed) 1.321 ms spine14.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a27d) 1.668 ms spine14.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a275) 1.417 ms
6 core11.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1e1) 11.282 ms 10.852 ms core12.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1e5) 0.517 ms
7 juniper4.dc2.nbg1.hetzner.com (2a01:4f8:0:3::10a) 0.482 ms juniper4.dc2.nbg1.hetzner.com (2a01:4f8:0:3::26) 3.300 ms juniper5.dc2.nbg1.hetzner.com (2a01:4f8:0:3::22a) 0.476 ms
8 nug-b1-link.ip.twelve99.net (2001:2000:3080:1e9f::1) 0.804 ms nug-b2-link.ip.twelve99.net (2001:2035:0:2540::1) 0.458 ms nug-b1-link.ip.twelve99.net (2001:2000:3080:146f::1) 0.759 ms
9 prs-bb2-v6.ip.twelve99.net (2001:2034:1:c1::1) 16.074 ms 15.955 ms ffm-bb1-v6.ip.twelve99.net (2001:2034:1:6b::1) 3.455 ms
10 rest-bb1-v6.ip.twelve99.net (2001:2034:1:73::1) 93.080 ms prs-bb1-v6.ip.twelve99.net (2001:2034:1:be::1) 14.074 ms 13.876 ms
11 ash-bb2-v6.ip.twelve99.net (2001:2034:1:74::1) 99.874 ms 100.142 ms 99.778 ms
12 wshdc82crs.ipv6.att.net (2001:1890:ff:ffff:12:122:135:102) 113.175 ms * 118.281 ms
13 wshdc82crs.ipv6.att.net (2001:1890:ff:ffff:12:122:135:102) 118.275 ms 2001:1890:ff:ffff:12:122:135:250 (2001:1890:ff:ffff:12:122:135:250) 116.239 ms 117.627 ms
14 attga21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:2:29) 116.973 ms 2001:1890:ff:ffff:12:122:135:250 (2001:1890:ff:ffff:12:122:135:250) 116.306 ms 119.179 ms
15 attga21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:2:29) 117.498 ms 118.305 ms 120.184 ms
16 2001:1890:ff:ffff:12:83:170:17 (2001:1890:ff:ffff:12:83:170:17) 122.383 ms 121.445 ms 119.591 ms
17 2600:300:2020:105::1 (2600:300:2020:105::1) 118.906 ms 118.289 ms 2600:300:2020:2920::2 (2600:300:2020:2920::2) 110.918 ms
18 2600:300:2020:2920::2 (2600:300:2020:2920::2) 122.247 ms 113.498 ms 2600:387:2:80f::3d (2600:387:2:80f::3d) 114.218 ms