Free BlueSky identity helper

BlueSky DID and PLC directory lookup helper

Normalize a BlueSky handle, check a DID string, and open the public resolver links that help technical teams separate a mutable handle from the stable account identity used by AT Protocol.

Check a handle or DID

This helper validates local syntax and builds public lookup links. It does not request your password, app password, session token, or private account data.

BlueSky handleDID string

Handle result

Normalized handle: bsky.app

This matches the AT Protocol handle syntax shape.

DID result

Method: plc

This DID uses an AT Protocol supported method.

Public lookup links

Resolve handle to DID Open PLC directory document

Why scheduling tools care

BlueSky handles can change, but DIDs are the stable account identifiers. ONYX scheduling should stay mapped to the account identity you approved, even when the public handle changes later.

For rebrands and DNS changes, use the engineering guide for managing handle propagation delays and clearing localized directory network caches.

For brand-history audits, read the guide on auditing append-only cryptographic transaction chains inside public PLC directory logs.

For repo integrity checks, use the verifier for verifying Content Identifiers and validating cryptographic record signatures inside block commits.

What to check before connecting tools

The handle resolves to the DID you expect.
The DID document points back to the current handle.
The PDS service endpoint exists in the DID document.
The account is connected with a revocable app password.
Scheduled posts are approved before any publishing action runs.

Official references

AT Protocol DID spec AT Protocol handle spec DID PLC directory

Connect after identity checks

Once the handle, DID, and app password are clear, build a reviewed ONYX queue around that account identity.

Start Free