How to Check if You're Shadowbanned on X (Twitter) 2026

By Sorsa Editorial

Updated June 2026: added X's native Account status check, refreshed the logged-out search steps for X's current behavior, added the sensitive-media setting to the recovery steps, and re-verified the enforcement figures against X's own transparency report.

A shadowban is the most disorienting problem on X because nothing visibly breaks. Your posts publish, your likes register, your follower count holds. From the inside everything looks normal. From the outside you have quietly dropped out of search, and your replies sink to the bottom of every thread.

The fastest checks are a one-minute manual test and X's own Account status screen, both covered below. That same logged-out from:username search is also a single call to Sorsa API, an alternative Twitter/X API: it runs the check on maintained infrastructure that does not break when X reshuffles its search the way scraper-based checkers do, costs a flat rate per request (far cheaper than the official X API for reads like this), and needs one API key with no app approval and no OAuth. Check a single account free in our shadowban checker, or automate the same test across hundreds.

We build and run that API, and since 2022 we have watched X's visibility filtering grow more aggressive and less transparent, which is what this guide reflects: how to confirm a shadowban in 2026, how to tell which restriction you have, and how to get your reach back. Every method below is free, and none require connecting or logging your X account into a third-party tool.

Table of Contents

1. What Is a Shadowban on X (Twitter)?
2. The Types of Shadowban on X
3. How to Check if Your X Account Is Shadowbanned
4. What Causes a Shadowban on X?
5. How Long Does a Shadowban Last on X?
6. How to Fix a Shadowban on X
7. How to Avoid Getting Shadowbanned on X
8. Checking Shadowbans at Scale
9. In Practice: A Reply-Spam Ghost Ban
10. FAQ

What Is a Shadowban on X (Twitter)?

A shadowban on X (Twitter) is a silent restriction that limits how far your content travels without notifying you. X's official term is "visibility filtering," applied under a policy it calls "Freedom of Speech, Not Reach." You keep full posting access, but the platform decides who is allowed to see what you publish.

This is not a fringe theory, and X no longer fully denies it. In a 2018 blog post, Twitter denied shadowbanning by defining it narrowly as making content invisible to everyone, then argued that ranking adjustments and search exclusions did not meet that definition. The wording was technically careful and practically misleading.

Under current ownership the practice sits in X's own filings. X's April 2024 DSA transparency report, covering October 21, 2023 through March 31, 2024, disclosed 502,920 "restricted reach" labels. Around 87% of them were applied automatically with no human review. According to X's transparency center, a restricted-reach label strips the ability to engage with a post and confines its reach to views that happen directly on the author's profile. In plain terms, the post vanishes from search, recommendations, and other people's timelines while still looking normal to you.

There is an important distinction worth holding onto, because it shapes how you check. Some restrictions are explicit account labels you can actually see: X built an Account status screen that names a label and offers an appeal. Others are the silent algorithmic kind, the true "shadow" part, where nothing is surfaced to you at all. A complete check covers both.

Academic work reached the same conclusion before X admitted anything. A 2021 peer-reviewed study presented at IEEE INFOCOM crawled more than 2.5 million Twitter profiles and found that the platform's "it is just bugs" explanation for visibility limits was statistically implausible, one of the first large-scale confirmations that shadowbanning was real and measurable.

If you rely on X for audience growth, brand reach, or lead generation, a shadowban can erase your visibility for days before you notice. That is why testing matters.

The Types of Shadowban on X

X uses several distinct visibility restrictions, and they behave differently: a search ban (your posts vanish from search), a search suggestion ban (your handle stops appearing in autocomplete), a ghost ban (your replies get hidden behind a "Show more replies" click), and reply deboosting (your replies are pushed to the bottom of threads). Knowing which one you have determines how you fix it.

Search Ban

The most damaging common restriction. Your posts stop appearing in X search entirely, even when someone searches your exact handle with the from: operator. If from:yourhandle returns nothing in the Latest tab despite recent posts, you are search-banned. It is usually triggered by spam-like patterns: duplicate content, hashtag stuffing, automated posting, or abnormal volume.

Search Suggestion Ban

The lightest restriction, sometimes called a "hard" shadowban in older community guides. Your account stops appearing in X's autocomplete dropdown when someone starts typing your username. New people cannot find you by guessing your handle. It often acts as an early warning that a fuller search ban is coming.

