Block 167.71.0.0

← back to the map index · 167.0.0.0/8

Range167.71.0.0 - 167.71.255.255
Prefix167.71.0.0/16
Size65,536 addresses
Statusallocated — operator-held
Registryarin
Country (delegation)US
Date20190424
Opaque idcd0f3b8e7d9444ab07dc47565abf4031
Block UUID0cd44fff-a6aa-539b-84d9-5161a89790c7
Probes2,916
RDAP stateown — the registry object is this block
RDAP servicerdap.arin.net
RDAP fetched2026-09-10T23:13:02Z
Flagsnone

RIR delegation record

registryarin
countryUS
typeipv4
start167.71.0.0
value65,536
date20190424
statusallocated
extensions['cd0f3b8e7d9444ab07dc47565abf4031']

RDAP summary

handleNET-167-71-0-0-1
nameDIGITALOCEAN-167-71-0-0
typeDIRECT ALLOCATION
parent handleNET-167-0-0-0-0
start address167.71.0.0
end address167.71.255.255
country—
organizationDigitalOcean, LLC
events{"last changed": "2020-04-03T14:12:23-04:00", "registration": "2019-04-24T15:35:13-04:00"}
entities1: registrant × 1 (contact details are not published)

Probes in this block

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

167.71.2.2 167.71.2.3 167.71.2.5 167.71.2.7 167.71.2.11 167.71.2.13 167.71.2.17 167.71.2.19 167.71.2.23 167.71.2.29 167.71.2.31 167.71.2.37 167.71.2.41 167.71.2.43 167.71.2.47 167.71.2.53 167.71.2.59 167.71.2.61 167.71.2.67 167.71.2.71 167.71.2.73 167.71.2.79 167.71.2.83 167.71.2.89 167.71.2.97 167.71.2.101 167.71.2.103 167.71.2.107 167.71.2.109 167.71.2.113 167.71.2.127 167.71.2.131 167.71.2.137 167.71.2.139 167.71.2.149 167.71.2.151 167.71.2.157 167.71.2.163 167.71.2.167 167.71.2.173 167.71.2.179 167.71.2.181 167.71.2.191 167.71.2.193 167.71.2.197 167.71.2.199 167.71.2.211 167.71.2.223 167.71.2.227 167.71.2.229 167.71.2.233 167.71.2.239 167.71.2.241 167.71.2.251 167.71.3.2 167.71.3.3 167.71.3.5 167.71.3.7 167.71.3.11 167.71.3.13

Who operates this: the layers, side by side

Delegation fileallocated, US, 20190424
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.