A Bluesky handle can be any domain you control. Instead of @yourname.bsky.social you become @yourdomain.dev, and anyone can check that the account really belongs to whoever runs that site.

The usual instructions say to add a TXT record to your DNS. I didn't have convenient access to the DNS panel for my domain, but the site itself is a static site on GitHub Pages, deployed from a repository I control. That turns out to be enough: Bluesky also accepts verification through a file served over HTTPS.

Here is what I did for my own handle, @vincenzoallocca.dev.

1. Find your DID

Every Bluesky account has a permanent identifier, the DID, that looks like did:plc: followed by a string of letters and numbers. The handle is just a human-friendly name that points to it.

In the app: Settings → Account → Handle → I have my own domain, type your domain and switch to the No DNS panel tab. Bluesky shows the exact file path and the DID it expects. You can also look it up from a terminal:

curl "https://public.api.bsky.app/xrpc/app.bsky.actor.getProfile?actor=yourname.bsky.social" 

2. Add the file to your repository

The file must live at /.well-known/atproto-did and contain only the DID:

mkdir -p .well-known printf 'did:plc:xxxxxxxxxxxxxxxxxxxxxxxx' > .well-known/atproto-did 

I used printf instead of echo so the file has no trailing newline. The verification worked like that; I didn't test a version with a newline.

3. Make sure GitHub Pages actually serves it

This is the step that trips people up. If your Pages site is built with Jekyll (the default for branch deployments), Jekyll skips files and folders whose name starts with a dot, so .well-known/ never makes it into the published site.

Two ways around it:

  • add an empty .nojekyll file at the root of the published branch, which disables Jekyll entirely (my site already had one, because it is plain HTML);
  • or, if you need Jekyll, include the folder explicitly in _config.yml:
include: [".well-known"] 

If you deploy with a GitHub Actions workflow that uploads a build folder, just check that the folder ends up in the artifact.

Commit, push, wait for the deployment, then check:

curl -i https://yourdomain.dev/.well-known/atproto-did 

You want a 200 and the DID as the body. GitHub Pages serves the file as application/octet-stream because it has no extension, and Bluesky accepted it anyway.

4. Verify and switch

Back in the app, press Verify text file. When it says the domain is verified, press Update to yourdomain.dev. Your old .bsky.social handle stays reserved for your account, so you can switch back if you ever need to.

To confirm from outside the app:

curl "https://public.api.bsky.app/xrpc/com.atproto.identity.resolveHandle?handle=yourdomain.dev" 

It should return your DID.

Keep the file

Leave /.well-known/atproto-did in the repository. If it disappears, the handle can no longer be verified and the app flags it as invalid.

I also linked the profile from my site's structured data (sameAs) and with <link rel="me">, so the site and the account point at each other.

I'm Vincenzo Allocca, a software developer and Computer Engineering student in Naples. The site where I set this up is vincenzoallocca.dev.