Ghost Ban (Thread Ban)

Your replies to other accounts get tucked behind a "Show more replies" link that most readers never expand. The replies technically exist, but conversations you join look broken to anyone who does not already follow you. This one hurts most if your strategy depends on reply visibility under popular posts.

Reply Deboosting

Subtler than a ghost ban. Your replies are not hidden behind a click, they are sorted to the very bottom of the thread under dozens of others. You are visible in theory and invisible in practice. It targets accounts with low-quality engagement patterns, and in 2026 it is the most commonly reported restriction, especially on non-Premium accounts.

A related mode people increasingly describe is "For You" exclusion, where your posts stop surfacing in the algorithmic feed even though they still appear on your profile and in followers' chronological view. It overlaps heavily with the search and reply restrictions above and responds to the same fixes, so it rarely needs to be treated as its own category.

Shadowban Types at a Glance

How to Check if Your X Account Is Shadowbanned

To check if your X account is shadowbanned, run more than one test, because no single signal is conclusive. Start with X's native Account status to catch any explicit label, then confirm a search ban with a logged-out from: search, check autocomplete for a suggestion ban, and use a second account to test for a ghost ban. None of these require logging into a third-party service.

The methods build on each other, and the first one is the step most guides still skip.

Check X's Account Status (the official, native way)

X added an account-level status screen that tells you directly when your reach has been limited. This is the only first-party signal, so it is the place to start.

1. Open X on the web or in the app.
2. Go to Settings and privacy, then Your account, then Account status.
3. If X has applied an explicit label (for example, sensitive content or a policy flag), it appears here with a reason and, in most cases, an appeal link.

The catch is that Account status only surfaces the explicit, account-level labels. The silent algorithmic restrictions, which is what people usually mean by "shadowban," do not show up here. A clean Account status screen does not prove you are unrestricted. It only rules out the labeled kind, which is why the manual tests below still matter.

The Logged-Out Search Test (detects a search ban)

You can confirm a search ban yourself in under a minute:

1. Log out of X completely, or open a private or incognito browser window.
2. Go to X search and type from:yourusername.
3. Switch to the Latest tab.
4. If no posts appear and you have posted recently, you likely have a search ban.

This is the same from: lookup that the consumer checkers run under the hood. If you want to push it further, our Twitter search operators cheat sheet covers the full syntax X's own search understands.

The Autocomplete Test (detects a suggestion ban)

While completely logged out, start typing your @username into the X search box without pressing enter. If your account shows in the dropdown, your handle is in good standing. If it does not appear, you have a suggestion ban.

The Reply Test (detects a ghost ban or deboosting)

Reply to a popular post from an account you do not follow, then open an incognito window or log out and find that same post. If your reply is buried under "Show more replies" or missing from the visible thread, your replies are being ghosted or deboosted. Ghost bans are the hardest type to confirm alone, which is where a second account or an automated check saves real time.

Use a Free Shadowban Checker

A checker queries X's public search and typeahead infrastructure and reports whether your content and handle are visible, without a login. The Sorsa shadowban checker tests for search ban and search suggestion ban, the two most reliably detectable types, and returns results in seconds with no account connection and no daily limit.

You will also see older community tools recommended, the best known being shadowban.yuzurisa.com (formerly shadowban.eu), which historically tested all four types. Two things are worth knowing in 2026: its quality-filter test was removed after X deprecated the mechanism it relied on, and tools built on scraping X's front end break whenever X changes its search internals. That fragility is exactly why people keep searching for whether these checkers still work. A checker that runs on a maintained API rather than brittle scraping stays accurate through those changes, which is the practical reason to cross-check rather than trust a single tool.

What Causes a Shadowban on X?

Shadowbans on X are triggered by behavioral patterns, not single posts, and detection is almost entirely automated. X's spam systems were built to catch bot networks, and they do not reliably tell a bot apart from a human who behaves like one. The most common triggers are spam-like posting, follow/unfollow churn, third-party automation, mass low-quality replies, policy violations, a high rate of blocks and reports, and aggressive activity from brand-new accounts.

Spam-like posting patterns. Duplicate or near-duplicate posts, stuffing 10+ hashtags per post, flooding trending topics, or blasting 50+ posts in an hour. This is the single most common cause of a search ban.

