How to test for an X shadowban without a tool

X shows you your own posts and replies even when other people will not. If you run every search while logged in as the account you are worried about, you will often 'pass' a test that a stranger fails. The manual test needs two seats: the account under test, and a browser that is logged out.

A private or incognito window is the simple version. Before you search, open x.com and confirm you are looking at a logged-out home page, not your timeline. If the window still has a session, the results are personalized. A second account you control is a useful extra, but it is not a clean substitute: it has its own follows, blocks, and ranking. Prefer logged-out for the search and reply checks, and use the second account only if you want to see what one specific person would see.

Protected accounts cannot be judged this way. A logged-out visitor is not supposed to see their posts. Suspended accounts fail every public test because the profile is gone, which is a different problem. This procedure is for a public account that still loads at https://x.com/yourhandle.

• Write the handle down without the @ so you do not search a display name by mistake.
• Note two or three recent original posts (not reposts) with a unique phrase you can recognize.
• Do not delete those posts in the middle of the test. You need them as the control.

In the logged-out window, use the search box and run from:yourhandle. Open the Latest tab, not Top. Top is a ranked view. An account can be absent from Top because the posts are not competitive and still be fully present on Latest. Latest is the closer check for 'does search index these posts at all.'

Put the profile and the Latest results next to each other. You are looking for specific posts, not for whether the account looks popular. If a post from the last day is on the profile, public, and not a reply-only ghost, it should normally be eligible to appear in from:handle Latest. If several recent original posts are missing, and a refresh plus a few minutes does not bring them back, that is the search-visibility symptom described in the search ban guide.

Search can lag. A post that is thirty seconds old is a bad sample. Use posts that have been up long enough to be indexed, and repeat the search once before you decide. Also try a unique phrase from the post in quotes, still logged out. If the phrase search finds the post, the account is not invisible to search even if a sloppy from: query looked empty.

What this test does not mean: a missing post can be a reply that search treats differently, a post you restricted, or a post with a label that removed it from search while leaving it on the profile. Read the post itself for a warning label before you generalize to the whole account. Sensitive labels are covered on their own page, sensitive media flags.

Autocomplete is a separate system from Latest search. Click the search box in the logged-out window and type the handle slowly, stopping one or two characters short of the end. Watch the suggestion list. You are checking whether your profile is offered before the query is complete.

Then finish the handle and run the search. Open the People filter if X shows one, and also look at the top results. An account can fail autocomplete and still appear the moment the full handle is submitted. That split is what people call a search suggestion ban rather than a search ban. An account that is missing from both Latest from: results and an exact People search is a stronger search-visibility problem.

Common false alarms: you typed the display name instead of the handle, the handle was changed recently, or a much larger account with a similar prefix fills the suggestion list so yours is below the fold. Scroll the suggestions. Try the test with a prefix that is still unique to you. Very new accounts and accounts with almost no activity are easy for suggestion ranking to ignore without any enforcement label at all.

Run this test logged out first. Then, if you want, repeat it logged in as someone who does not follow you. If logged-out search finds you and only one friend's app does not, you are looking at their blocks, mutes, or a client glitch, not an account-wide search ban.

Pick a public post from an account you do not control, ideally a conversation that is alive but not so large that ranking is chaos. From the account you are testing, post a reply that contains a unique short phrase you can search for by eye. Do not reply to yourself. Do not use a private or protected post.

Wait a couple of minutes. In the logged-out window, open that same post from its URL, not from your profile. Read the replies that load immediately. Then open Show more replies, or whatever control X is using to expand the lower-ranked replies. Use the browser's find function for your unique phrase.

• The phrase is in the main reply list. This test did not show a reply visibility limit.
• The phrase appears only after Show more. The reply was ranked down. One instance is ordinary. Repeat on two or three unrelated posts before you call it a reply deboost.
• The phrase is on your profile when you are logged in, and it never appears in the logged-out thread, including the expanded replies. That is the ghost ban pattern.
• The reply is still missing when you are logged in as the author. It did not send, the post was removed, or you are looking at the wrong conversation. That is not a ghost ban.

Authors almost always see their own reply in the thread. If you only check while logged in as yourself, you will not catch a ghost. Followers can also be a special case: some reply filters hide you from non-followers and still show you to people who follow you. The logged-out window stands in for a stranger. It does not stand in for every follower.

Mixed results are the normal outcome, and they are more useful than a single red badge. Search can work while replies are buried. Autocomplete can fail on a quiet account that is fully searchable. A sensitive image can be warned and still show up in from: search. Write the four results in a line: profile loads, Latest search, autocomplete, reply placement. That line is your diagnosis.

Repeat a failed test once after several minutes, still logged out, before you change your behavior. Search indexes and reply ranking both move. A post that appears on the second try was a lag, not a ban. A reply that is buried in one huge thread and normal in a smaller thread is ranking, not an account-level ghost.

Do not stack extra variables in the same hour. Deleting a dozen posts, changing your handle, and posting twenty replies 'to test it' makes the next result impossible to interpret. Note the time, keep the account quiet, and run the same four checks again later. There is no official number of hours to wait. A same-day retest catches indexing lag. A later retest is how you tell whether a limit lifted. More on that uncertainty is in how long shadowbans last.

A checker is this procedure, automated, with the failures that automation adds. It can run the search, suggestion, and reply probes faster than you can, and it can look at sensitive flags on recent posts. It cannot sit in your private window, and it cannot see a block relationship between two people. If the homepage checker and your logged-out test disagree, believe the specific posts you compared by eye, then run the tool again later in case its request failed.

Tools also disagree with each other because the labels are not standardized. One product's 'ghost ban' is another product's 'reply deboost' because one of them never opened Show more. Read the description of each card, not just the color. The comparison with X's own report is in Under the Hood vs checkers. Under the Hood will not perform this logged-out test for you. It answers a different question: which labels X says it applied to your account over the prior month, if you are eligible to see the report.

When the manual test shows a repeatable miss, the next page to use is how to recover: verify the account, stop the pattern that matches the failed test, and retest the same way. Do not file a stack of identical support messages and call that a test. Support cannot show you a logged-out from: search, and you can.