Quick answer: to investigate an apparent X shadowban, check for account notices, compare whether your public profile and recent posts can be found, and review any X Under the Hood report available to you. A post missing from one search result is not proof of a restriction: X search applies relevance and safety filters, and results can differ between queries and viewers.
“Shadowban” is a user term, not a single public diagnostic result that an independent checker can verify for every account. The useful question is more specific: which visibility signal changed, what evidence can you observe, and what does X itself report?
What an X shadowban usually refers to
People use the phrase to describe several different experiences: a profile that is difficult to find, posts that do not appear for a query, replies that receive little exposure, or a change in recommendations. Those are separate surfaces and should not be collapsed into one “banned” or “clean” label.
X's own search guidance explains that not every post is guaranteed to appear in search. Search can filter or rank results based on relevance, account and content settings, and other quality or safety considerations. Start with the official X search troubleshooting guide and X search policies.
Separate profile, search, suggestions and replies
Before you run a check, decide which question you are trying to answer:
- Profile availability: does a public profile response contain the account identifier you requested?
- Search visibility: does a particular recent post appear in the limited public search query being tested?
- Username suggestions: does the exact username appear in the sampled typeahead response?
- Reply visibility: does a particular reply appear in a particular conversation and view?
- Recommendations: how does X distribute the content to individual users? A public username check cannot measure this.
A reachable profile does not prove that posts are searchable. One post appearing in search does not prove that every post is indexed or recommended. Reply ranking is conversation-specific and cannot be established from a username alone.
1. Review your X Under the Hood report
If X has made an Under the Hood report available for your account, review the reporting period and the labels it contains. The report can provide account-level and post-level information for the period covered by that export. It is more useful than a generic third-party “shadowban score” because it is information supplied in the report itself.
Shadowban.online lets you select an X Under the Hood JSON report and parse it locally in your browser. The report file is not uploaded by this import workflow. The checker displays supported reporting dates, account and post labels, explanations and associated counts when those fields exist in the report.
- Use the report from the account you want to investigate.
- Check the start and end dates before interpreting any label.
- Read the label's explanation and reported effect, not just its name.
- Compare the report period with the dates of your posts and any visibility changes.
A report only describes the information included for its reporting period. An absence of a label is not a promise about all future posts, current search placement or recommendation distribution.
2. Run a limited public visibility check
The X visibility checker requests a public profile response and attempts limited signed-out search and username-suggestion observations when it can establish a guest session. It reports each signal separately.
- Observed: the requested marker or item was returned in that response.
- Not observed: the sampled response did not return the item. This does not explain why it was absent.
- Unknown / inconclusive: the public endpoint failed, timed out, a guest session was unavailable, or the response did not contain enough evidence.
A generic HTTP success page is not sufficient evidence that the requested profile was found. The current checker requires an exact username marker for a profile observation. Its X search and typeahead checks must also receive their own usable responses; a reachable profile is never used as a substitute for missing search evidence.
The query is a limited sample, not a complete search-index audit. Results can be cached, so review the check timestamp and cache indicator before treating an observation as current. Search and typeahead endpoints can change or become unavailable.
3. Make your own search comparison repeatable
When you manually compare search results, change one variable at a time. Record the exact query, post URL, date, whether you were signed in, and whether the account or post was public. A general search for a display name is not equivalent to a query for a specific handle or post.
- Confirm that the profile and post are public and that the post has not been deleted.
- Search for the exact username and then for a specific recent post or phrase.
- Repeat the same query later without changing several settings at once.
- Where appropriate, compare a public signed-out view with your own signed-in view, while remembering that search results may still differ.
- Record what appeared instead of translating one missing result into a restriction verdict.
Avoid repeatedly running many near-identical searches in a short period. It can make comparisons noisy and may trigger platform protections or rate limits.
4. Interpret results without overclaiming
| What you observed | What it supports | What it does not prove |
|---|---|---|
| Profile marker found | That public response contained the requested identifier | Search indexing or recommendation eligibility |
| Post returned in sampled search | That the sampled query returned that post | Complete indexing or visibility to every user |
| Post absent from one query | Only that it was not returned in that sample | An account-wide restriction |
| Search API unavailable | That the check could not obtain evidence | That the account is restricted or unrestricted |
What an X shadowban checker cannot tell you
An outside tool cannot inspect all of X's internal ranking decisions, private account analytics or recommendation systems. Shadowban.online does not claim to measure impressions, For You distribution, every search index, or reply ranking from a username alone. It combines the supported local report import with a limited set of public response observations.
Never give a third-party checker your X password, one-time login code, session cookie or authorization token. A checker should not need your private credentials to review public signals.
Frequently asked questions
Does X have an official shadowban status?
The term “shadowban” is commonly used by users, but it is not a universal public diagnosis that a third-party tool can verify. Use X's notices, search guidance and any report information available to understand a specific issue.
Why can my profile appear while my post does not appear in search?
Profile availability and post search visibility are different signals. Search results are filtered and ranked, and not every post is guaranteed to appear for every query.
Can the X checker confirm a clean account?
No. It can report limited observations. If evidence is unavailable, it returns inconclusive rather than inferring that an account is clean or restricted.
Does the report import upload my Under the Hood file?
The report import is processed locally in the browser. The separate public username check sends the username to the checker server for limited public endpoint requests.
Related guides
- What is a shadowban? A practical cross-platform guide
- How to check Instagram Account Status and recommendation eligibility
- How to check TikTok For You feed eligibility
- How to check YouTube channel and video visibility
Last checked: November 4, 2026. X can change its search behavior, public endpoints and report formats. Check the official X help pages for current platform information.