Follow/unfollow churn. Following hundreds of accounts and unfollowing them days later is a classic growth hack and a textbook bot signal. X flags the churn regardless of intent.

Automation and third-party tools. Bots, auto-reply scripts, and tools that act on your behalf raise flags through timing, fingerprints, and action velocity. For a deeper look at how X detects this, see our guide on the automated-request error on X.

Mass low-quality engagement. Rapid-fire generic replies ("Great thread!", "So true!") across dozens of conversations signal low-value engagement and primarily trigger reply deboosting and ghost bans.

Content policy violations. Posts flagged under Hateful Conduct, Abuse and Harassment, or Violent Speech can be filtered under the Freedom of Speech, Not Reach policy. These are also the cases most likely to produce a visible label on your Account status screen.

A spike in blocks, mutes, or reports. If many users block, mute, or report you in a short window, X reads it as a signal that your content is unwanted and can limit your reach while it reviews the account.

New accounts with sudden spikes. Fresh accounts that post or follow aggressively get flagged faster, because X's trust scoring weighs account age, profile completeness, and history. A new account with no avatar doing 40 replies in its first hour will get restricted.

The common thread is the pattern, not any single action. X matches your behavior against the shape of bot activity, so the fix is almost always about changing the rhythm of what you do rather than deleting one specific post.

How Long Does a Shadowban Last on X?

A shadowban on X typically lasts 24 to 72 hours for automated restrictions once you stop the triggering behavior, and one to two weeks for human-reviewed cases. Repeat offenders face longer durations, because the algorithm applies a shorter fuse to accounts with a history of violations. The exact length depends heavily on the type.

A search suggestion ban is the fastest to lift, usually 12 to 48 hours and rarely past 72. A search ban runs 2 to 7 days, averaging 3 to 5 when you take recovery steps, and stretching toward 14 for repeat offenders. A ghost ban lingers longest, 3 to 14 days on average and up to 30 in severe or repeated cases. Reply deboosting is the most variable: light cases clear in 48 to 96 hours, but persistent low-quality patterns can keep it active for weeks, because it tracks behavior in near real time rather than running on a fixed timer.

One rule holds across all four: repeated violations lower the threshold and extend future durations, while a clean history buys you the benefit of the doubt.

How to Fix a Shadowban on X

To fix a shadowban on X, stop all activity immediately, remove the content that triggered it, revoke third-party app access, then re-enter slowly over several days. Most search and suggestion bans clear within a week if you follow these steps and do not repeat the behavior. Every interaction during a restriction can reset the algorithm's penalty timer, so the cool-down only works if it is genuinely quiet.

Day 0 to 1: Stop and Clean Up

1. Stop all activity. No posting, replying, liking, or following. The algorithm is watching for continued patterns, and each new action can restart the clock.
2. Delete recent offending content. Review your last 48 to 72 hours: mass replies, hashtag-heavy posts, duplicate content, promotional links. Remove what could have triggered the restriction.
3. Check your sensitive-media setting. In Settings, Privacy and safety, make sure your own posts are not incorrectly marked as containing sensitive media, which can quietly limit how widely they are shown.
4. Revoke third-party app access. Go to Settings, then Security and account access, then Apps and sessions, and remove any automation tools or apps you do not actively need.

Day 1 to 3: Stabilize

5. Complete your profile. Verify your email and phone, and add an avatar, bio, and header. Incomplete profiles score lower in X's trust model.
6. Recheck your status. Run a shadowban check and look at Account status again. If a restriction persists after 48 hours of inactivity, do not panic, since some types take longer.
7. Do not create a new account to evade it. X detects evasion through IP, device fingerprints, and behavior. A second account makes things worse.

Day 3 to 7: Re-Enter Gradually

8. Resume posting slowly. One to three original posts a day to start, spaced at least an hour apart. Favor your own content over reposts and links.
9. Skip hashtags for the first few days, then keep them minimal. Hashtag volume is one of the fastest ways to re-trigger a search ban while your account is still on a short leash.
10. Engage with substance. Reply with real responses, not one-liners. Quality over quantity.

Day 7+: Appeal

11. File an appeal. If a label is showing on your Account status screen, use the appeal option there. Otherwise submit a request through X's Help Center, state that you believe your account was incorrectly restricted, and be specific about what you have fixed. Responses can take days to weeks.

