Free BlueSky custom handle checker

BlueSky DNS TXT record validator

Check the DNS record BlueSky uses for custom domain handles. The AT Protocol DNS method expects one TXT value at the _atproto subdomain with a did= prefix, then the DID document must also point back to the handle.

Validate a custom handle

This tool checks public DNS only. It does not ask for your BlueSky password, app password, session token, or DNS registrar login.

Domain handleAccount DID

TXT name

_atproto.onyxhq.us

TXT value

did=did:plc:examplecheckthisvalue

What BlueSky expects

The handle should be a DNS-style hostname such as example.com or social.example.com.
The TXT record name should be _atproto plus the full handle.
The TXT value should be did= followed by the account DID.
Only one valid did= record should exist at a time.
BlueSky must also confirm that the DID document claims the same handle.

Common fixes

Use _atproto as the DNS host when the provider appends the domain automatically.
Use _atproto.example.com when the provider expects a fully qualified name.
Remove old did= records before retrying verification.
Wait for DNS propagation or retry from another resolver if the value was just changed.
Keep your ONYX posting calendar paused until the official brand handle resolves correctly.

Official reference

The AT Protocol handle spec defines the DNS TXT method and the HTTPS well-known fallback. Use the spec when debugging custom handle validation.

Open AT Protocol handle spec