Start with the handle, not the badge
When an account claims to represent a person or organization, the first thing to read is the handle itself. On Bluesky, a handle can be a domain name the account controls, which is why a handle ending in an organization’s own domain is a stronger signal than a free-form name. That does not make the account official on its own: a domain handle shows control of that domain at the time it was set, not that every post is authorized.
Do not confuse the handle with the badge. They answer different questions. The handle asks “what name is this account using, and does it point at a domain?” The badge asks “who, if anyone, reviewed this account?” Treat them as separate columns in your notes, because they can disagree.
Step 1: Read the handle character by character
Copy the handle into a plain text note and compare it with the organization’s published handle. Watch for lookalike substitutions: doubled letters, hyphens where the real handle has none, a different top-level domain, or an extra word such as “official” or “support.” These are ordinary impersonation patterns you can check yourself without any tool.
If the handle is domain-based, check whether the domain is the organization’s real domain or a near-miss. A handle that reads like a brand but sits on an unrelated domain is a warning sign, not a neutral detail.
Step 2: Inspect the badge and its issuer
A verification badge is not a single universal seal. Bluesky distinguishes domain-based handles from verification badges.
Bluesky distinguishes domain-based handles from verification badges. Source
That distinction matters because a badge can come from an organization rather than from the platform itself. Tapping an account verification badge shows which organization granted verification; selected Trusted Verifiers can issue badges that Bluesky reviews.
Tapping an account verification badge shows which organization granted verification; selected Trusted Verifiers can issue badges that Bluesky reviews. Source
So the useful question is not “does this account have a badge?” but “which organization issued this badge, and is that issuer the organization the account claims to represent?” A badge from a newsroom, a community group or another verifier is not the same as a badge from the organization named in the profile.
Step 3: Compare the profile’s own claims
Read the biography and links as claims to be checked, not facts. A profile can display a logo, a display name and a biography that all match an organization while the handle and badge point somewhere else. Ask three questions in order:
- Does the handle match the organization’s published handle or its real domain?
- Does the badge issuer match the organization, or is it an unrelated verifier?
- Do the profile’s links lead to the organization’s known properties rather than to lookalikes?
If the answers conflict, stop and treat the account as unverified until you can confirm it through a channel the organization publishes itself.
Decision table: when to trust, pause or stop
| Handle signal | Badge signal | What it means | Action |
|---|---|---|---|
| Exact match to the organization’s published handle or real domain | Badge issued by the organization or a verifier you can identify and connect to it | Signals agree | Still confirm through the organization’s own published channels before acting on requests |
| Exact match | No badge, or badge from an unrelated issuer | Handle looks right but review is missing or mismatched | Pause; do not treat as official until confirmed elsewhere |
| Near-miss or unrelated domain | Badge present | Badge may be real but attached to the wrong account | Stop; a badge does not repair a mismatched handle |
| Near-miss or unrelated domain | No badge, or badge from an unrelated issuer | Multiple signals point away from the organization | Stop; treat as a likely impersonation lead |
| Any handle | Badge issuer cannot be determined | The key signal is missing | Stop; do not infer verification from the badge’s appearance |
This table is a stopping rule, not a scoring system. One clean signal does not cancel a conflicting one.
Common mistakes
Treating the badge as a universal trust mark. A badge records who reviewed the account, not whether every statement, offer or transaction is legitimate. A verified account can still be compromised, and a badge does not certify the content of individual posts.
Reading the display name instead of the handle. Display names are free text. The handle is the identifier you should compare, character by character.
Assuming a domain handle means the organization runs the account. A domain handle is a signal about domain control, not a statement about who posts or what they are authorized to say.
Skipping the issuer. If you cannot say which organization granted the badge, you have not checked the badge. The issuer is the point of the check.
Stopping at one platform. A matching photo, biography and handle on another network is a lead, not proof that the accounts belong to the same person or organization. Public identifiers can be copied, and matching them cannot independently prove identity.
Confusing this check with handle setup. This guide is about assessing an account you are looking at. If you want to configure your own domain handle and public links, the separate guide on setting a Bluesky domain handle and updating your public links covers that task.
A self-review checklist before you act
Run this list before you reply, share, pay or hand over information to an account that claims to be official:
- I copied the handle and compared it character by character with the organization’s published handle.
- I identified the badge issuer, or I recorded that I could not.
- I checked whether the issuer is the organization named in the profile or a verifier I can connect to it.
- I noted any conflict between handle and badge instead of averaging the signals.
- I confirmed the account through a channel the organization publishes itself, not through the profile’s own links.
- I remembered that a badge does not verify every statement or transaction.
If any line is unchecked, the honest status is “unverified.” That is a useful answer, not a failure.
Protecting your own footprint
The same signals you use to judge others apply to your own accounts. Keep your public handle consistent with the identity you actually control, and remember that a badge reflects a review by a named issuer, not a blanket endorsement. When you assess someone else, write down what you checked and when, so a later change in the profile does not rewrite your notes.
If you want to review your own known public handles across networks, TraceSeek is a username search app that checks 3,000+ platforms in a stated 20-30 seconds, with a free first scan. It reports public matches; it does not change platform settings, guarantee a match or verify anyone’s identity. Treat every result as a lead and confirm it through the account owner’s own published channels. Our methodology page explains how we frame these limits.
Key facts
- Bluesky distinguishes domain-based handles from verification badges.
- Tapping an account verification badge shows which organization granted verification, and selected Trusted Verifiers can issue badges that Bluesky reviews.
- TraceSeek covers 3,000+ platforms and states a scan time of 20-30 seconds with a free first scan.
- Public username matches are leads, not proof that accounts belong to the same person.