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.
Cached: 2026.10.16 22:11:07/ 1 day 17 hours ago Confirmed: 2026.10.16 22:16:53/ 1 day 17 hours ago
ntp-msn-com-world-atm-default.trafficmanager.net is an alias for ntp.msn.com-ion.edgesuite.net.
ntp.msn.com-ion.edgesuite.net is an alias for a434.dscr.akamai.net.
a434.dscr.akamai.net has address 2.16.168.201a434.dscr.akamai.net has address 2.16.168.217a434.dscr.akamai.net has IPv6 address 2a02:26f0:b700:8::210:ce4ba434.dscr.akamai.net has IPv6 address 2a02:26f0:b700:8::210:ce50
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.16 22:12:15/ 1 day 17 hours ago
traceroute to ntp-msn-com-world-atm-default.trafficmanager.net (2.16.168.217), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 4.285 ms 4.547 ms 4.531 ms
2 15019.your-cloud.host (49.12.138.15) 0.830 ms 0.848 ms 0.842 ms
3 * * *
4 * * *
5 core-spine-rdev2.cloud1.nbg1.hetzner.com (213.239.239.122) 1.441 ms core-spine-rdev1.cloud1.nbg1.hetzner.com (213.239.203.102) 1.689 ms core-spine-rdev2.cloud1.nbg1.hetzner.com (213.239.239.122) 1.437 ms
6 core12.nbg1.hetzner.com (213.239.203.105) 1.695 ms core12.nbg1.hetzner.com (213.239.239.141) 0.931 ms 0.917 ms
7 core4.fra.hetzner.com (213.239.245.245) 4.063 ms 3.433 ms 3.406 ms
8 213-133-121-150.clients.your-server.de (213.133.121.150) 3.885 ms 3.853 ms 3.833 ms
9 ae3.r21.fra03.mag.netarch.akamai.com (23.197.78.104) 4.463 ms 4.378 ms 4.189 ms
10 ae0.r23.fra02.ien.netarch.akamai.com (23.197.78.93) 4.019 ms 3.994 ms ae2.r24.fra03.ien.netarch.akamai.com (23.197.79.111) 3.981 ms
11 ae2.r01.border01.fra04.fab.netarch.akamai.com (23.210.52.101) 4.255 ms ae4.r02.border01.fra04.fab.netarch.akamai.com (23.210.52.99) 5.213 ms ae3.r04.border01.fra04.fab.netarch.akamai.com (23.210.54.81) 4.550 ms
12 lo1.r03.stem01.fra04.fab.netarch.akamai.com (2.16.78.22) 4.528 ms 4.535 ms lo1.r02.stem01.fra04.fab.netarch.akamai.com (2.16.78.21) 4.450 ms
13 lo1.r02.spine03.fra04.fab.netarch.akamai.com (2.16.78.13) 4.255 ms lo1.r02.spine01.fra04.fab.netarch.akamai.com (2.16.78.5) 4.569 ms lo1.r03.spine03.fra04.fab.netarch.akamai.com (2.16.78.14) 4.232 ms
14 lo1.r01.leaf01.fra04.fab.netarch.akamai.com (2.16.78.24) 4.214 ms lo1.r03.leaf01.fra04.fab.netarch.akamai.com (2.16.78.26) 4.102 ms lo1.r02.leaf01.fra04.fab.netarch.akamai.com (2.16.78.25) 4.133 ms
15 vlan100.r13.tor01.fra04.fab.netarch.akamai.com (2.16.168.193) 4.563 ms 4.439 ms 4.454 ms
16 a2-16-168-217.deploy.static.akamaitechnologies.com (2.16.168.217) 4.411 ms 4.018 ms 4.035 ms
No results found, please run it to get the result.
Cached: 2026.10.16 22:12:15/ 1 day 17 hours ago
traceroute to ntp-msn-com-world-atm-default.trafficmanager.net (2.16.168.217), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 4.285 ms 4.547 ms 4.531 ms
2 15019.your-cloud.host (49.12.138.15) 0.830 ms 0.848 ms 0.842 ms
3 * * *
4 * * *
5 core-spine-rdev2.cloud1.nbg1.hetzner.com (213.239.239.122) 1.441 ms core-spine-rdev1.cloud1.nbg1.hetzner.com (213.239.203.102) 1.689 ms core-spine-rdev2.cloud1.nbg1.hetzner.com (213.239.239.122) 1.437 ms
6 core12.nbg1.hetzner.com (213.239.203.105) 1.695 ms core12.nbg1.hetzner.com (213.239.239.141) 0.931 ms 0.917 ms
7 core4.fra.hetzner.com (213.239.245.245) 4.063 ms 3.433 ms 3.406 ms
8 213-133-121-150.clients.your-server.de (213.133.121.150) 3.885 ms 3.853 ms 3.833 ms
9 ae3.r21.fra03.mag.netarch.akamai.com (23.197.78.104) 4.463 ms 4.378 ms 4.189 ms
10 ae0.r23.fra02.ien.netarch.akamai.com (23.197.78.93) 4.019 ms 3.994 ms ae2.r24.fra03.ien.netarch.akamai.com (23.197.79.111) 3.981 ms
11 ae2.r01.border01.fra04.fab.netarch.akamai.com (23.210.52.101) 4.255 ms ae4.r02.border01.fra04.fab.netarch.akamai.com (23.210.52.99) 5.213 ms ae3.r04.border01.fra04.fab.netarch.akamai.com (23.210.54.81) 4.550 ms
12 lo1.r03.stem01.fra04.fab.netarch.akamai.com (2.16.78.22) 4.528 ms 4.535 ms lo1.r02.stem01.fra04.fab.netarch.akamai.com (2.16.78.21) 4.450 ms
13 lo1.r02.spine03.fra04.fab.netarch.akamai.com (2.16.78.13) 4.255 ms lo1.r02.spine01.fra04.fab.netarch.akamai.com (2.16.78.5) 4.569 ms lo1.r03.spine03.fra04.fab.netarch.akamai.com (2.16.78.14) 4.232 ms
14 lo1.r01.leaf01.fra04.fab.netarch.akamai.com (2.16.78.24) 4.214 ms lo1.r03.leaf01.fra04.fab.netarch.akamai.com (2.16.78.26) 4.102 ms lo1.r02.leaf01.fra04.fab.netarch.akamai.com (2.16.78.25) 4.133 ms
15 vlan100.r13.tor01.fra04.fab.netarch.akamai.com (2.16.168.193) 4.563 ms 4.439 ms 4.454 ms
16 a2-16-168-217.deploy.static.akamaitechnologies.com (2.16.168.217) 4.411 ms 4.018 ms 4.035 ms