A note on X Premium: subscribing does not prevent or lift a shadowban. Premium may give a small baseline boost in algorithmic reach, but it does not override visibility filtering, and Premium accounts get restricted on the same triggers as free ones. Do not buy a subscription expecting it to fix this.

How to Avoid Getting Shadowbanned on X

Most shadowbans come from sustained patterns, so consistent habits keep you off the algorithm's radar. Keep posting volume reasonable, limit hashtags, avoid follow/unfollow churn, write genuine replies, and be careful with automation.

Keep volume reasonable. A safe range for most accounts is 5 to 15 posts a day, spaced out. Fifty posts in an hour gets flagged regardless of quality.

Limit hashtags to 3 to 5 per post. Going above that, especially on trending topics, is one of the most common search-ban triggers.

Avoid follow/unfollow churn. If you use growth tools that mass-follow then unfollow, stop. This is the single most reliable way to get flagged.

Write real replies. If a reply could apply to literally any post ("Love this!", "Facts!"), it is the kind of engagement the algorithm deprioritizes. Make responses specific enough that they only make sense in context.

Monitor your reach. Track engagement over time so you can spot drops early. A baseline tool like the Sorsa engagement calculator helps you tell a real decline from normal fluctuation before it becomes a long-term problem. For automated tracking in your own stack, our Twitter analytics API guide shows how to pull those metrics programmatically.

Be careful with automation. Keep scheduling tools to basic post scheduling. Anything that automates replies, likes, follows, or DMs sharply raises your risk.

Checking Shadowbans at Scale

If you manage accounts for clients, brands, or a community, checking each one by hand does not scale. The logic behind every shadowban checker is simple enough to automate: query X's search for a user's content and see whether results come back. A from:username query that returns nothing despite recent posts indicates a search ban, and a missing typeahead result indicates a suggestion ban.

Any Twitter/X data API with search support can run this. Sorsa's search-tweets endpoint accepts the full advanced-search syntax, including from: queries, which is the same mechanism the consumer checkers use internally. Because it runs on maintained infrastructure rather than front-end scraping, a batch check across hundreds of handles stays consistent instead of breaking every time X reshuffles its search. A single call looks like this:

import requests

resp = requests.post(
    "https://api.sorsa.io/v3/search-tweets",
    headers={"ApiKey": "YOUR_API_KEY"},
    json={"query": "from:targethandle", "order": "latest"},
)

tweets = resp.json().get("tweets", [])
print("search-ban suspected" if not tweets else f"{len(tweets)} posts visible")

The economics are what make this practical at volume. As an X data provider, Sorsa uses flat per-request pricing on every plan, with a 20 request-per-second limit and no per-endpoint metering, which for read-heavy auditing works out far cheaper than the official API (roughly an order of magnitude or more once you are doing this across many accounts). Setup is a single API key in the header with no app-approval process, and we have served more than 5 billion requests on this infrastructure since 2022. The quickstart guide covers authentication and a first query, and if you are weighing options, our Twitter/X API alternatives comparison breaks down the practical tradeoffs against the official API and the scraper tools. If all you need is to check one personal account once, the free web checker is the right tool; the API is for doing it repeatedly, at scale, inside your own systems.

