How Greatfon works, part by part
Issued · Kimberly Jung
Four parts of one lookup, and what each sees
Four parties touch each lookup. The Instagram rules below are as of September 24, 2026; the lookup behaviour is as of October 13, 2026; a line with its own stamp overrides that date.
In one line: you type a handle, greatfon.net receives it, hands it to a separate data supplier, which fetches that public account, and the result lands back in your tab. Each row of the table is one party, read across three columns.
| Part | Receives | Keeps | Never receives |
|---|---|---|---|
| Your browser | The handle you type. Profile data and clips (thumbnails included) from greatfon.net; photos direct from Instagram’s CDN. | “Your recent lookups”: the last 10 handles, this browser only. “Wipe list” empties it. | Your Instagram session: it plays no part. |
| greatfon.net | The page request and every lookup: the handle (also in the address bar, as /?u=), your IP and the result of a silent bot screen. Its server also relays clips and their thumbnails, avatars, saved files and the small cover image of every highlight. | No lookup log. Page addresses can reach routine host logs; request counts per IP live a few minutes for rate limits. | Any Instagram login. No field exists for one. |
| Data supplier (third party) | One handle with its request time, relayed by greatfon.net’s server. | Beyond this site’s reach. No guarantee from this page. | Your IP, your browser details, which site asked, cookies, whether you are signed in to Instagram. |
| Requests sent by the supplier; the photo requests from your tab, carrying your IP; greatfon.net is never named in them. | Not visible from here. Owner’s side: the viewer list may show an unrecognised account. | Your login. No account of yours gets used. |
Reading the Keeps column. Two rows carry an answer this page can stand behind. Your browser holds a short list that you control. greatfon.net holds no record of what you search. The supplier row stays open, because a promise about someone else’s server would be a guess.
The recent list, in detail. Browser storage, this browser, this site’s pages only. Never uploaded. In private browsing mode the list disappears with the window. Another browser or phone starts empty.
Failed lookups. An unused handle gets its own “not found” message from our server; any other failure shows a note and a countdown. No extra request goes out on your behalf.
Your IP address. greatfon.net gets it, and so does Instagram’s CDN whenever a photo loads, as for any web request; the supplier does not, because our server, not your browser, calls it. Your Instagram session plays no part in that exchange.
Instagram’s own rule. In the app, whoever is signed in owns the view: the story credits that account, and the poster sees it. For a lookup here, no account of yours gets used.
Not for: anyone who needs proof that nothing shows on the owner’s side. The owner may notice a view from an unrecognised account. That is the Instagram row, and no cell of it is in this page’s hands.
To test it on a profile you know, send one public handle through all four parts and open its Stories tab.
What loads for a public account
Per public profile, the supplier returns these parts:
- Stories: whatever is live at the moment of the lookup.
- Highlights: every set kept on the profile, as the supplier returns them, each clip playable on its own.
- Posts: the grid, most recent on top, extending on scroll to roughly 70, never the full history. Carousel slides arrive as separate cards.
- Reels: a separate tab.
- Video: grid videos play inside the page.
- Header: follower, following and post counts, plus the bio; the two follower counters bring up the opening batch of names on each list.
- Profile picture: full size in the viewer, downloadable.
- Captions: a first line under each card, the full text in the viewer, with like and comment counters; the comments open there too, read-only.
- Age: each item carries a “days ago” style stamp.
Left out by design: like, comment, reply and reaction buttons. Nothing tapped here reaches the account.
Saving works item by item, from the button under each one. File formats and the bulk-save question sit in Which Greatfon alternative fits your task?
Contrast: instagram.com signed out, in a desktop browser. Open a public profile there without logging in:
- Profile header: shown.
- Posts: a first batch, followed by a prompt offering more.
- Stories: a login screen straight away.
- Highlights: the row shows; a click on a set opens nothing.
That wall on stories is why a no-login page is useful for public profiles. Same handle on greatfon.net: public stories and highlights play with no sign-in.
Out of reach, for every viewer
Private accounts. Instagram shows stories and posts from a locked profile to accepted followers only. Non-followers: profile picture, bio, counters, nothing more. Owners will find the setting explained in Instagram’s help entry on private accounts.
On this page, such a profile gets no further than its header, Private label included; no counts are drawn and the tabs stay shut, with a note in their place. Instagram sets that lock; no viewer lifts it.
Lists and tabs greatfon.net never returns, public account or not:
- Story viewer lists. Those belong to the poster alone.
- Names behind a like count. The number shows; the people do not.
- Tagged tab. Not fetched; tagged accounts show only on the post itself.
- Close-friends-only stories. Limited by the poster to a chosen group.
Stories past their day. At 24 hours from upload, a story vanishes from public view; a copy pinned to a highlight stays, and the original moves to the poster’s archive when archiving is on. A lapsed one cannot be pulled back from here.
One commenter under a April 1, 2026 r/SocialMediaScheduling thread named one gap: none of the no-login sites they had found showed both the caption text and readable comments. That gap closes here: the full caption sits in the viewer, with comments a tap away.
Why do no-login viewers close down?
Each of the four parts can end a viewer. This is a reading with no figures behind it; nobody measured it.
- Instagram: a change in how public profiles are served can stall a supplier overnight, and every page relying on it stalls with it.
- Data supplier: it rations traffic, and a viewer then shows errors until the limit lifts. Here, a limit shows up as a message and a countdown, decoded in Is Greatfon down? Read the message first. The supplier also bills for every fetch, and a free page earns nothing from the lookup itself.
- greatfon.net, through its host and registrar: owners and rights holders send removal requests there, and either can act on them. This site takes them through its removal requests page.
- Your browser: no part in a closure. It only shows what the other three deliver.
So a viewer that worked last month proves nothing about today. One lookup of a large public account answers that faster than any review.
Red flags on any viewer
This list covers behaviour once a page has loaded. Close the tab at any of these:
- A handle that returns a profile you did not ask for, or a redirect to an unrelated product.
- An offer wall, a mini-game or a “prove you are human” survey standing in front of the result.
- A price for private access, whether as a fee, a trial or a subscription.
- Claims this page could never make: private accounts unlocked, story viewer lists revealed, total invisibility guaranteed.
- A password field, or an Instagram sign-in button. Public posts need no login of yours to be read.
- An app or browser extension to install before a single result appears.
A commenter in an r/selfimprovement thread about story viewers, started May 7, 2026, boiled the topic down to one rule: no app of this kind gets your login. It costs nothing to follow.
Password already handed to a site like that? Change it inside Instagram, look through the account’s login activity and security settings, and add a second login step through Instagram’s two-factor setting.
Lookup mechanics, six questions
Stories with no Instagram login: possible at all?
Yes, for public profiles. A page like this one has its server fetch them via an outside supplier. instagram.com itself puts a login screen in front of stories for signed-out visitors. A locked account opens for neither.
What does the story’s owner see after a lookup here?
No account of yours gets used for the lookup, and Instagram logs each story view to the account signed in at the moment it opens (state: September 24, 2026). Its owner may still get a view from an unrecognised account. Opening the same story in the app while signed in is a different case.
Can a viewer pull the following list of a locked account?
No. For a locked account neither list, followers or following, is returned here; for an open one you see the opening batch of each (state: October 13, 2026). On Instagram, what a locked profile shares, stories included, stays inside the circle of followers whose requests got a yes. Treat any tool promising that list with suspicion.
Highlights opened here: anonymous too?
Highlights outlast the 24-hour story window, and the route is the one a live story takes: the supplier finds each clip and greatfon.net’s server passes it on to your browser. No account of yours gets used here either. Even so, the poster may see a highlight view from an unrecognised account.
Does frequent browsing of one profile leave a count anywhere?
No visitor list for a profile appears on Instagram, however often someone returns. Single exception, story viewers: the poster gets their names. Pro accounts get insight totals, no names.
Once a story is opened in the app, can the view be hidden?
No. A view made while signed in is credited to that account. No action here reverses it. Lookups here are a separate route.
More notes
Kimberly Jung — Greatfon editor who date-stamps every note.