Block 211.101.0.0

← back to the map index · 211.0.0.0/8

Range211.101.0.0 - 211.101.63.255
Prefix211.101.0.0/18
Size16,384 addresses
Statusallocated — operator-held
Registryapnic
Country (delegation)CN
Date19991214
Opaque idA9162E3D
Block UUID0990f50c-c6da-57ab-b34c-fd112a0c36a7
Probes972
RDAP stateown — the registry object is this block
RDAP servicerdap.apnic.net
RDAP fetched2026-09-10T23:33:29Z
Flagsnone

RIR delegation record

registryapnic
countryCN
typeipv4
start211.101.0.0
value16,384
date19991214
statusallocated
extensions['A9162E3D']

RDAP summary

handle211.101.0.0 - 211.101.63.255
nameDXTNET
typeALLOCATED PORTABLE
parent handle—
start address211.101.0.0
end address211.101.63.255
countryCN
organizationXu Fuyuan
events{"registration": "2008-09-04T06:49:38Z", "last changed": "2023-11-28T00:57:24Z"}
entities2: abuse × 1, technical × 1 (contact details are not published)

Probes in this block

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

211.101.2.2 211.101.2.3 211.101.2.5 211.101.2.7 211.101.2.11 211.101.2.13 211.101.2.17 211.101.2.19 211.101.2.23 211.101.2.29 211.101.2.31 211.101.2.37 211.101.2.41 211.101.2.43 211.101.2.47 211.101.2.53 211.101.2.59 211.101.2.61 211.101.2.67 211.101.2.71 211.101.2.73 211.101.2.79 211.101.2.83 211.101.2.89 211.101.2.97 211.101.2.101 211.101.2.103 211.101.2.107 211.101.2.109 211.101.2.113 211.101.2.127 211.101.2.131 211.101.2.137 211.101.2.139 211.101.2.149 211.101.2.151 211.101.2.157 211.101.2.163 211.101.2.167 211.101.2.173 211.101.2.179 211.101.2.181 211.101.2.191 211.101.2.193 211.101.2.197 211.101.2.199 211.101.2.211 211.101.2.223 211.101.2.227 211.101.2.229 211.101.2.233 211.101.2.239 211.101.2.241 211.101.2.251 211.101.3.2 211.101.3.3 211.101.3.5 211.101.3.7 211.101.3.11 211.101.3.13

Who operates this: the layers, side by side

Delegation fileallocated, CN, 19991214
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.