There are really three ways to run shadowban checks at volume, and they trade off differently on cost and stability (the per-resource figures below come from the official X API's pay-per-use pricing):

Of the three, the API is the only one that stays both affordable and stable as X reshuffles its search, which is why it is the practical choice once you are auditing more than a handful of accounts.

In Practice: A Reply-Spam Ghost Ban

A small marketing agency we work with, under ten people running social for several consumer brands, came to us after one client account's engagement fell off a cliff over a weekend. Nothing in their dashboard flagged a problem: every post and reply had published normally, and the follower count was steady. The giveaway was that impressions on new posts had collapsed while older posts kept their numbers.

The cause was a community manager who had been posting near-identical promotional replies, each with the same link, under dozens of trending threads a day to chase reach. That is a textbook ghost-ban and search-ban trigger. A logged-out from: search confirmed the posts were missing from search, and a second-account check showed the replies buried under "Show more replies." Account status, notably, showed nothing, a clean illustration of why the labeled-status check alone is not enough.

The fix was unglamorous and matched the recovery steps above: stop the reply campaign, delete the worst offenders, and re-enter at a human pace. Visibility came back over the following week. The lesson we keep relearning is that the automation does not care about intent. Behavior that looks like a bot gets treated like a bot, whether a script or a well-meaning human is driving it.

FAQ

How do you know if you're shadowbanned on X?

You know you are shadowbanned on X when your reach drops without any change to your posting and external tests confirm it. The two fastest checks are a logged-out search for from:yourusername in the Latest tab, where missing recent posts indicate a search ban, and X's Account status screen under Settings, which shows any explicit reach label. A drop in impressions alone is suggestive, not proof.

Does X notify you when you are shadowbanned?

No. The defining feature of a shadowban is that you are not told. For the silent algorithmic restrictions, your account looks and functions normally from your side, so the only way to find out is to test externally with a from: search or a checker tool. The one exception is an explicit policy label, which X does surface on the Account status screen with a reason and an appeal option.

Is a shadowban the same as being suspended or banned on X?

No. A shadowban (visibility filtering) limits how far your content spreads while leaving your account fully usable, and it is usually silent. A suspension or ban removes or locks your account outright and comes with a clear notification. If you can still post but your reach has collapsed, that points to a shadowban; if you are locked out or see a suspension notice, that is a separate and more severe enforcement action.

Does X Premium remove a shadowban?

No. X Premium (formerly Twitter Blue) may provide a minor boost in algorithmic distribution, but it does not exempt you from visibility filtering. Premium accounts get shadowbanned on the same triggers as free accounts, and subscribing will not lift an existing restriction. Recovery comes from stopping the triggering behavior and waiting out the cool-down, not from a paid tier.

Is shadowban.yuzurisa.com still accurate in 2026?

shadowban.yuzurisa.com (formerly shadowban.eu) still runs, but its quality-filter test was removed after X deprecated the mechanism it depended on, and front-end-based checkers break whenever X changes its search internals. Treat any single checker as an indicator, not proof. Cross-checking with a second tool that runs on a maintained search API, such as the free Sorsa shadowban checker, gives more reliable results.

How do you check shadowbans across many X accounts at once?

Developers automate the same from:username search test that web checkers run manually. Sorsa API's search endpoint accepts advanced-search operators including from:, returns clean JSON, and authenticates with a single API key. At 20 requests per second, a script can run one search per handle and audit hundreds of accounts for search-ban status in a single pass, without connecting any X account.

What causes a reach drop when a shadowban checker shows nothing?

Not every reach drop is a shadowban. Algorithm changes, posting at low-traffic times, a less engaging topic, or normal week-to-week variance all cause dips. If a shadowban test and your Account status both come back clean, the cause is more likely content or timing than a restriction on your account. Tracking your engagement rate over time helps separate a real decline from ordinary fluctuation.

Can you be permanently shadowbanned on X?

There is no documented permanent-shadowban category. Restrictions lift once the triggering behavior stops, but repeated violations make the algorithm quicker to restrict you again and for longer each time. In extreme cases, persistent violations escalate from visibility filtering to a full account suspension, which is a separate and more severe action than a shadowban.

Check Your Account Now

If your reach has dropped and you want a fast answer, run Sorsa's free shadowban checker: enter a handle and get search-ban and suggestion-ban results in seconds, no login or account connection required. To audit many accounts, the same from: test runs through Sorsa's API at a flat 20 requests per second on every plan, far cheaper than the official X API for reads like this, with a single API key and no app approval. The quickstart gets you a first query in a few minutes. Questions about X data access? Reach us at contacts@sorsa.io or on Discord.

Reviewed by Keksich, founder of Sorsa, marketer and X API researcher.

How we put this together: we build and operate an alternative Twitter/X API and have run search-based queries against X's public endpoints since 2022, the same mechanism every shadowban checker depends on. For this update we re-ran the logged-out from: test against live accounts and walked through X's current Account status screen in June 2026, and we verified the enforcement figures directly against X's DSA transparency filing rather than secondhand summaries. The other external claims trace to primary sources: X's 2018 statement on shadow banning and the 2021 IEEE INFOCOM study on Twitter visibility limits. Product details come from the Sorsa API documentation; more about who we are is on our About page. Last verified June 5, 2026.