05 — Resolver
The resolver is the bridge between a DID string and a DID Document. Each method has a different resolution path — DNS for did:web, Hedera Mirror Node for did:hedera, local cryptography for did:key, Bitcoin for did:ion. This tool resolves DIDs in real time via a Cloudflare Worker.
A DID resolution request fans out to different backends depending on the method. Hover any path to see latency and protocol details.
Enter a DID to resolve it. did:web resolution is live — other methods are simulated with production-accurate document structures, ready for live upgrade.
Live resolution for did:web, did:key, did:pkh. Simulated for did:hedera, did:ion, did:ethr — ready for Worker upgrade.
Enter a DID string or select an example above to resolve and inspect its DID Document
The W3C DID Resolution specification defines a standard interface: given a DID string, return a DID Document and resolution metadata. The resolver is method-agnostic — it detects the method from the DID prefix and routes to the appropriate backend.
Cloudflare Workers are ideal for this: edge-deployed, sub-50ms cold start, native fetch API for did:web resolution, and the ability to call external APIs for other methods. The result is a universal DID resolver that runs at the edge.