IdentityNo sign-in needed

PLC history viewer

Every handle change, server move and key change of an account.

Paste a handle or a DID to read the public history of a Bluesky identity in the PLC directory: when it was created, each handle change, each move to another server and each key change, in plain words.

Examples:bsky.appdid:plc:z72i7hdynmk6r22z27h6tvur

Identity history

did:plc:z72i7hdynmk6r22z27h6tvur

Created on
Operations
4
Handle in the PLC document
bsky.appVerified both ways: the handle points back to this DID.
Last change
Status
Active
Nullified operations
0

Timeline

Previous handles are hidden: open “Show the handles” on a step to see them. The PLC directory publishes them.

  1. Operation

    CIDbafyreifn4pk…nyxm3q

    • ServerMoved to another server (PDS)

      Before: bsky.socialAfter: puffball.us-east.host.bsky.network

    • Signing keySigning key changed

      Before: did:key:zQ3shXjHeiBuRCKmM36cuYnm7YEMzhGnCmCyW92sRJ9pribSFAfter: did:key:zQ3shQo6TF2moaqMTrUZEM1jeuYRQXeHEx4evX9751y2qPqRA

  2. Operation

    CIDbafyreiexwzi…6tan3a

    • No changeNo visible change

  3. Operation

    CIDbafyreihmuvr…nunjoq

    • HandleHandle changed

      Show the handles

      Before: bluesky-team.bsky.socialAfter: bsky.app

  4. Operation

    CIDbafyreigp6sh…7bw6zm

    • CreatedIdentity created

    • HandleHandle set

      Show the handles

      Before: —After: bluesky-team.bsky.social

    • ServerServer (PDS) set

      Before: —After: bsky.social

    • Signing keySigning key set

    • Rotation keys2 rotation keys set

      Added:
      • did:key:zQ3shhCGUqDKjStzuDxPkTxN6ujddP4RkEKJJouJGRRkaLGbg
      • did:key:zQ3shpKnbdPx3g3CmPf5cRVTPe1HtSwVn5ish3wSnDPQCbLJK

How it works

Almost every Bluesky account has a did:plc identity. The PLC directory, a public registry, keeps every change ever made to it as a signed operation: the handle, the server that hosts the account (its PDS) and the keys allowed to sign posts or change the identity.

The viewer reads that log and compares each operation with the previous one, so you see what changed in plain words: a new handle, a move to another server, a new key. Operations overridden during the 72-hour recovery window are kept and marked as nullified.

Previous handles stay hidden until you ask for them: people change names for personal reasons. Nothing you type is stored; the lookup reads the PLC directory, the Bluesky API when you give a handle, and the DNS and server of the document's handle to check it both ways.

Questions

How do I see the handle history of a Bluesky account?
Paste the account's handle or DID above. Each handle change in the PLC directory shows up as a step of the timeline, with its date; open “Show the handles” on a step to see the old and the new handle.
Can this tell me if my account was taken over?
It shows every key change and every server move, with the date. A change of rotation keys and a server move on the same day is what moving your account to another server looks like: if you did not do it, contact the host of your server (PDS) right away.
Why is there no history for my did:web?
A did:web identity has no central registry: its document lives on its own domain, which keeps no public history. Only did:plc identities, the vast majority on Bluesky, have a log in the PLC directory.

Documentation

Account age checker

See when any account joined Bluesky.

Also useful:Handle finder (DID to handle)Bluesky whois

See all the tools