% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '2a03:2880::/29'
% Abuse contact for '2a03:2880::/29' is 'domain@fb.com'
inet6num: 2a03:2880::/29
netname: IE-FACEBOOK-201100822
country: IE
org: ORG-FIL7-RIPE
admin-c: NE1880-RIPE
tech-c: NE1880-RIPE
status: ALLOCATED-BY-RIR
mnt-by: RIPE-NCC-HM-MNT
mnt-by: meta-mnt
mnt-routes: fb-neteng
created: 2015-09-24T12:59:37Z
last-modified: 2022-10-29T00:51:39Z
source: RIPE # Filtered
organisation: ORG-FIL7-RIPE
org-name: Meta Platforms Ireland Limited
country: IE
org-type: LIR
address: Merrion Road Dublin 4
address: D04 X2K5
address: Dublin
address: IRELAND
phone: +353 1443 4342
phone: +0016505434800
fax-no: +0016505435325
admin-c: PH4972-RIPE
mnt-ref: RIPE-NCC-HM-MNT
mnt-ref: meta-mnt
mnt-by: RIPE-NCC-HM-MNT
mnt-by: meta-mnt
abuse-c: RD4299-RIPE
created: 2011-04-07T13:16:29Z
last-modified: 2024-04-29T09:07:11Z
source: RIPE # Filtered
role: Network Engineering
address: 4 GRAND CANAL SQUARE, GRAND CANAL HARBOUR, DUBLIN, IRELAND
nic-hdl: NE1880-RIPE
mnt-by: fb-neteng
mnt-by: facebook-neteng
created: 2022-05-19T14:17:28Z
last-modified: 2022-05-19T14:17:28Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.116 (DEXTER)
Cached: 2025.03.31 19:54:43/ 20 days 22 hours ago Confirmed: 2025.03.31 19:54:44/ 20 days 22 hours ago
0.2.4.4.0.0.0.0.c.0.0.b.e.c.a.f.5.e.1.0.8.4.2.f.0.8.8.2.3.0.a.2.ip6.arpa domain name pointer instagram-p426-shv-02-gru1.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: 2025.03.31 19:55:04/ 20 days 22 hours ago Confirmed: 2025.03.31 19:55:05/ 20 days 22 hours ago
traceroute to 2a03:2880:f248:1e5:face:b00c:0:4420 (2a03:2880:f248:1e5:face:b00c:0:4420), 30 hops max, 80 byte packets
1 fe80::%eth0 (fe80::%eth0) 4.173 ms 4.601 ms 4.699 ms
2 22399.your-cloud.host (2a01:4f8:0:e0c0::703c) 0.509 ms 0.568 ms 0.770 ms
3 * * *
4 spine7.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a2b1) 48.044 ms spine8.cloud1.nbg1.hetzner.com (2a01:4f8:0:e0c0::a2b5) 3.226 ms 3.227 ms
5 * * *
6 core11.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1e1) 1.426 ms 0.967 ms core12.nbg1.hetzner.com (2a01:4f8:0:e0c0::a1e5) 0.968 ms
7 core5.fra.hetzner.com (2a01:4f8:0:3::326) 3.613 ms core0.fra.hetzner.com (2a01:4f8:0:3::351) 3.511 ms core5.fra.hetzner.com (2a01:4f8:0:3::326) 3.459 ms
8 ae1.pr01.fra2.tfbnw.net (2620:0:1cff:dead:beee::19f6) 3.629 ms ae1.pr02.fra2.tfbnw.net (2620:0:1cff:dead:beee::19f0) 3.516 ms ae2.pr01.fra2.tfbnw.net (2620:0:1cff:dead:beee::624) 3.617 ms
9 po171.asw02.fra5.tfbnw.net (2620:0:1cff:dead:beef::8f8) 3.999 ms po171.asw01.fra5.tfbnw.net (2620:0:1cff:dead:beef::7a6) 3.841 ms po181.asw01.fra2.tfbnw.net (2620:0:1cff:dead:beef::5fa) 3.657 ms
10 ae3.ar01.fra5.tfbnw.net (2620:0:1cff:dead:beef::c5a) 4.550 ms ae121.ar01.fra2.tfbnw.net (2620:0:1cff:dead:beef::52f6) 4.712 ms ae111.ar02.fra2.tfbnw.net (2620:0:1cff:dead:beef::1522) 9.502 ms
11 ae146.bb04.fra8.tfbnw.net (2620:0:1cff:dead:beef::38de) 4.727 ms 5.589 ms ae5.bb03.fra5.tfbnw.net (2620:0:1cff:dead:beef::1d42) 7.188 ms
12 ae129.bb04.fra5.tfbnw.net (2620:0:1cff:dead:beef::1a18) 9.977 ms ae21.bb03.cdg1.tfbnw.net (2620:0:1cff:dead:beef::b88) 16.672 ms ae23.bb02.cdg1.tfbnw.net (2620:0:1cff:dead:beef::c64) 13.534 ms
13 ae16.bb01.cdg1.tfbnw.net (2620:0:1cff:dead:beef::c6e) 14.586 ms ae29.bb04.bio1.tfbnw.net (2620:0:1cff:dead:beef::363a) 38.454 ms ae16.bb01.cdg1.tfbnw.net (2620:0:1cff:dead:beef::c6e) 14.176 ms
14 ae28.bb03.bio1.tfbnw.net (2620:0:1cff:dead:beef::3634) 38.700 ms ae202.bb03.vab1.tfbnw.net (2620:0:1cff:dead:beef::1c11) 104.587 ms ae202.bb04.vab1.tfbnw.net (2620:0:1cff:dead:beef::1c19) 102.574 ms
15 ae202.bb04.vab1.tfbnw.net (2620:0:1cff:dead:beef::1c19) 102.188 ms ae202.bb02.vab1.tfbnw.net (2620:0:1cff:dead:beef::1c13) 99.072 ms ae3.bb01.gig3.tfbnw.net (2620:0:1cff:dead:beef::176) 226.941 ms
16 ae54.bb02.gru1.tfbnw.net (2620:0:1cff:dead:beef::553) 230.769 ms 229.768 ms ae4.bb03.gig3.tfbnw.net (2620:0:1cff:dead:beef::18a) 230.713 ms
17 ae55.bb01.gru1.tfbnw.net (2620:0:1cff:dead:beef::3f59) 229.143 ms ae2.ar02.gru1.tfbnw.net (2620:0:1cff:dead:beef::e8d) 214.213 ms ae55.bb01.gru1.tfbnw.net (2620:0:1cff:dead:beef::3f59) 228.349 ms
18 ae2.ar01.gru2.tfbnw.net (2620:0:1cff:dead:beef::17dd) 244.091 ms 244.006 ms po211.asw01.gru1.tfbnw.net (2620:0:1cff:dead:beef::256b) 213.711 ms
19 po221.asw01.gru1.tfbnw.net (2620:0:1cff:dead:beef::256d) 213.613 ms po211.asw02.gru1.tfbnw.net (2620:0:1cff:dead:beef::256f) 213.379 ms ae1.ar01.gru2.tfbnw.net (2620:0:1cff:dead:beef::4f3) 228.056 ms
20 be3.msw1ak.02.gru1.tfbnw.net (2a03:2880:f048:ffff::27d) 217.490 ms be2.msw1ao.02.gru1.tfbnw.net (2a03:2880:f048:ffff::251) 216.098 ms po221.asw02.gru2.tfbnw.net (2620:0:1cff:dead:beef::1dc3) 213.835 ms
21 po3.msw1ar.02.gru1.tfbnw.net (2a03:2880:f048:ffff::28b) 214.141 ms po282.psw02.gru1.tfbnw.net (2620:0:1cff:dead:beef::5451) 213.899 ms po4.msw1ar.02.gru1.tfbnw.net (2a03:2880:f048:ffff::2bf) 213.446 ms
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
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.03.31 19:54:43/ 20 days 22 hours ago Confirmed: 2025.03.31 19:54:44/ 20 days 22 hours ago
0.2.4.4.0.0.0.0.c.0.0.b.e.c.a.f.5.e.1.0.8.4.2.f.0.8.8.2.3.0.a.2.ip6.arpa domain name pointer instagram-p426-shv-02-gru1.fbcdn.net.