Blocked or gone for everyone: the scope test
· AnonSight · rev
Scope first: only you, or everyone?
A block is a setting between exactly two accounts. The owner picks one account, yours, and Instagram then withholds their profile from it. Every other account keeps the view it had. So the useful first question is not “was I blocked?” but “who else lost the profile?”. The answers sort by scope:
- Missing for you only. Other signed-in people still open it. The scope is your account, and a block fits.
- Missing for everyone signed in. Friends on their own phones get the same empty result. The scope is the whole account, so it is not a block.
- Missing even with no session. A read with no login returns nothing either. Scope: the account, or the handle you typed.
When several friends notice the gap on the same day, the second line already applies. A block on each of them at once is possible in theory; a single account-wide change explains it with one event.
The in-app signs come next, and they come as a set. From the blocked account, the picture is this:
- Search: the handle returns no result for you.
- Profile link: a page-unavailable notice.
- Follow: fails.
- Tagging: their handle is refused.
- Your past likes and comments: gone from their posts. Your own account cannot show you that change.
- Direct messages: the thread stays in your inbox. New messages leave your side and never arrive, and an unblock later does not deliver them either.
- Notice: none. The blocked account is not told by Instagram.
No single item on that list proves anything. Search, the unavailable page and a failed follow also appear for accounts that are deactivated or deleted. That overlap is why scope is tested before any sign is read.
A different pattern is when the profile opens as usual and only the story ring is missing. That is not a block at all, and its causes are listed in One person’s stories won’t load: five causes.
AnonSight makes the third line testable from a browser: it takes a public handle, and signing in to Instagram is never one of the steps. Reference state for each Instagram behaviour on this page: iOS and Android apps, personal accounts, 24 Sep 2026. A line carrying its own date overrides it.
One error string, six account states
“User not found” is one response covering six account states; the unavailable page is the same response in another form. The app returns the same text for all of them and adds no hint. Grouped by scope, they sort like this:
| Scope | State | What actually changed |
|---|---|---|
| Pair | Blocked you | The owner removed your account from their audience |
| Account-wide | Deactivated | Switched off by its owner, and reversible by the same owner |
| Account-wide | Deleted | Removed by its owner |
| Account-wide | Username changed | Same account, new handle; the old handle stops pointing at them |
| Account-wide | Removed by Instagram | The platform took the account down |
| Input | Mistyped handle or dead link | Account untouched; the request named a wrong handle |
One row out of six is scoped to a pair of accounts. Four are scoped to the account itself and would hit every viewer equally. One is a fault in the input. Reading the message as “blocked” means betting on one row with no evidence against the other five.
Two rows deserve a closer look.
Input. A single wrong character, a trailing dot or a link copied from an old caption yields the same string as a deleted account. Check the handle character by character before anything else. It is the cheapest row to remove.
Rename. A new username breaks saved links and old @-mentions of the old handle in one go. An account active every day can read as deleted from one hour to the next, for all viewers at once, which matches the “gone for everyone” pattern exactly. Tracing a handle that changed is its own task, covered in Old friend, business, lost handle: finding them.
Deactivating and deleting are distinct owner actions, and the platform’s help centre covers both, starting from Permanently delete or deactivate your Instagram profile. Seen by a viewer, the pair return an identical response.
Three observers, one handle
Scope cannot be read from one seat. It takes at least two readings of the same handle, made from places that do not share your account. First, copy the handle character for character, so the input row is out of play. Then compare:
| Observer | What loads | What that rules out |
|---|---|---|
| Your app, signed in | Nothing: empty search, unavailable page | Nothing yet; all six states look like this |
| A friend’s app, signed in | The profile | Every account-wide state and a typo; a block on you remains |
| A friend’s app, signed in | Nothing | A block on you as the full explanation |
| A read here, no login | Header, current stories, latest grid items, reels | Removal, deletion, deactivation, a stale handle |
| A read here, no login | “No account with this handle” | Makes a block unlikely for an open profile; retry once to be sure |
Read it as a block when the profile resolves for a friend and in a signed-out read, and fails only in your app. Every account-wide state would fail in all three seats. The friend’s seat has one caveat. If the owner blocked that friend as well, the friend’s view proves nothing, so a seat with no account attached is the cleaner control.
This site offers such a seat. A signed-out read of the same handle returns an open account’s header block, any live frames, the grid’s newest items, reels, highlights, and the first pages of its follower lists. For that read, no account of yours is used; the route is described step by step in Story viewing with no account in the request.
A plain instagram.com tab with no login is a weaker observer. Signed out, Instagram serves the header plus an opening set of posts, and the grid then ends at a button asking for more. Stories sit behind the login wall outright. Verification covered desktop Chrome only, with phone browsers left out. Such a tab still settles the scope question for a public profile, provided the browser really holds no Instagram session. A tab where you are signed in is just your app again.
Block, restrict, mute, hidden story: scope of each
The word “blocked” gets applied to four separate settings. Just one of the four takes a profile away, so just one triggers the scope test.
- Block. Removes the profile, its stories, the search result and tagging, for one account. Your screen then reads “User not found”.
- Restrict. Removes nothing from the profile view. The changes sit in comments, messages and online status, split by side in Restricted on Instagram: who sees what, per side. An account under restriction still opens the profile and watches stories, with no notice from Instagram.
- Hidden story. Removes the stories for you, and only the stories; the profile keeps opening as normal. No alert about it reaches you.
- Mute. Takes nothing away on your side: the profile stays exactly where it was.
Where the profile still resolves for you, the scope test has nothing to measure; the cause is one of the quieter three, or no setting at all.
Where the outside read returns nothing useful
The three-seat comparison has blind spots. Each one returns a response that fits more than one state.
Locked profile. A read here stops at a locked account. The response is the top card alone, stamped Private, every tab inert. A locked handle, blocked or unblocked, gives this page one identical answer. A friend’s signed-in view is the better seat in that case. Non-follower access to a locked account is the subject of Private accounts: one rule, enforced by Instagram.
Deactivated or deleted. Identical from every seat, including a read on this page. A deactivated account comes back whenever its owner signs in again; a deleted one, once the deletion completes, does not.
Renamed. The old handle returns nothing anywhere, here included, unless someone else has since claimed it. The read can only confirm a new handle once you have one.
Out of scope. Reading a locked profile whose owner blocked you. No seat on this page reaches it, and nothing here is built to.
In each of these cases the accurate status is “undetermined”, and no seat on this page upgrades it to “blocked”.
Blocks and vanished handles: FAQ
A block, seen from the blocked account: what shows?
Absences, mainly. Your search no longer finds the handle, the profile link reports the page unavailable, follows and tags fail, and new messages stay undelivered. No block notice reaches you.
Block or deactivation: which one is it?
Ask a second seat. Deactivation takes the account away from every viewer, signed in or out, while a block takes it from your account only. Public profiles therefore keep loading for a friend and in a signed-out read.
Does “User not found” prove a block?
No. Six states share the string: deletion, deactivation, a block, a changed username, removal by Instagram and a mistyped handle. A block becomes the likely reading only if the profile loads in some other seat and fails in yours.
Friends can open the profile and I can’t. What does that mean?
Pair-scoped cause. The profile is live for other viewers, so deactivation, deletion and removal drop out. A block on your account fits best; recheck your copy of the handle once before settling on it.
Would a mutual friend still see the profile if I were blocked?
Yes. A block covers one pair of accounts, the owner’s and yours. A mutual friend keeps the same view as before; as for you, no notification of the block arrives, then or later.