IdentityNo sign-in needed

Custom domain handle checker

Find out why your handle is invalid, and how to fix it.

Type your domain to check its DNS record, its well-known file and your DID document. See in plain words what is wrong, and copy the exact record to add.

Your current handle or your DID: the checker then tells you whether the domain points to it, and fills in the record to add.

DNS can take up to an hour to update. This tool asks fresh every time.

Examples:bsky.appatproto.com

Your handle is set up correctly

Checked: bsky.app.
  1. Handle syntax: Passed

    bsky.app is a valid handle.

  2. DNS TXT record: Passed

    Found: _atproto.bsky.app points to did:plc:z72i7hdynmk6r22z27h6tvur.

    • did=did:plc:z72i7hdynmk6r22z27h6tvur
  3. HTTPS file: Passed

    No usable file. That is fine: your DNS record does the job.

  4. DNS and HTTPS agree: Not checked

    Only one method is set up: nothing to compare.

  5. Your DID document: Passed

    Your DID document claims bsky.app: the link works both ways.

  6. The account you expect: Not checked

    No account given: the domain points to did:plc:z72i7hdynmk6r22z27h6tvur.

  7. What Bluesky shows: Passed

    Bluesky shows bsky.app: all good.

Not sure a domain is the right choice? Compare the three ways to get a handle.

How it works

A domain handle works when Bluesky can prove two things: the domain points to your account, and your account points back to the domain. The domain says it with a TXT record at _atproto followed by the handle (for alice.example.com: _atproto.alice.example.com) whose value is did= followed by your DID, or with a file at /.well-known/atproto-did that holds only your DID.

The checker runs each step Bluesky runs: the handle’s syntax, the TXT record (and the usual copy-paste mistakes, like a record on the wrong name), the file, whether both agree, whether your DID document claims the domain, and what Bluesky shows right now.

DNS changes can take up to an hour to reach everyone. The checker asks fresh every time, so run it again after a change. It only reads public DNS, your domain’s web server and public Bluesky data, and stores nothing.

Questions

Why does Bluesky say my handle is invalid?
Most often the TXT record is on the wrong name (the DNS panel added your domain a second time), the value misses the did= prefix, two records name different DIDs, or Bluesky has not switched your handle yet. The checker tells you which one it is.
What do I type as the host or name of the TXT record?
The part of _atproto.yourhandle before your DNS zone, since panels add the zone on their own: _atproto for a handle that is the domain itself (example.com), _atproto.alice for alice.example.com in the zone example.com. The checker shows the exact host. The value is did= followed by your DID, with no quotes and no spaces.
My record is right, but the handle still shows as invalid. What now?
Bluesky checks again when you set your handle. In the app, open Settings, Account, Handle, choose “I have my own domain” and verify it again. It can take a few minutes to show everywhere.
Is there an easier way for a bot?
Yes: a name.bluesky.bot handle needs no domain and no DNS. Bluesky.bot serves the file Bluesky checks and switches the handle for you.

Documentation

Handle availability checker

Is your name free on Bluesky?

Also useful:Bluesky whois

See all the tools