Summary

  • In the captured ARIN response for 8.8.8.8, parentHandle links the network registration NET-8-8-8-0-2 to the parent registration NET-8-0-0-0-0.
  • That link is registry evidence. It does not identify a transit provider, commercial upstream, BGP path or the network currently carrying traffic.

The ARIN RDAP response for 8.8.8.8, captured on 26 August 2026, places two similar-looking identifiers within the same object. The object’s own handle is NET-8-8-8-0-2; its parentHandle is NET-8-0-0-0-0. The first record covers 8.8.8.0 through 8.8.8.255, carries the name GOGL, and is classified as a DIRECT ALLOCATION. Read casually, the second handle can look like an operational dependency: a larger network behind a smaller one. Read according to the data model, it says something narrower and more useful.

ARIN describes RDAP as a service for querying Internet resource registration data. Its documented parent traversal returns another registry object. That is the relevant frame: the response is showing how one registered range is contained within a parent registration in ARIN’s records. It is not presenting a measurement of packets, an interconnection agreement, or a routing table.

The standard is unusually direct on this point. RFC 9083 defines parentHandle as the RIR-unique identifier of the parent network of the network registration. The last two words matter. The parent belongs to the registration model. The field is therefore valuable when an investigator needs to follow allocation lineage, check the scope of a record, distinguish a specific registered range from a covering record, or understand which registry object sits above another.

The field is silent about a different set of questions. It does not say which autonomous system originates 8.8.8.0/24, which networks propagate reachability, whether any of them sell transit, what contract governs carriage, or which path a packet would take from a particular vantage point. The captured object contains no upstream ASN, BGP peer, forwarding next hop or route path. Absence alone does not answer those questions; it tells the analyst that this object is not the evidence surface on which to answer them.

RFC 4271 locates operational path evidence elsewhere. BGP exchanges reachability between autonomous systems, and its mandatory AS_PATH attribute records the autonomous systems through which routing information has passed. Even an observed AS path has its own limits—it is an observation of routing information from a vantage point, not a commercial contract—but it is at least evidence from the routing system. A registry parent handle is not.

This separation prevents a common category error. A large parent registration may reflect delegation history or database organization without being the current carrier of the more-specific range. Conversely, a network that carries traffic may never appear as the parent of the address registration. Registration containment and network transit can coexist, but one does not prove the other.

For practical research, the correct move is not to discard parentHandle, but to label its evidentiary role precisely. Use it to walk the registration hierarchy. If the question changes to origin, propagation, peering, transit or forwarding, open a new evidence track and time-stamp it. The result is a cleaner chain of reasoning: ARIN RDAP establishes what the registry relates; routing observations establish what networks announce; commercial evidence, where available, establishes what organizations have agreed.

The two handles in the captured response therefore answer a bounded question with confidence. NET-8-8-8-0-2 sits beneath NET-8-0-0-0-0 in the registration hierarchy represented by ARIN RDAP. They do not, on their own, name a network transit relationship.