#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2022, American Registry for Internet Numbers, Ltd.
#
NetRange: 2001:4998:: - 2001:4998:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
CIDR: 2001:4998::/32
NetName: YAHOO-IPV6-BLK-2
NetHandle: NET6-2001-4998-1
Parent: ARIN-004 (NET6-2001-4800-0)
NetType: Direct Allocation
OriginAS: AS10310
Organization: Oath Holdings Inc. (OH-207)
RegDate: 2005-10-27
Updated: 2019-05-01
Ref: https://rdap.arin.net/registry/ip/2001:4998::
OrgName: Oath Holdings Inc.
OrgId: OH-207
Address: 770 BROADWAY FL 4
City: New York
StateProv: NY
PostalCode: 10003-9558
Country: US
RegDate: 2018-12-21
Updated: 2019-05-16
Ref: https://rdap.arin.net/registry/entity/OH-207
OrgAbuseHandle: OATHA-ARIN
OrgAbuseName: Oath Abuse
OrgAbusePhone: +1-408-349-3300
OrgAbuseEmail: rir-abuse@yahoo-inc.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/OATHA-ARIN
OrgNOCHandle: OATHN-ARIN
OrgNOCName: Oath NOC
OrgNOCPhone: +1-408-349-5555
OrgNOCEmail: rir-noc@yahooinc.com
OrgNOCRef: https://rdap.arin.net/registry/entity/OATHN-ARIN
OrgTechHandle: OTC2-ARIN
OrgTechName: Oath Tech Contact
OrgTechPhone: +1-408-349-5555
OrgTechEmail: rir-tech@oath.com
OrgTechRef: https://rdap.arin.net/registry/entity/OTC2-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2022, American Registry for Internet Numbers, Ltd.
#
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.
No results found, please run it to get the result.
Cached: 2022.07.10 18:34:08/ 2 years 5 months ago Confirmed: 2022.07.10 19:47:07/ 2 years 5 months ago
traceroute to 2001:4998:124:1507::f001 (2001:4998:124:1507::f001), 30 hops max, 80 byte packets
1 fe80::%eth0 (fe80::%eth0) 6.892 ms 8.265 ms 8.189 ms
2 2a01:4f8:0:e0c0::413c (2a01:4f8:0:e0c0::413c) 0.834 ms 0.977 ms 0.962 ms
3 * * *
4 2a01:4f8:0:e0c0::a15d (2a01:4f8:0:e0c0::a15d) 19.185 ms 2a01:4f8:0:e0c0::a159 (2a01:4f8:0:e0c0::a159) 1.491 ms 2a01:4f8:0:e0c0::a15d (2a01:4f8:0:e0c0::a15d) 19.160 ms
5 spine11.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1ed) 1.591 ms spine13.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a279) 1.785 ms spine12.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1f1) 3.028 ms
6 core11.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1f9) 1.443 ms 2a01:4f8:0:e0c0::a001 (2a01:4f8:0:e0c0::a001) 4.745 ms 2a01:4f8:0:e0c0::a005 (2a01:4f8:0:e0c0::a005) 0.383 ms
7 core4.fra.hetzner.com (2a01:4f8:0:3::f5) 3.585 ms core0.fra.hetzner.com (2a01:4f8:0:3::355) 5.233 ms core0.fra.hetzner.com (2a01:4f8:0:3::351) 3.364 ms
8 ge-1-3-0.pat2.dee.yahoo.com (2001:7f8::2846:0:2) 3.867 ms 3.765 ms ge-1-3-0.pat1.dee.yahoo.com (2001:7f8::2846:0:1) 3.725 ms
9 ae-3.pat2.frz.yahoo.com (2a00:1288:f021:20d::1) 13.829 ms 13.637 ms ae-0.pat2.dez.yahoo.com (2a00:1288:f021::1) 9.787 ms
10 ae-11.pat1.dce.yahoo.com (2001:4998:f003:3::) 91.487 ms 91.448 ms ae-1.pat2.frz.yahoo.com (2a00:1288:f025:1::1) 13.566 ms
11 ae-4.pat1.nyc.yahoo.com (2001:4998:f003:13::1) 89.290 ms ae-11.pat1.dce.yahoo.com (2001:4998:f003:3::) 91.217 ms ae-4.pat1.nyc.yahoo.com (2001:4998:f003:13::1) 88.794 ms
12 ae-4.pat1.nyc.yahoo.com (2001:4998:f003:13::1) 88.356 ms ae-0.pat1.bfw.yahoo.com (2001:4998:f00b:13::1) 100.027 ms ae-4.pat1.nyc.yahoo.com (2001:4998:f003:13::1) 88.352 ms
13 ae-1.pat2.bfw.yahoo.com (2001:4998:f00b:206::1) 98.662 ms 2001:4998:f023::1 (2001:4998:f023::1) 98.420 ms ae-1.pat2.bfw.yahoo.com (2001:4998:f00b:206::1) 100.399 ms
14 2001:4998:124:fc02::1 (2001:4998:124:fc02::1) 102.229 ms 2001:4998:58:fe21::1 (2001:4998:58:fe21::1) 101.520 ms 2001:4998:f023:5::1 (2001:4998:f023:5::1) 98.489 ms
15 2001:4998:124:f805::1 (2001:4998:124:f805::1) 100.848 ms 2001:4998:124:fc03::1 (2001:4998:124:fc03::1) 102.169 ms 2001:4998:124:fa04::1 (2001:4998:124:fa04::1) 99.555 ms
16 et29.usw1-1-lbb.bf2.yahoo.com (2001:4998:124:d206::1) 98.367 ms et27.usw1-1-lbb.bf2.yahoo.com (2001:4998:124:d606::1) 100.717 ms et26.usw2-1-lbb.bf2.yahoo.com (2001:4998:124:d807::1) 101.980 ms
17 media-router-fp74.prod.media.vip.bf1.yahoo.com (2001:4998:124:1507::f001) 102.126 ms et30.usw1-1-lbb.bf2.yahoo.com (2001:4998:124:d006::1) 100.481 ms media-router-fp74.prod.media.vip.bf1.yahoo.com (2001:4998:124:1507::f001) 98.246 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: 2022.07.10 16:00:18/ 2 years 5 months ago
PING 2001:4998:124:1507::f001(2001:4998:124:1507::f001) 56 data bytes
64 bytes from 2001:4998:124:1507::f001: icmp_seq=1 ttl=50 time=102 ms
64 bytes from 2001:4998:124:1507::f001: icmp_seq=2 ttl=50 time=102 ms
64 bytes from 2001:4998:124:1507::f001: icmp_seq=3 ttl=50 time=101 ms
--- 2001:4998:124:1507::f001 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 101.849/102.014/102.119/0.387 ms