traceroute to sf16-telemetry-proxy-oci.tiktokcdn-us.com (23.221.236.99), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 3.044 ms 3.534 ms 3.692 ms
2 23352.your-cloud.host (168.119.221.28) 0.810 ms 0.817 ms 0.806 ms
3 * * *
4 * * *
5 spine15.cloud1.nbg1.hetzner.com (213.133.127.10) 1.256 ms 1.280 ms spine16.cloud1.nbg1.hetzner.com (213.133.127.6) 1.277 ms
6 core11.nbg1.hetzner.com (213.239.203.101) 1.379 ms core12.nbg1.hetzner.com (213.239.203.105) 1.138 ms 1.095 ms
7 juniper4.dc2.nbg1.hetzner.com (213.239.203.138) 1.265 ms juniper5.dc2.nbg1.hetzner.com (213.239.229.162) 0.428 ms juniper4.dc2.nbg1.hetzner.com (213.239.245.26) 0.463 ms
8 nug-b2-link.ip.twelve99.net (213.248.70.0) 14.761 ms nug-b2-link.ip.twelve99.net (62.115.183.232) 14.817 ms nug-b2-link.ip.twelve99.net (213.248.70.0) 14.457 ms
9 * * *
10 ldn-bb2-link.ip.twelve99.net (62.115.122.161) 27.615 ms 27.426 ms 27.422 ms
11 ewr-bb2-link.ip.twelve99.net (62.115.139.246) 96.031 ms 95.775 ms 95.759 ms
12 bost-b6-link.ip.twelve99.net (62.115.138.59) 106.045 ms 104.886 ms 105.869 ms
13 bost-b3-link.ip.twelve99.net (62.115.140.26) 103.222 ms * *
14 akamai-ic-384688.ip.twelve99-cust.net (62.115.159.249) 131.438 ms 121.069 ms 108.573 ms
15 ae2.r03.border01.bos01.fab.netarch.akamai.com (23.203.149.23) 103.837 ms 103.283 ms 103.415 ms
16 lo1.r04.stem01.bos01.fab.netarch.akamai.com (23.197.87.23) 107.774 ms lo1.r02.stem01.bos01.fab.netarch.akamai.com (23.197.87.21) 108.083 ms lo1.r04.stem01.bos01.fab.netarch.akamai.com (23.197.87.23) 106.951 ms
17 lo1.r04.spine03.bos01.fab.netarch.akamai.com (23.197.87.15) 105.695 ms lo1.r02.spine01.bos01.fab.netarch.akamai.com (23.197.87.5) 103.181 ms lo1.r04.spine04.bos01.fab.netarch.akamai.com (23.197.87.19) 103.433 ms
18 lo1.r03.leaf01.bos01.fab.netarch.akamai.com (23.197.87.26) 107.296 ms lo1.r02.leaf01.bos01.fab.netarch.akamai.com (23.197.87.25) 106.984 ms lo1.r01.leaf01.bos01.fab.netarch.akamai.com (23.197.87.24) 107.284 ms
19 vlan100.r12.tor01.bos01.fab.netarch.akamai.com (23.221.199.97) 103.567 ms 103.274 ms 103.271 ms
20 a23-221-236-99.deploy.static.akamaitechnologies.com (23.221.236.99) 106.837 ms 106.838 ms 103.159 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: 2025.08.31 05:30:46/ 2 months 7 days ago Confirmed: 2025.11.01 21:16:59/ 3 days 9 hours ago History: 2 records (hide history)
traceroute to sf16-telemetry-proxy-oci.tiktokcdn-us.com (23.221.236.99), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 3.044 ms 3.534 ms 3.692 ms
2 23352.your-cloud.host (168.119.221.28) 0.810 ms 0.817 ms 0.806 ms
3 * * *
4 * * *
5 spine15.cloud1.nbg1.hetzner.com (213.133.127.10) 1.256 ms 1.280 ms spine16.cloud1.nbg1.hetzner.com (213.133.127.6) 1.277 ms
6 core11.nbg1.hetzner.com (213.239.203.101) 1.379 ms core12.nbg1.hetzner.com (213.239.203.105) 1.138 ms 1.095 ms
7 juniper4.dc2.nbg1.hetzner.com (213.239.203.138) 1.265 ms juniper5.dc2.nbg1.hetzner.com (213.239.229.162) 0.428 ms juniper4.dc2.nbg1.hetzner.com (213.239.245.26) 0.463 ms
8 nug-b2-link.ip.twelve99.net (213.248.70.0) 14.761 ms nug-b2-link.ip.twelve99.net (62.115.183.232) 14.817 ms nug-b2-link.ip.twelve99.net (213.248.70.0) 14.457 ms
9 * * *
10 ldn-bb2-link.ip.twelve99.net (62.115.122.161) 27.615 ms 27.426 ms 27.422 ms
11 ewr-bb2-link.ip.twelve99.net (62.115.139.246) 96.031 ms 95.775 ms 95.759 ms
12 bost-b6-link.ip.twelve99.net (62.115.138.59) 106.045 ms 104.886 ms 105.869 ms
13 bost-b3-link.ip.twelve99.net (62.115.140.26) 103.222 ms * *
14 akamai-ic-384688.ip.twelve99-cust.net (62.115.159.249) 131.438 ms 121.069 ms 108.573 ms
15 ae2.r03.border01.bos01.fab.netarch.akamai.com (23.203.149.23) 103.837 ms 103.283 ms 103.415 ms
16 lo1.r04.stem01.bos01.fab.netarch.akamai.com (23.197.87.23) 107.774 ms lo1.r02.stem01.bos01.fab.netarch.akamai.com (23.197.87.21) 108.083 ms lo1.r04.stem01.bos01.fab.netarch.akamai.com (23.197.87.23) 106.951 ms
17 lo1.r04.spine03.bos01.fab.netarch.akamai.com (23.197.87.15) 105.695 ms lo1.r02.spine01.bos01.fab.netarch.akamai.com (23.197.87.5) 103.181 ms lo1.r04.spine04.bos01.fab.netarch.akamai.com (23.197.87.19) 103.433 ms
18 lo1.r03.leaf01.bos01.fab.netarch.akamai.com (23.197.87.26) 107.296 ms lo1.r02.leaf01.bos01.fab.netarch.akamai.com (23.197.87.25) 106.984 ms lo1.r01.leaf01.bos01.fab.netarch.akamai.com (23.197.87.24) 107.284 ms
19 vlan100.r12.tor01.bos01.fab.netarch.akamai.com (23.221.199.97) 103.567 ms 103.274 ms 103.271 ms
20 a23-221-236-99.deploy.static.akamaitechnologies.com (23.221.236.99) 106.837 ms 106.838 ms 103.159 ms