BanScope Methodology

This page documents what BanScope measures automatically, what it cannot observe, and why an unavailable signal is not treated as proof of a restriction. BanScope measures public visibility from outside the account; it does not claim access to internal X or Threads enforcement flags.

No loginNo passwordPublic data onlyMulti-source / beta

No login · No password · Results in seconds

No password or login required. Usernames are not stored in server analytics. Recent check history can be kept only in this browser on this device.

What you get

100 Visibility score✓ Profile✓ Search✓ Posts✓ Replies

X and Threads do not publish an official shadowban flag. BanScope cross-checks profile, suggestions, search, posts and replies across multiple public sources.

BANSCOPE METHODOLOGY

BanScope Methodology

Last reviewed: September 22, 2026

Core principle

BanScope is an outside-in public visibility diagnostic. It separates direct observations, ID matching and secondary index evidence; a missing signal is not automatically converted into a restriction verdict, and insufficient evidence remains Unknown / re-check.

XDirect observation

Public profile

What BanScope observes: BanScope resolves the profile through multiple public-access paths and only uses a secondary web-index signal when profile or recent-post evidence is otherwise unavailable.
What BanScope does not observe: It does not observe X internal account-enforcement labels, search rank or For You distribution volume.
Official basis: X Help: Public and protected posts
Last reviewed: September 22, 2026

Confidence: High / Medium

XDirect observation

Search suggestion

What BanScope observes: The checker looks for the target handle in an available typeahead response. If the public profile exists but a valid suggestion response omits the handle, the result is a warning rather than a claim about every viewer’s personalized suggestions.
What BanScope does not observe: It does not observe every viewer’s personalized suggestions, internal typeahead scores or the reason for a suggestion rank.
Official basis: X Help: Search recommendations
Last reviewed: September 22, 2026

Confidence: High / Medium

XPost-ID matching

Search visibility

What BanScope observes: Recent profile post IDs are compared with IDs from `from:username -filter:replies` and `from:username` Latest-search responses. A match is strong evidence of visibility; valid searches with no match produce a warning whose confidence depends on the available evidence.
What BanScope does not observe: It does not observe an internal search-restriction flag, exclusion reason codes, or every region/session’s search output.
Official basis: X Help: Search recommendations · X Help: Search rules and restrictions
Last reviewed: September 22, 2026

Confidence: High / Medium / Low

XDirect observation

Post visibility

What BanScope observes: Recent public posts are resolved from the profile feed. Protected accounts are not treated as a failure. An external-index fallback can provide medium-confidence evidence when the primary public feed is unavailable.
What BanScope does not observe: It does not observe For You ranking, impression volume or private health scores.
Official basis: X Help: Public and protected posts · X Help: Search rules and restrictions
Last reviewed: September 22, 2026

Confidence: High / Medium

XReply-ID matching

Reply visibility

What BanScope observes: Up to three recent replies are checked for direct public resolution, reply search and, where possible, conversation search. Precise Reply Check tests one supplied URL with a larger search window. Exact thread ranking is not measured.
What BanScope does not observe: It does not observe an exact reply rank, private conversation scores or the reason a reply was downranked.
Official basis: X Help: Conversations recommendations · X Help: Search rules and restrictions
Last reviewed: September 22, 2026

Confidence: High / Medium / Low

ThreadsDirect observation

Public profile

What BanScope observes: BanScope checks the public Threads profile through multiple public-access conditions, can compare an alternate public domain, and uses an external-index signal only as a secondary fallback.
What BanScope does not observe: It does not observe Meta recommendation eligibility, non-follower distribution volume or private account-status labels.
Official basis: Meta: Threads product and search
Last reviewed: September 22, 2026

Confidence: High / Medium

ThreadsPublic search observation

Search visibility

What BanScope observes: The checker queries accessible Threads search output for the username and looks for the target handle. It does not reproduce every viewer’s personalized search results or rank every individual post.
What BanScope does not observe: It does not reproduce every viewer’s personalized search ranking or each post’s keyword rank.
Official basis: Meta: Threads product and search
Last reviewed: September 22, 2026

Confidence: Medium

ThreadsPublic HTML observation

Post visibility

What BanScope observes: BanScope looks for public Threads post URLs belonging to the target account in the public profile response, with a secondary external-index fallback when needed.
What BanScope does not observe: It does not directly observe whether a public post is recommendation-eligible or how much recommendation distribution it receives across Meta apps.
Official basis: Meta: Recommendation Guidelines · Meta: Threads Insights and discovery
Last reviewed: September 22, 2026

Confidence: Medium

ThreadsNot automated

Suggestions & reply ranking

What BanScope observes: BanScope does not currently claim a reliable automated Threads suggestion or reply-ranking signal. Missing evidence is returned as unknown rather than converted into a fake restriction verdict.
What BanScope does not observe: BanScope does not currently automate Threads suggestions, reply rank or recommendation eligibility.
Official basis: Meta: Recommendation Guidelines · Meta: Threads Insights and discovery
Last reviewed: September 22, 2026

Confidence: Unknown

Scoring and overall label

The overall label is “warning” if any measured check warns, “normal trend” when at least two checks pass and none warn, and “re-check” otherwise. Safety Score is not a probability of being banned. Unknown checks receive a neutral midpoint while Coverage and Reliability separately show how much evidence was actually measured. X weights are profile 15, suggestion 15, search 30, post 20 and reply 20; Threads weights are profile 20, suggestion 10, search 30, post 25 and reply 15.

Short result cache

Identical checks use a short cache of up to 180 seconds to avoid excessive requests to external services. For a meaningful comparison, wait beyond that short window and allow for search/reply state to change.

What BanScope can never observe directly

An internal official “shadowban=true” flag on X or Threads
Private moderation scores or enforcement reason codes
Identical search output for every country, login state or viewer
Threads recommendation eligibility itself
The intent behind X reply-ranking decisions

Official references

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.

X Help: Search troubleshooting X Help: Search rules and restrictions X Help: Search recommendations X Help: Conversations recommendations Meta: Recommendation Guidelines Meta: Threads Insights and discovery

Public validation log

See dated platform validation, official references and major methodology changes.

See validation and update history for this methodology → →

Related BanScope guides

Free X Shadowban Checker Free Threads Shadowban Checker What Is a X Shadowban?What Is a Threads Shadowban?BanScope Validation Log & Updates What Causes an X Shadowban?How to Recover From an X Shadowban What Is an X Search Ban?What Is an X Search Suggestion Ban?