Universal Resolver
Community DID Infrastructure
A Successful Incubation
As of October 14, 2026, The Decentralized Identity Foundation is no longer hosting a "community staging server" for the Universal Resolver. The complexity of hosting and administering it as a public resource has grown over the years, and the number of production-grade implementations of the Universal Resolver specification (with free tiers) have largely obviated the need for DIF to "seed" the market, which is growing into maturity.
Developers who were using DIF's community resolver (which was powered, all along, by GoDiddy's staging backend)
are encouraged to consider using one of the two resolvers listed below for experimentation and research, and to
consider DIF-affiliated commercial options for production infrastructural needs. Both deployments are
deployed and funded by DIF members, who maintain the respective reference implementations they are based on through
DIF, including change requests, bug fixes, and ongoing review of new drivers, whether dockerized, NPM-packaged, or
both. Some of these drivers, like those for
did:ethr and
did:webvh
are, in turn, also DIF work items, and thus good examples to analyze if you are planning your own driver contribution.
In historical order, the main DIF-member deployments are:
GoDiddy, by DanubeTech
Productionized reference implementation of the original Universal Resolver form-factor.
GoDiddy's production front-end, which continues to run DanubeTech's foundational reference implementation of the specification they donated to DIF and managed here. It is comprised of a workhorse Java router and docker containers per method to support the widest possible range of resolution designs.
ThisDID, by GoPlausible
Edge-worker-optimized and proxy-fallback wrapper around DIF's NPM-based resolver engine
ThisDID.com, is a more recent re-architecting of the Veramo-project-maintained TypeScript/NPM reference implementation. It uses an edge-worker deployment to route and proxy resolution to optimize for low latency and operational cost for methods which have been packaged as NPM packages, and has a "fallback" to proxied resolution everywhere else, load-balancing (and ranking) where multiple backends support these non-NPM resolution drivers.