Block 163.61.96.0

← back to the map index · 163.0.0.0/8

Range163.61.96.0 - 163.61.97.255
Prefix163.61.96.0/23
Size512 addresses
Statusallocated — operator-held
Registryapnic
Country (delegation)IN
Date20250210
Opaque idA91BDEEB
Block UUID2e7e20f0-0cc3-5e93-9e87-6c54a082e76f
Probes54
RDAP stateown — the registry object is this block
RDAP servicerdap.apnic.net
RDAP fetched2026-09-10T23:12:23Z
Flagsnone

RIR delegation record

registryapnic
countryIN
typeipv4
start163.61.96.0
value512
date20250210
statusallocated
extensions['A91BDEEB']

RDAP summary

handle163.61.96.0 - 163.61.97.255
nameVILMAX3-IN
typeALLOCATED PORTABLE
parent handle—
start address163.61.96.0
end address163.61.97.255
countryIN
organizationVILMAX INTERNET SERVICES PRIVATE LIMITED administrator
events{"registration": "2025-02-10T03:27:52Z", "last changed": "2025-02-10T03:28:22Z"}
entities3: abuse × 1, administrative × 1, registrant × 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.

163.61.97.2 163.61.97.3 163.61.97.5 163.61.97.7 163.61.97.11 163.61.97.13 163.61.97.17 163.61.97.19 163.61.97.23 163.61.97.29 163.61.97.31 163.61.97.37 163.61.97.41 163.61.97.43 163.61.97.47 163.61.97.53 163.61.97.59 163.61.97.61 163.61.97.67 163.61.97.71 163.61.97.73 163.61.97.79 163.61.97.83 163.61.97.89 163.61.97.97 163.61.97.101 163.61.97.103 163.61.97.107 163.61.97.109 163.61.97.113 163.61.97.127 163.61.97.131 163.61.97.137 163.61.97.139 163.61.97.149 163.61.97.151 163.61.97.157 163.61.97.163 163.61.97.167 163.61.97.173 163.61.97.179 163.61.97.181 163.61.97.191 163.61.97.193 163.61.97.197 163.61.97.199 163.61.97.211 163.61.97.223 163.61.97.227 163.61.97.229 163.61.97.233 163.61.97.239 163.61.97.241 163.61.97.251

Who operates this: the layers, side by side

Delegation fileallocated, IN, 20250210
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.