Bluesky DID Lookup: Handles, DIDs, and Safe Profile Links
Resolve a Bluesky handle to its permanent DID, understand AT Protocol identity, and share a profile link that survives handle changes.
A handle is an address, not the identity
A Bluesky handle is readable and convenient. A decentralized identifier, or DID, is the durable identity underneath it.
That distinction matters when a profile URL is indexed, added to a bio, or used as evidence. Handles can move between accounts. A DID continues to represent the same actor.
bluesky.dawg.bot accepts either form:
bluesky.dawg.bot/bsky.appbluesky.dawg.bot/did:plc:z72i7hdynmk6r22z27h6tvurbluesky.dawg.bot/profile/did:plc:z72i7hdynmk6r22z27h6tvur
The first two resolve to the canonical third form after the public AppView confirms the account.
What the lookup records
Dawg collects the public actor profile and separately captures optional public surfaces:
- Handle, DID, display name, description, avatar, banner, and verification
- Follower, following, and post counts
- Recent public posts and engagement counts
- Public follower and following samples
- Custom feeds, lists, and starter packs created by the actor
The actor profile is required. Optional collections are isolated, so a temporary feed or graph outage cannot discard a valid identity result.
Every successful bundle is stored as a durable provider snapshot before normalized fields, graph edges, and resource entities are applied. The public frontend reads Dawg's stored projection; it does not call Bluesky directly.
Why old handle routes stay bound
The first confirmed handle lookup creates a durable route binding to the actor's DID. Dawg never silently repoints that historical URL to another account.
This makes an old indexed link, forum post, or audit record keep its original meaning after a rename or handle reuse. For records that must survive any handle change, use:
bluesky.dawg.bot/profile/<did>
Social links are not ownership proof
Public follows, mentions, and profile links enrich the identity graph. They do not merge Dawg accounts or prove that one person controls multiple profiles.
Ownership remains a separate explicit proof. This keeps the graph useful without turning a public relationship into an impersonation path.
Frequently Asked Questions
How do I find a Bluesky DID?
Enter the account's current handle on bluesky.dawg.bot. The resolver confirms the actor through Bluesky's public AppView and redirects to /profile/<did>.
Can a Bluesky DID change?
A DID is the durable account identifier. A user can change handles or display names without changing the identity anchor.
Does bluesky.dawg.bot require a login?
No. Public lookups use anonymous AT Protocol AppView endpoints. A Dawg account is only needed for owner controls.
Try it on bluesky.dawg.bot
Paste a Bluesky handle or DID and see the public profile immediately.