IdentityNo sign-in needed

DID finder

Get the DID behind any Bluesky handle.

Type a handle to get its DID, the permanent ID of the account. See how the handle resolves (DNS, HTTPS) and whether the account claims it back.

Examples:bsky.appatproto.com

The DID of this handle

For atproto.com
DID
did:plc:ewvi7nxzyoun6zhxrhs64oiz
Verification
Found by DNSVerified both ways

How the handle resolves

MethodAnswer
DNS TXT record (_atproto)Points to a DIDdid:plc:ewvi7nxzyoun6zhxrhs64oiz
HTTPS file (/.well-known/atproto-did)No answer
Bluesky's AppViewPoints to a DIDdid:plc:ewvi7nxzyoun6zhxrhs64oiz

How it works

Every Bluesky account has a DID, a permanent identifier such as did:plc:… that never changes, and a handle, the name people see. Bots, feeds, labelers and API calls usually need the DID.

A handle points to its DID in one of two ways: a DNS TXT record named _atproto on the domain, or a file at https://<handle>/.well-known/atproto-did. We check both, and ask Bluesky's AppView for a third opinion.

Then we read the DID's document and check that it claims the handle back. Only a handle verified both ways belongs to the account: if the two disagree, the result says so, with how to fix it.

Questions

How do I find my DID on Bluesky?
Type your handle above: the DID shows in large print with a copy button. In the Bluesky app it is also under Settings → Privacy and security → Advanced, but the tool also checks that your handle is set up right.
Does my DID change when I change my handle?
No. The DID stays the same for the life of the account; only the handle it claims changes. That is why bots and apps store the DID, not the handle.
What does "verified both ways" mean?
The handle points to the DID (by DNS or HTTPS) and the DID's document points back to the handle. Bluesky requires both before it shows a handle; otherwise it shows handle.invalid.

Documentation

Handle finder (DID to handle)

Find the handle behind a DID.

Also useful:Bluesky whoisHandle availability checker

See all the tools