Summary

  • RIPE NCC’s live RDAP response for 193.0.0.0 carries country: "NL" inside an IP-network registration object.
  • RFC 9083 defines this as a two-character country code of the network; the field alone does not locate routers, users, traffic, services or the BGP origin.

A registration attribute, not a coordinate

The RIPE NCC response covers 193.0.0.0–193.0.7.255 and returns country: "NL". The same object separately records its handle, name, RIR-specific type, address bounds, IP version, status, links and events. That placement is the defensible scope: NL is the country value served for this network registration at the time of capture.

RFC 9083 section 5.4 describes the country member as a string containing the two-character country code of the network. The specification uses ISO 3166 alpha-2 notation when a country identity is needed. It does not turn the value into latitude, longitude or a measurement of infrastructure presence.

Geolocation requires different evidence

Addresses can be announced from many places, carried across borders, used by remote customers or served through distributed infrastructure. A registry country code can remain unchanged while topology and use change. BGP observations are required for route-origin and path claims; measurements, operator disclosures and service data are required for physical or user location.

The field also cannot, by itself, establish a company’s legal domicile, headquarters or contractual responsibility. Preserve it with the object handle, source URL and capture time. Any map, sanctions decision, latency expectation or jurisdictional conclusion needs its own evidence and uncertainty.

Sources