Twitter Shadowban Checker
Check whether a public account still appears across its profile, recent posts, and Latest search—with evidence for every signal.
Check a public account
Use a handle or profile URL. No X password is requested.
How this Twitter shadowban checker works
A useful check does not ask whether one number is low. It asks where a public account or post stops appearing. CarryFeed follows the same recent posts through three public surfaces, so a missing search result cannot be confused with a missing profile.
-
Confirm that the public profile resolves
A profile that cannot be opened publicly is not a search-ranking result. The account may be protected, unavailable, renamed, or temporarily missing from the public source. That is why profile access is checked before any search conclusion.
-
Collect recent post IDs from the account
The checker takes a small sample of recent public posts and keeps their direct URLs. A direct post is the baseline: if it opens by URL, the post exists publicly even when a search page does not return it.
-
Compare those same posts with Latest search
CarryFeed runs a from:handle search in Latest and looks for the same post IDs. Matching IDs are useful evidence that the sample reached that search surface. A mismatch is a reason to verify manually, not proof of an account-wide ban.
How to read a Twitter shadowban check
The result is a decision aid, not a red-or-green label. Read the three observations together and stop when the evidence already explains what happened.
- No issue observed
-
The public profile and recent-post sample loaded, and at least one sampled post also appeared in Latest.
Next: Stop checking for a search restriction. Diagnose the post topic, timing, opening, and audience fit. - Needs a manual check
-
Recent posts loaded, but the same sample did not appear in the Latest result returned to CarryFeed.
Next: Open the prepared Latest search while logged out or from another account and check the same post URL. - Inconclusive
-
One of the public sources was unavailable, empty, private, or temporarily failed.
Next: Use the direct profile/post links shown, then repeat only the missing observation later.
When to stop: if the profile, recent-post sample, and at least one matching post in Latest all load, this check found no search gap in that sample. Low reach still may be real, but repeating the same checker will not explain it. Review the post's topic, timing, opening, and audience fit instead.
Why tweets may not appear in search
A post missing from one search result does not automatically mean the account is hidden everywhere. These are the most useful explanations to separate before you act.
-
The post is public, but this search sample is incomplete
A public profile or direct post can load while one search response omits it. Search requests can also be limited or temporarily unavailable. Repeat the missing observation before treating one empty sample as a durable restriction.
-
Latest and Top answer different questions
Top is ranked for relevance. Latest is closer to a chronological visibility check, although X says global visibility filtering still applies. Use Latest for the comparison and avoid reading a Top ranking as a simple pass-or-fail test.
-
Recommendation eligibility is not the same as public access
X can leave content available on an author's profile and to followers while limiting where it is recommended. If the direct URL works but discovery is weak, diagnose the affected surface instead of calling the whole account invisible.
-
Protected, deleted, and unavailable sources are stop states
A protected account, removed post, renamed handle, or unavailable public source cannot produce a reliable automated comparison. The honest result is inconclusive until the source can be opened again.
How to verify a suspected Twitter shadowban manually
Manual verification is most useful when the automated Latest check is unavailable or when recent posts and search results do not overlap. Keep the source fixed and change only the viewing context.
-
Choose one recent original post
Use a normal public post rather than a reply, repost, or very old item. Keep its direct URL and post ID so every viewing context checks the same source.
-
Open the prepared from:handle query in Latest
Look for that exact post, not merely the account name. If the account posts frequently, add a phrase from the post or a narrow date range in CarryFeed's Advanced Search tool.
-
Repeat from a signed-out window or another account
Search suggestions and reply placement depend on viewing context. A second context helps separate an account-specific view from a broader discovery problem.
-
Record the surface that failed
Write down whether the problem is profile access, direct-post access, Latest search, suggestions, or reply placement. Different failures need different next actions; one vague shadowban label does not.
If from:handle is too broad, use the Twitter Advanced Search tool to add a phrase, date, media filter, or reply filter without losing the source query.
Twitter shadowban checker questions
Can this checker prove that X shadowbanned my account?
No. Public tools cannot read X's internal enforcement state. This checker compares public surfaces and reports the observations separately.
Why does the result say inconclusive?
A profile, recent-post feed, or search request may be private, empty, rate-limited, or temporarily unavailable. The result names the missing observation instead of treating it as a ban.
Does low engagement mean I am shadowbanned?
No. Low engagement can be a reason to run the check, but it is not evidence by itself. A useful visibility check compares the same account or post across public surfaces.
Why does the checker use Latest instead of Top?
Top is ranked for relevance and engagement. Latest is the better comparison for whether a recent public post appears in the search surface, although X still applies visibility filtering.