runs-at.dev
runs-at.dev // documentation

Docs / Guides / Bluesky handle

Bluesky handle

you.runs-at.dev as your verified Bluesky handle, via DNS, no app hosting involved.

What you'll end up with

Bluesky can verify a custom domain as your handle by checking for a TXT record at _atproto.you.runs-at.dev containing your account's DID. Once verified, you.runs-at.dev shows on your profile in place of a *.bsky.social handle.

The record

domains/you.json

"subdomains": {
  "_atproto": { "TXT": ["did=did:plc:abc123"] }
}

Replace did:plc:abc123 with your account's actual DID, found in the Bluesky app under Settings → Advanced → your DID.

Steps

Note

Two ways to apply this. The quickest is runs-at.dev/manage: sign in, pick the record type, paste the value, save. It writes the same commit to the registry and DNS follows within seconds. The steps below do it by pull request instead, which is what you want if you would rather review the change first. Either way handles subdomains entries.

  1. Fork the registry and edit domains/you.json to the record above.
  2. Open a pull request. Once merged, the TXT record is synced to DNS automatically.
  3. In the Bluesky app: Settings → Account → Handle → I have my own domain → enter you.runs-at.dev → No DNS Panel → Verify DNS Record.

How to tell it worked

Bluesky confirms the handle change immediately once it can resolve the TXT record and the DID matches. Your profile then shows you.runs-at.dev as your handle.