Check if you're shadowbanned on X (Twitter)

Wondering, "Is my Twitter shadowbanned?" X does not describe its visibility limits as shadowbans, but reach can still be restricted. This free checker tests public, logged-out signals for search suggestions, search, and profile visibility. Reply ranking needs a specific conversation, so that signal may remain unknown. No login is required. X's own account notices and visibility controls are the authoritative place to review account-specific decisions.

Support Us

Check a public X username

@

Four visibility signals, with clear limits

Search suggestion visibility

The typeahead signal checks whether a logged-out X search suggestion response includes the username. A missing suggestion can happen because of personalization, query matching, endpoint changes, or temporary service limits. It is not, by itself, proof that X has restricted an account. Try the exact handle in a private browser window and compare more than once before treating an absence as meaningful. Make sure the spelling and punctuation match the public handle, and remember that suggestions can be affected by the query and the viewer's location or recent activity. A successful response confirms only that this endpoint returned a suggestion at that moment. It does not measure impressions, recommendations, or what every user sees. If the endpoint is unavailable or rate-limited, the result stays unknown instead of treating a failed request as a ban.

Search visibility

A search request for public posts associated with an account can offer a limited view of search indexing. Results depend on whether the account has public posts, the query, language, location, and X's current search behavior. This checker cannot see personalized results or private account notices. An empty or incomplete response is marked inconclusive unless the endpoint provides evidence that can be interpreted reliably. A new or quiet account may have no matching posts; protected, deleted, or age-restricted material also will not behave like ordinary public posts. Search may take time to index new content and may rank identical queries differently. Compare a specific public post from a signed-out session rather than relying on a single broad query. Even repeated absence is a reason to inspect X's own account notices, not a definitive diagnosis from a third party.

Logged-out profile visibility

The public profile signal checks whether X returns the requested account without a signed-in session. A reachable profile only confirms that the profile endpoint responded; it does not prove that every post is visible in search or recommendations. A profile may be unavailable for reasons unrelated to a visibility restriction, including a changed handle, suspension, deletion, age or region controls, and temporary errors. Check that the entered username is current and does not include a URL or extra punctuation. If the profile loads in one browser but not another, sign-in state, region, age settings, or an intermittent platform response may explain the difference. This test does not inspect private analytics, follower-only posts, or account status messages. Treat a positive profile response as one narrow observation and use the platform's own notices to understand any account-specific action.

Reply visibility

Reply ranking is conversation-specific. Replies may be collapsed, hidden behind a control, or ordered differently for different viewers. A username alone does not identify a conversation or let a third-party tool inspect the views of multiple logged-out readers. This signal therefore remains unknown here. Ask a trusted person to compare the same public conversation while logged out, and check any account notices in X before drawing a conclusion. Compare the same reply URL and conversation rather than searching only for the author's handle. Replies can be deleted, filtered by the author, hidden by a viewer's settings, or ranked below a platform control for ordinary quality and safety reasons. A difference between accounts is not enough to establish a penalty. X alone can explain whether it applied a specific visibility action, and a supported appeal should refer to the notice or content involved.

What to do if visibility changed

  1. Pause repetitive behavior while you investigate. Avoid repeatedly posting identical replies, hashtags, links, or unsolicited direct messages; normal posting frequency varies by account and there is no universal safe quota. Check recent activity for automation, duplicate posts, or behavior that may have triggered a platform warning. Do not try to evade a restriction with alternate accounts or rapid retries. A short pause is a practical troubleshooting step, not a guaranteed fix or an admission that a rule was broken.
  2. Review the posts and replies that changed visibility. Remove or edit content only when it violates X's current rules or you no longer want it public. Keep a copy of relevant account notices and avoid mass-deleting content based only on an inconclusive third-party result. Check the date, affected post, and wording of any notice; distinguish content removal from reduced search or recommendation eligibility. If an item is accurate and allowed, use the review path attached to that specific decision rather than repeatedly reposting it.
  3. Give temporary limits time to clear, then compare the same public searches from a signed-out browser. Recheck after a reasonable interval rather than submitting many rapid checks; this service rate-limits requests and caches results for up to one hour. Compare several posts with similar topics and ages, and record the query, time, and whether the viewer was logged in. Audience changes, seasonality, competition, and ranking experiments can change reach without any account restriction. One post's views are not a reliable account-wide measurement.
  4. Use X's in-product account status, safety, and content visibility controls, and follow the appeal or review link shown on the specific notice. Menu names and available controls can change. Only X can confirm an account-level decision or restore distribution. Review the current rules and any explanation tied to a particular post before appealing, and include relevant URLs if the official form requests them. Do not give a third-party checker your password, verification code, or access token. If there is no account notice, continue to treat public endpoint results as clues rather than a confirmed penalty.

No account login or watchlist. Results may be cached for up to one hour; infrastructure providers may retain technical request logs under their own settings. Last updated October 3, 2026. Built by @gutnews247.

Buy Me a Coffee

Frequently asked questions

Does X have an official shadowban status?

X does not provide a single public status that confirms every kind of reduced visibility. Review account notices and X's own visibility controls for authoritative information.

What does this X shadowban check test?

It checks whether logged-out X endpoints return typeahead, search, and public-profile signals. Reply ranking cannot be confirmed from a username alone, and an unavailable endpoint is marked unknown.

Can a clean result prove my posts are not downranked?

No. Public endpoints cannot reveal all personalized search, recommendation, moderation, or reply-ranking decisions. Treat each result as a limited signal, not a guarantee.

Do I need to connect my X account?

No. Enter a public username only. Never provide a password, verification code, or access token to a third-party checker.

By @gutnews247
Get alerted if banned again

OUR OFFICIAL ACCOUNTS - TEST THEM

Twitter: @gutnews247Instagram: @aljannah.tvTikTok: @hownwhenFacebook: functionSmarterAIYouTube: @villainaudit