Block 43.229.176.0

← back to the map index · 43.0.0.0/8

Range43.229.176.0 - 43.229.179.255
Prefix43.229.176.0/22
Size1,024 addresses
Statusallocated — operator-held
Registryapnic
Country (delegation)CN
Date20150127
Opaque idA927D4D0
Block UUID9193ac35-d644-579b-8e95-7ae361ce8516
Probes54
RDAP stateown — the registry object is this block
RDAP servicerdap.apnic.net
RDAP fetched2026-09-10T22:55:42Z
Flagsnone

RIR delegation record

registryapnic
countryCN
typeipv4
start43.229.176.0
value1,024
date20150127
statusallocated
extensions['A927D4D0']

RDAP summary

handle43.229.176.0 - 43.229.179.255
namePOWER
typeALLOCATED PORTABLE
parent handle—
start address43.229.176.0
end address43.229.179.255
countryCN
organizationjinglong Wang
events{"registration": "2015-01-27T06:49:03Z", "last changed": "2023-11-28T00:57:56Z"}
entities3: abuse × 1, administrative × 1, technical × 1 (contact details are not published)

Probes in this block

54 probes; the first 54 are listed. An asterisk means phase 3 heard something back.

43.229.179.2 43.229.179.3 43.229.179.5 43.229.179.7 43.229.179.11 43.229.179.13 43.229.179.17 43.229.179.19 43.229.179.23 43.229.179.29 43.229.179.31 43.229.179.37 43.229.179.41 43.229.179.43 43.229.179.47 43.229.179.53 43.229.179.59 43.229.179.61 43.229.179.67 43.229.179.71 43.229.179.73 43.229.179.79 43.229.179.83 43.229.179.89 43.229.179.97 43.229.179.101 43.229.179.103 43.229.179.107 43.229.179.109 43.229.179.113 43.229.179.127 43.229.179.131 43.229.179.137 43.229.179.139 43.229.179.149 43.229.179.151 43.229.179.157 43.229.179.163 43.229.179.167 43.229.179.173 43.229.179.179 43.229.179.181 43.229.179.191 43.229.179.193 43.229.179.197 43.229.179.199 43.229.179.211 43.229.179.223 43.229.179.227 43.229.179.229 43.229.179.233 43.229.179.239 43.229.179.241 43.229.179.251

Who operates this: the layers, side by side

Delegation fileallocated, CN, 20150127
Registry objectown — the registry object is this block
Routingnot recorded
Authorizationnot recorded
DNS pointing herenot recorded
Certificatenone presented

The registry's verbatim RDAP answer is kept in the local work product dataflow.out/02_ip_block.json and is not published, because it carries registrant contact details.