Every time a DOI resolves — a browser sends a user from https://doi.org/10.1234/example to the actual location of the article, dataset, or record it names — that lookup is not performed by the DOI system itself. It is performed by the Handle System, a general-purpose identifier resolution infrastructure that DOI is built on top of. The DOI syntax, DOI-specific metadata rules, and the Registration Agency model (Crossref, DataCite, and the other agencies accredited by the International DOI Foundation) are a policy layer; the Handle System is the resolution layer underneath it. Several other identifier schemes are built on the same infrastructure, including RAiD (Research Activity Identifier).
For a research administrator, understanding this distinction matters less as a matter of protocol trivia and more because it clarifies exactly what a “persistent identifier” is actually promising: persistence is a governance and infrastructure commitment layered on top of a resolution mechanism, not a property of the string itself. This guide covers how the Handle System works, who governs it, and what that means in practice for anyone relying on DOI (or handle-based) persistence guarantees. For the DOI-specific policy layer — registration agencies, metadata schemas, ISO 26324 — see DOI Registration Agency: What It Is and Why the DOI System Is Federated. For a side-by-side comparison of the two, see DOI vs Handle.
What the Handle System is
The Handle System is a distributed infrastructure for assigning and resolving persistent digital identifiers, developed in the early-to-mid 1990s by the Corporation for National Research Initiatives (CNRI), a nonprofit research organization based in Reston, Virginia. It was formally documented in IETF RFC 3650 (“Handle System Overview,” 2003) alongside companion RFCs covering its namespace and protocol.
A handle is an identifier string with the same two-part shape as a DOI — a prefix identifying the naming authority, and a suffix chosen by that authority — separated by a slash, e.g. 20.1000/100. DOIs are, structurally, a specific handle namespace: every DOI is a valid handle (with a DOI-specific prefix range and metadata conventions layered on top), resolvable directly at https://hdl.handle.net/ as well as at https://doi.org/. Not every handle is a DOI — an institution can register a handle prefix and mint plain handles for internal use without ever registering as a DOI Registration Agency.
Governance: from CNRI to the DONA Foundation
CNRI operated the Handle System’s central registry as its sole administrator from the system’s creation through 2014. In 2014, CNRI transferred operational governance to the DONA Foundation, a non-profit organization established in Geneva, Switzerland, that now sets policy for the system and credentials the organizations authorized to operate parts of its registry. DONA takes its name from the “Digital Object Naming Authority” concept underlying the broader Handle System / Digital Object Architecture work CNRI originated. CNRI remains involved in the technical maintenance of the Handle.Net reference software, but DONA is the governing body.
How handle resolution actually works
The architecture has three layers:
- Global Handle Registry (GHR). The top-level registry that records which organization has been allotted which handle prefix, and directs a resolution request to the right place to continue. Since December 2015 the GHR has operated on a multi-primary basis — no single organization runs it alone — rather than the single-administrator model CNRI ran before the DONA transfer.
- Multi-Primary Administrators (MPAs). Organizations credentialed directly by DONA to operate GHR services collaboratively and to allot prefixes — to themselves or to third parties (including, historically, the International DOI Foundation for the DOI namespace). This is the redundancy mechanism: because several independent MPAs jointly operate the top level, no single organization’s outage or failure takes down handle resolution globally.
- Local Handle Services (LHS). The organization holding a given prefix — a DOI Registration Agency, a university, an archive — runs (or contracts) the actual resolution service that answers, for a specific handle, with the current location and associated data.
When a client resolves a handle, it queries the GHR layer, which returns the network address of the correct Local Handle Service for that handle’s prefix; the client then queries that service directly for the current record. This two-step, delegated lookup is what makes the identifier durable in the face of URL change: the object’s location can change at any time, because only the LHS record — not the identifier string itself — needs to be updated. The registrant, not the resolution infrastructure, is responsible for actually keeping that record current.
A handle record is not limited to a single URL. It can carry multiple typed data values against one identifier — for example a primary URL alongside an administrative email, a public key, or free-text metadata — and a resolution request can return one, several, or all of them depending on how it’s queried. Resolution itself runs over the Digital Object Identifier Resolution Protocol (an internal Handle System protocol, distinct in name only from “DOI” the identifier scheme), which is independent of DNS: handle resolution does not depend on the domain name system, even though the public-facing resolvers most people use (hdl.handle.net, doi.org) are themselves reached via ordinary DNS-resolved web addresses.
Why this layer matters for anyone relying on DOI persistence
A DOI’s “permanence” promise has two distinct components, and confusing them is a common source of misplaced trust:
- Resolution-layer durability — whether the Handle System infrastructure itself keeps functioning. The multi-primary GHR architecture, and the fact that DONA governs the system independently of any single company or publisher, is what underwrites this. It has survived one full change of central administrator (CNRI to DONA) without breaking existing identifiers.
- Registrant-layer commitment — whether the specific organization that registered a given handle or DOI actually keeps its record’s target current when the underlying object moves. This is a policy commitment enforced by the DOI Registration Agencies (see DOI Registration Agency) and, for plain handles outside the DOI namespace, by whatever prefix holder is responsible for that Local Handle Service. The Handle System provides the mechanism to keep an identifier resolvable through a change of location; it cannot force a negligent or defunct registrant to update the record.
In practice, this means a resolvable DOI or handle reflects the resolution infrastructure working correctly and the registrant maintaining its record — a broken or stale link (“DOI tombstone” pages exist precisely for the retraction/removal case) is almost always a registrant-side maintenance gap, not a Handle System outage. For research administrators evaluating whether to trust a given identifier scheme for long-term citation, grant reporting, or data management plan compliance, the relevant question is less “does this identifier use the Handle System” (most persistent scholarly identifiers, including DOI, effectively do) and more “which organization is contractually and reputationally on the hook for keeping this specific record current.”
Handle System vs. DOI: the practical difference
Because DOI is a namespace within the Handle System rather than a separate technology, the distinction that matters day to day is governance and scope, not resolution mechanics:
| Handle System | DOI | |
|---|---|---|
| What it is | General-purpose identifier resolution infrastructure | A specific, policy-governed namespace built on the Handle System |
| Governs | DONA Foundation (formerly CNRI) | International DOI Foundation; syntax standardized as ISO 26324 |
| Who can register | Any organization that obtains a handle prefix | Only through an accredited DOI Registration Agency (Crossref, DataCite, and others) |
| Metadata requirements | None imposed at the infrastructure level | Registration-Agency-specific schemas (e.g. Crossref’s or DataCite’s metadata schema) |
| Public resolver | https://hdl.handle.net/ |
https://doi.org/ (also resolves via the same underlying infrastructure) |
See the full breakdown, including format examples, at DOI vs Handle — what is the difference?.
Frequently asked questions
Is the Handle System the same organization as the DOI Foundation?
No. The Handle System is governed by the DONA Foundation, which sets policy for handle resolution infrastructure broadly. The International DOI Foundation is a separate body that governs the DOI namespace specifically — a naming policy and Registration Agency system built on top of Handle System resolution. DOI relies on Handle infrastructure but is administered independently of it.
Does every persistent identifier use the Handle System?
No — other major scholarly PID schemes use different infrastructure. ORCID iDs, for instance, resolve through ORCID’s own registry rather than the Handle System, and ARK identifiers (see ARK Identifiers Explained) use a different resolution model built around the identifier’s issuing institution. DOI and RAiD are the most prominent research-administration identifiers built directly on Handle System resolution.
What happens if the organization holding a handle prefix stops maintaining it?
The Handle System’s multi-primary top-level architecture continues functioning independently of any single prefix holder, but an individual Local Handle Service that goes unmaintained can leave handles under its prefix unresolvable or pointing at stale targets. For DOIs specifically, the Registration Agency model exists partly to guard against this: agencies such as Crossref and DataCite commit to maintaining resolution for the DOIs registered through them, including in cases of publisher or repository failure.
Can I look up who holds a given handle prefix?
Handle and DOI prefixes are generally traceable through the resolver itself or the relevant Registration Agency; for DOI prefixes specifically, see How to Find, Cite, and Use a DOI for practical lookup steps.
Related CASRAI resources
- Handle — dictionary definition
- DOI — dictionary definition
- DOI vs Handle — what is the difference?
- DOI Registration Agency: What It Is and Why the DOI System Is Federated
- How to Find, Cite, and Use a DOI
- Identifier Crosswalk: Connecting DOI, ORCID, ROR, and Institutional IDs in Practice
- ARK Identifiers Explained
