#
# 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: 157.240.0.0 - 157.240.255.255
CIDR: 157.240.0.0/16
NetName: THEFA-3
NetHandle: NET-157-240-0-0-1
Parent: NET157 (NET-157-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Facebook, Inc. (THEFA-3)
RegDate: 2015-05-14
Updated: 2021-12-14
Ref: https://rdap.arin.net/registry/ip/157.240.0.0
OrgName: Facebook, Inc.
OrgId: THEFA-3
Address: 1601 Willow Rd.
City: Menlo Park
StateProv: CA
PostalCode: 94025
Country: US
RegDate: 2004-08-11
Updated: 2012-04-17
Ref: https://rdap.arin.net/registry/entity/THEFA-3
OrgAbuseHandle: OPERA82-ARIN
OrgAbuseName: Operations
OrgAbusePhone: +1-650-543-4800
OrgAbuseEmail: domain@facebook.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/OPERA82-ARIN
OrgTechHandle: OPERA82-ARIN
OrgTechName: Operations
OrgTechPhone: +1-650-543-4800
OrgTechEmail: domain@facebook.com
OrgTechRef: https://rdap.arin.net/registry/entity/OPERA82-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.
#
Cached: 2022.02.11 13:49:31/ 2 years 9 months ago Confirmed: 2022.02.12 02:57:22/ 2 years 9 months ago
63.229.240.157.in-addr.arpa domain name pointer instagram-p3-shv-02-iad3.fbcdn.net.
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.02.03 04:03:06/ 2 years 9 months ago Confirmed: 2022.11.28 19:04:16/ 1 year 11 months ago History: 2 records (show history)
traceroute to 157.240.229.63 (157.240.229.63), 30 hops max, 60 byte packets
1 gateway (172.31.1.1) 7.004 ms 7.074 ms 7.053 ms
2 19541.your-cloud.host (168.119.217.134) 0.322 ms 0.472 ms 0.408 ms
3 * * *
4 static.125.14.46.78.clients.your-server.de (78.46.14.125) 1.259 ms static.121.14.46.78.clients.your-server.de (78.46.14.121) 1.303 ms static.125.14.46.78.clients.your-server.de (78.46.14.125) 1.553 ms
5 spine13.cloud1.nbg1.hetzner.com (213.133.114.1) 1.189 ms spine14.cloud1.nbg1.hetzner.com (213.133.114.5) 1.052 ms spine14.cloud1.nbg1.hetzner.com (213.133.113.77) 1.597 ms
6 213-239-239-121.clients.your-server.de (213.239.239.121) 2.292 ms * 0.429 ms
7 juniper4.dc2.nbg1.hetzner.com (213.239.245.26) 0.676 ms juniper4.dc2.nbg1.hetzner.com (213.239.203.138) 0.308 ms juniper6.dc2.nbg1.hetzner.com (213.239.245.78) 0.396 ms
8 nug-b2-link.ip.twelve99.net (62.115.50.222) 3.501 ms 3.498 ms nug-b1-link.ip.twelve99.net (213.248.70.0) 0.870 ms
9 prs-bb2-link.ip.twelve99.net (62.115.112.214) 14.884 ms ffm-bb1-link.ip.twelve99.net (62.115.113.146) 3.689 ms prs-bb2-link.ip.twelve99.net (62.115.112.214) 14.925 ms
10 * prs-bb1-link.ip.twelve99.net (62.115.123.13) 12.131 ms rest-bb1-link.ip.twelve99.net (62.115.122.159) 92.022 ms
11 ash-bb2-link.ip.twelve99.net (62.115.112.242) 97.395 ms 97.548 ms 97.778 ms
12 ash-b2-link.ip.twelve99.net (62.115.123.125) 97.814 ms 97.846 ms facebook-ic337861-ash-b2.ip.twelve99-cust.net (62.115.12.91) 96.006 ms
13 facebook-ic337863-ash-b2.ip.twelve99-cust.net (62.115.12.115) 98.308 ms po103.psw03.iad3.tfbnw.net (31.13.27.99) 91.579 ms po104.psw04.iad3.tfbnw.net (31.13.28.99) 92.290 ms
14 157.240.36.11 (157.240.36.11) 95.413 ms po106.psw03.iad3.tfbnw.net (157.240.43.129) 93.279 ms po106.psw02.iad3.tfbnw.net (157.240.43.127) 93.248 ms
15 instagram-p3-shv-02-iad3.fbcdn.net (157.240.229.63) 92.009 ms 91.904 ms 173.252.67.235 (173.252.67.235) 93.866 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.02.11 13:49:31/ 2 years 9 months ago Confirmed: 2022.02.12 02:57:22/ 2 years 9 months ago
63.229.240.157.in-addr.arpa domain name pointer instagram-p3-shv-02-iad3.fbcdn.net.