“Ghost Ban” commonly describes replies that exist for the author but are difficult to find from outside the account. BanScope checks the actual reply IDs against direct access, reply search and conversation search instead of assuming absence from one thread view is proof.
“Ghost Ban” commonly describes replies that exist for the author but are difficult to find from outside the account. BanScope checks the actual reply IDs against direct access, reply search and conversation search instead of assuming absence from one thread view is proof.
Last reviewed: 2026-09-22Large conversations may be incomplete, reply permissions can affect visibility, and a thread view may not load every reply. A reliable diagnostic separates direct reply existence from whether the same reply ID appears in search or conversation queries.
BanScope samples up to three recent replies, checks whether their status URLs resolve publicly, searches `from:username filter:replies`, and when a parent post is known also searches `conversation_id:parent from:username`. The Precise Reply Check can test one supplied reply URL with higher specificity.
See the BanScope methodology →A missing reply ID can be an important warning, but it can also be caused by conversation limits or incomplete retrieval. BanScope reports uncertainty when evidence is insufficient instead of claiming access to an internal ghost-ban flag.
Use only a public username. No login or password required.
BanScope does not turn a third-party guess into a verdict. These platform documents describe search, recommendation and public-visibility behavior relevant to the diagnostic.
See validation and update history for this methodology →
