What Am I Shadownbanned Actually Tells You About X Reach

A sudden drop in reach is difficult to diagnose on X. Your posts are still published, your account is still visible to you, and there may be no message explaining why fewer people seem to find them. The usual response is to test the account while logged out, search for possible causes, and hope someone has documented the same behaviour.

Am I Shadownbanned is a free web checker for that narrow problem. It takes an X handle and runs nine checks that are intended to identify account restrictions and forms of post suppression. The useful question is not whether it promises to reveal a secret state. It is what the results can actually tell you, and where they stop.

It turns a vague suspicion into separate checks

The service does not present the result as one overall visibility score. Instead, it reports nine yes or no signals: whether the account is unregistered, suspended, locked, not graduated, marked sensitive, withheld, subject to a search suggestion ban, affected by a search ban, or affected by a ghost ban.

That distinction matters because “shadowbanned” is often used as a catch-all term. An account that cannot appear in search is dealing with a different problem from one whose replies are harder to discover. Separating the checks gives the reader a more specific starting point than a single pass or fail label.

The product says each signal uses the same direction: yes means the problem was detected. Red indicates a hit, green indicates a clean result, and grey means the check could not be measured. That grey state is one of the more responsible details in the design. A failed measurement is not the same as evidence that everything is fine.

The page itself is deliberately spare. There is a field for an X handle and a check action. The developer says the service uses public information, does not require an X login, and does not ask for OAuth access, an extension, or an account of its own. It also says it is not affiliated with X Corp and does not change anything on the account.

The more ambitious part is the explanation

A basic X shadowban checker would be useful only if it gave a reasonably clear indication of what to investigate next. Am I Shadownbanned claims to go further by quoting the relevant X policy line, identifying the post associated with the issue, and showing the day the account’s reach fell.

Those details aim to answer the questions that matter after a visibility drop. Which rule might be involved? Was there a particular post worth reviewing? When did the change appear to begin? The product is therefore positioned less as a permanent account monitor and more as a diagnostic snapshot for someone who has noticed a sharp change.

There is an important qualification here. These are the developer’s stated capabilities, not an independent confirmation that X’s internal ranking or enforcement systems can be fully reconstructed from public data. A policy reference can provide context, but it does not by itself establish why a post reached fewer people. The same applies to associating a specific date with a drop in reach.

What it cannot tell you

The service is clearer about its boundaries than many tools in this category. It does not provide a recovery-time prediction. It does not offer a visibility score from 0 to 100 or a trend graph. The developer’s reasoning is that it can measure the current set of checks, but cannot honestly turn that limited view into a forecast or historical curve.

That makes the tool unsuitable for ongoing analytics. If you want to compare reach across weeks, track several accounts, or build a record of changes over time, this is not presented as that kind of product. It is also not a recovery tool. It cannot appeal a restriction, alter an account, or explain what X will do next.

The grey result creates another practical limit. When a check cannot be measured, the tool reports uncertainty rather than a clean pass. That is more informative than hiding the gap, but it means a user may finish with an unresolved result. A report with no hits is not necessarily proof that an account has normal distribution, and a detected signal is not necessarily an explanation for every post that performed poorly.

The platform boundary is simple too. This is a web service for X accounts. It is not a desktop or mobile application, and the available information describes no connection to other social networks.

Who should use it

This fits an X user whose reach has dropped and who wants a structured first check without handing over account credentials. It is especially useful for separating several possible restriction signals and for giving a creator a concrete post or policy reference to inspect, if the stated diagnostic features produce one.

It is not for someone looking for guaranteed proof of an algorithmic penalty, a prediction about when reach will return, or a long-term social analytics dashboard. Treat the result as evidence to investigate, not as an official decision from X. That is the sensible place for a nine-signal public check: useful for narrowing the problem, but not capable of resolving everything behind it.