How to check Bluesky follow backs
Learn to compare current Bluesky follow lists, interpret mutual and unknown relationships, and avoid mistaking a partial snapshot for unfollower history.
Check current follow backs, step by step
Open the follow-back checker, enter a public Bluesky handle, DID or profile link, and run the check. You do not need to connect your account or provide an app password. Start with a small account when learning the interface: it is easier to inspect coverage and understand each group.
Read the two coverage cards before interpreting the names. Each list examines at most 500 entries. “Complete at capture” requires the list to end, contain no omitted or duplicate accounts, and match the profile’s reported count. A larger account can therefore have a useful result without a complete comparison.
Understand the four groups
An observed mutual account appears in both lists. “Following you do not observe back” contains accounts in the following list that are absent from a complete follower list. “Followers you do not follow back” uses the reverse comparison. If the opposite list is incomplete, the relationship goes into “unknown” instead.
For example, finding 60 followers and 80 followed accounts is insufficient to conclude that 20 people do not follow back: the two sets must actually be compared. The checker compares DIDs rather than display names or handles. Each group displays its observed count and previews its first 100 accounts.
Why a list may be partial
Hidden profiles, invalid entries, repeated cursors, upstream failures, the 500-entry cap or the shared eight-second list-reading budget can limit coverage. Public counts and relationships can also change during the check; these requests do not form an atomic database snapshot. A conservative “unknown” result is preferable to an unsupported negative relationship.
Do not try to fix a partial result by repeatedly submitting it. Successful answers share a five-minute cache. For a personal list backup, use the separately bounded follower export and read any partial-export comment in the downloaded CSV.
This is not an unfollower history
The checker stores no historical snapshots and receives no follow dates. It cannot identify who unfollowed you yesterday, explain someone’s intentions, or establish whether a relationship used to be mutual. Keep comparisons respectful: a current non-reciprocal follow does not imply a technical problem or an obligation to follow.
Use the API or MCP
The same bounded comparison is available through the tools API at GET /api/v1/tools/follow-back-checker?q=HANDLE and the MCP tool check_follow_back. The structured answer includes capture time, coverage for both lists and the groups. Unknown relationships remain unknown in every interface. A call costs six quota units; the page also uses per-IP and site-wide fan-out limits.
Privacy and next steps
All operations are public reads. The tool cannot follow, unfollow, block or post, and hidden identities are discarded before results are returned. Inputs and lists are not persisted as a relationship database; successful results live in the short shared cache. See the privacy policy for platform logging and cookie details. Use this result to understand a current public list, not to infer historical behaviour.