Bsky tools AIO

Custom Domain Verification

Check the verification status of your custom Bluesky handle via DNS or HTTPS methods

About Custom Domain Verification

AT Protocol supports two methods for verifying custom domain handles: DNS and HTTP(S). These methods prove that you control the domain you're using as your handle.

DNS Verification

The DNS method uses a TXT record at _atproto.yourdomain.comcontaining your DID:

did=did:plc:your-did-here

DNS verification is the preferred method as it's more reliable and doesn't require web server configuration. This tool queries both Google DNS and Cloudflare DNS-over-HTTPS APIs simultaneously and shows results from each provider separately, helping you verify that your records are properly propagated across different DNS resolvers.

Note: Subdomains are fully supported (e.g., abu.sayed.swifties.social). The TXT record should be at _atproto.abu.sayed.swifties.social.

HTTP Verification

The HTTP method serves your DID at the well-known endpoint:

https://yourdomain.com/.well-known/atproto-did

The file should contain only your DID with no additional formatting, served with HTTPS.

Verification Priority

If both DNS and HTTP verification pass, DNS takes priority. If one method fails, the other can still successfully verify your handle. This provides redundancy and flexibility in how you configure your custom domain.

Common Issues

DNS propagation delay

DNS changes can take up to 48 hours to propagate globally. If one DNS provider shows your record but another doesn't, this indicates propagation is still in progress. Both Google DNS and Cloudflare DNS are queried to show you the current state across different resolvers.

Subdomain configuration

For subdomains like abu.sayed.swifties.social, ensure the TXT record is at _atproto.abu.sayed.swifties.social, not at the root domain. Each subdomain needs its own _atproto TXT record.

HTTP redirects

Too many redirects can cause HTTP verification to fail. Ensure the well-known endpoint is directly accessible without multiple redirects.

HTTPS requirement

HTTP verification requires HTTPS (not HTTP). Make sure your domain has a valid SSL/TLS certificate and the well-known file is served over HTTPS.

Incorrect DID format

Ensure your DID follows the correct format: did:plc:... or did:web:...

How It Works

  1. 1Enter your custom handle or domain (with or without @), including subdomains like abu.sayed.swifties.social
  2. 2The tool queries both Google DNS and Cloudflare DNS-over-HTTPS APIs in parallel to check TXT records at _atproto.yourdomain
  3. 3Results from both DNS providers are displayed separately, showing which resolver returns which value
  4. 4Simultaneously, it attempts to fetch /.well-known/atproto-did via HTTPS
  5. 5Results show which verification method(s) passed and display your DID with a copy button
  6. 6Detailed status checks help diagnose any configuration issues with specific error messages from each provider