When an IP address is not allocated to any organization at the registry level, we do not return their geolocation or ASN data. When that is the case, there is no foundation for geolocation or ASN data to be built on, and we return nothing.
How IP intelligence is built
IP geolocation and ASN data do not come from the IP address itself. They come from layered inputs:
- Registry allocations from the five RIRs (RIPE, ARIN, APNIC, LACNIC, AFRINIC) provide the org, country, and abuse contact for a given range.
- BGP announcements provide the origin ASN and routing context.
- Active measurement (probe RTT, traceroute, latency triangulation) provides city-level geolocation.
- Reverse DNS, passive DNS, and other signals add hostname and domain context.
If an IP is not covered by a registered allocation and is not announced in BGP, none of those layers produce a result. There is no parent block to inherit data from, no origin AS, and no traffic for our probes to measure against. We return an empty response in that case rather than fabricate a location.
Two examples
212.11.64.250 and 185.196.11.225 are both in this state today. A direct WHOIS query to RIPE for either address returns only the IANA root object:
inetnum: 0.0.0.0 - 255.255.255.255
netname: IANA-BLK
descr: The whole IPv4 address space
country: EU
org: ORG-IANA1-RIPE
status: ALLOCATED UNSPECIFIED
remarks: This object represents all IPv4 addresses.
remarks: If you see this object as a result of a single IP query, it
remarks: means that the IP address you are querying is currently not
remarks: assigned to any organisation.
mnt-by: RIPE-NCC-HM-MNT
source: RIPE
The remarks section states the condition directly. Neither IP is covered by a more-specific inetnum object. There is no LIR allocation, no registered org, and no abuse contact. The IPs sit in space that RIPE has received from IANA but has not yet sub-allocated to any network.
How to verify the routing side
If you want to confirm whether the prefix is announced in BGP, RIPEstat and bgp.tools both expose routing-status lookups. An unrouted prefix is unreachable on the public internet, which is consistent with an empty enrichment response.
When this state changes
Allocations are not static. When RIPE assigns one of these ranges to an LIR and the new holder begins announcing the prefix, our pipeline picks up the registry update and the routing data on the next cycle, and the IPs move from empty to enriched. Until then, an honest empty response is the correct answer.