Domain Name: TEDDYBEARMETAL.COM
Registry Domain ID: 2616212828_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: http://registrar.amazon.com
Updated Date: 2023-04-27T02:24:03Z
Creation Date: 2021-05-31T11:54:59Z
Registry Expiry Date: 2024-05-31T11:54:59Z
Registrar: Amazon Registrar, Inc.
Registrar IANA ID: 468
Registrar Abuse Contact Email: abuse@amazonaws.com
Registrar Abuse Contact Phone: +1.2067406200
Domain Status: ok https://icann.org/epp#ok
Name Server: NS-1201.AWSDNS-22.ORG
Name Server: NS-1865.AWSDNS-41.CO.UK
Name Server: NS-363.AWSDNS-45.COM
Name Server: NS-854.AWSDNS-42.NET
DNSSEC: unsigned
Cached: 2023.12.30 20:12:18/ 3 months 28 days ago
happy.teddybearmetal.com has address 13.32.27.63happy.teddybearmetal.com has address 13.32.27.34happy.teddybearmetal.com has address 13.32.27.125happy.teddybearmetal.com has address 13.32.27.47happy.teddybearmetal.com has IPv6 address 2600:9000:211e:c800:11:eb39:67c0:93a1happy.teddybearmetal.com has IPv6 address 2600:9000:211e:1a00:11:eb39:67c0:93a1happy.teddybearmetal.com has IPv6 address 2600:9000:211e:7e00:11:eb39:67c0:93a1happy.teddybearmetal.com has IPv6 address 2600:9000:211e:e800:11:eb39:67c0:93a1happy.teddybearmetal.com has IPv6 address 2600:9000:211e:ca00:11:eb39:67c0:93a1happy.teddybearmetal.com has IPv6 address 2600:9000:211e:f000:11:eb39:67c0:93a1happy.teddybearmetal.com has IPv6 address 2600:9000:211e:aa00:11:eb39:67c0:93a1happy.teddybearmetal.com has IPv6 address 2600:9000:211e:8e00:11:eb39:67c0:93a1
No results found, please run it to get the result.
Cached: 2023.12.30 20:11:46/ 3 months 28 days ago Confirmed: 2023.12.30 20:12:48/ 3 months 28 days ago History: 2 records (show history)
No results found, please run it to get the result.
Cached: 2023.12.30 20:13:21/ 3 months 28 days ago
traceroute to happy.teddybearmetal.com (13.32.27.63), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 2.587 ms 2.571 ms 2.585 ms
2 21716.your-cloud.host (49.12.143.144) 0.485 ms 0.500 ms 0.544 ms
3 * * *
4 static.93.143.12.49.clients.your-server.de (49.12.143.93) 1.800 ms 2.071 ms 2.083 ms
5 * * *
6 core11.nbg1.hetzner.com (213.239.239.121) 16.644 ms core12.nbg1.hetzner.com (213.239.239.141) 0.837 ms 0.828 ms
7 core5.fra.hetzner.com (213.239.224.238) 3.926 ms core4.fra.hetzner.com (213.239.245.245) 3.576 ms core5.fra.hetzner.com (213.239.224.234) 3.467 ms
8 213-133-113-126.clients.your-server.de (213.133.113.126) 4.360 ms 4.319 ms amazon.hetzner.com (213.133.116.38) 3.920 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 server-13-32-27-63.fra56.r.cloudfront.net (13.32.27.63) 4.930 ms 4.932 ms 4.961 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: 2023.12.30 20:13:21/ 3 months 28 days ago
traceroute to happy.teddybearmetal.com (13.32.27.63), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 2.587 ms 2.571 ms 2.585 ms
2 21716.your-cloud.host (49.12.143.144) 0.485 ms 0.500 ms 0.544 ms
3 * * *
4 static.93.143.12.49.clients.your-server.de (49.12.143.93) 1.800 ms 2.071 ms 2.083 ms
5 * * *
6 core11.nbg1.hetzner.com (213.239.239.121) 16.644 ms core12.nbg1.hetzner.com (213.239.239.141) 0.837 ms 0.828 ms
7 core5.fra.hetzner.com (213.239.224.238) 3.926 ms core4.fra.hetzner.com (213.239.245.245) 3.576 ms core5.fra.hetzner.com (213.239.224.234) 3.467 ms
8 213-133-113-126.clients.your-server.de (213.133.113.126) 4.360 ms 4.319 ms amazon.hetzner.com (213.133.116.38) 3.920 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 server-13-32-27-63.fra56.r.cloudfront.net (13.32.27.63) 4.930 ms 4.932 ms 4.961 ms