How to see who blocked you on X (and what X hides)

#Quick answer

You cannot see who blocked you on X as a list, because X does not publish one and its API has no endpoint that returns it. The single documented check is per account: open the profile and X shows a message telling you that account blocked you. Since the 2024 block change, a public account that blocked you is often still readable, so the reliable tell is not what you can see but what you can no longer do - follow, reply, like, repost, DM, or add them to a list.

Last updated: September 2026

#Why there is no list, and never was

X keeps a block list in one direction only. Under Settings and privacy, Privacy and safety, Blocked accounts, you get every account you have blocked, and you can export it through Your X Data. The CSV import and export feature that used to sit on that screen was retired, but the list itself is still yours to read.

Nothing points the other way. X's help page on being blocked runs a few short paragraphs and offers exactly one method: "If you visit the profile of an account that has blocked your account, you will see a message alerting you of the block." That is the whole documented surface. Block status belongs to the person who set it, and X treats it as theirs.

So the honest framing for this question is not "how do I get the list" but "how do I check one handle properly, and how do I tell a block apart from the four other things that look identical."

#The 2024 change that most guides still ignore

Here is where the pages ranking for this query go stale. Almost all of them were written against the old behaviour, where a block meant a wall and nothing else.

In September 2024 X shipped a change to blocking: if your posts are public, accounts you have blocked can see them, but cannot engage with them. That is not a rumour, it is on X's blocking page as a bullet under "Important things to know about using block." The reasoning given at the time was that a blocked person could always log out or use a second account anyway.

The practical consequence for you: seeing someone's posts is no longer evidence that they have not blocked you. If you are working from a 2023-era checklist, you will talk yourself out of a block that is actually in place. Protected accounts are the exception - their posts stay hidden from anyone who is not an approved follower, blocked or not.

#The checks that actually confirm a block

X lists what a blocked account cannot do. Turn each restriction around and you get a test you can run in about thirty seconds. The first row is the one X documents as the method; the rest are inference, but they are inference from published behaviour rather than folklore.

Run the profile check first. If the notice is there, you are done, and the other five rows are only useful when someone sends you a link and you want to know why nothing works on it.

#Block, deactivated, suspended or protected

Four different states produce the same "I cannot get to this account" feeling, and mixing them up is the most common mistake in this whole topic. One trick separates all of them: open the same handle in a private browsing window where you are not signed in.

That last row is worth remembering in both directions, because it is also the strongest privacy setting available to you. We cover the trade-offs in how to make your X account private.

If the logged-out check shows a suspension, the account owner has a different problem entirely, and X account suspended walks through the three states and the appeal route.

#Why no tool can give you names

Every few months a "who blocked me" product appears, and the ceiling is always the same one.

X's developer documentation lists three blocks endpoints: a GET that retrieves the blocked user list for the authenticated user, a POST to block, and a DELETE to unblock. The GET is scoped to the account holding the token, so it answers "who have I blocked" and only that. There is no endpoint, on any access tier, that answers "who has blocked me." The block and unblock actions are Enterprise-only on top of that.

Which leaves three kinds of product, none of them what people are hoping for:

• Counters. A tool that samples accounts and reports a rough number of blockers. No names, and the number is an estimate.
• Manual checkers. A wrapper around the profile visit you can do yourself, one handle at a time.
• Scrapers and credential grabbers. Anything asking you to paste a session cookie, install a broad-permission extension, or hand over your password is the category to walk away from. The upside is a list that does not exist; the downside is your account.

If you want the real picture of what third-party access to X costs and what it can legitimately read, how to get an X API key covers the current tiers. The short version is that the paid tiers buy you data about your own account, not other people's settings.

#What you can still do to an account that blocked you

Being blocked does not make you powerless, and X spells out two things that survive it.

You can still block them back. X states that if you have been blocked, you can still block other accounts, including any that have blocked you. Doing so is mostly symbolic given the block already exists, though it does clean up your own experience if their posts keep surfacing in replies.

Reporting also survives a block. X's page on being blocked is explicit that the option stays available, with one limit: you can include posts that mention you, unless the account has protected their posts and you do not follow them. Posts from that account which do not mention you cannot be viewed or included in your report.

What you cannot do is undo it. There is no appeal for a block, no form, and no support path. It is one person's setting on one account, and it is theirs.

#What to do about it instead

For most people asking this question, the answer that helps is not a list of names. It is deciding how much a block should cost you.

If a specific block hurts because it was a customer, a collaborator or a friend, the route back is off-platform, not through X. If it is noise, mute is usually the tool you actually wanted rather than block. Our guide to blocking someone on X lays out mute versus block versus private and which one fits which problem.

If the worry is scale, that people are quietly blocking you at a rate that matters, block counts are not measurable but their cousin is. Follower churn is visible, and how to see who unfollowed you on X covers what is actually trackable. Churn tends to answer the underlying question better anyway: blocks come from a handful of individuals, while unfollows come from the way your account reads to everyone.

The pattern behind both is engagement quality. Accounts that reply thoughtfully in their niche get blocked rarely and followed often; accounts that spray the same generic reply under every large post get blocked constantly and learn nothing from it. That is the difference X-Autopilot is built around - it runs from your own browser on your own Mac and writes replies in your voice with the context of the post, rather than firing template comments at strangers. It reduces the surface that gets you blocked, and it does not pretend to eliminate it.

#The short version

X gives you a list of who you blocked and nothing about who blocked you, on purpose. Check one profile at a time, trust the notice on the profile over anything else, and repeat the check logged out to rule out a suspension, a deleted handle or a protected account. Remember that a public account which blocked you may still be readable since 2024, so judge by what fails rather than what shows. And treat any tool promising a named list the way you would treat any other product selling something the platform does not expose.