What each status means, why it lags, how not to dramatize it.
Online, redirect, offline — index words, not a verdict
TON Web Search cards may show statuses like online, redirect, offline. That’s a crawl snapshot: what the indexer saw at check time. It is not a honesty certificate and not a promise the entry stays the same tomorrow.
Online means “answered”. Redirect often lands in Telegram — convenient, but still verify the final username. Offline means “no answer now” — the name may be dead, sleeping, or just unreachable from the crawl point.
How to read a card
Look at type, status, name. Compare 2–3 lookalikes. Open a candidate slowly. Match the pin if the brand is known. For unknowns — experimental wallet and minimal action size.
Index delay is normal: seasons change storefronts faster than any catalog. If a card was online yesterday and empty today — trust your eyes, not memory.
What status doesn’t do
Doesn’t guarantee yield. Doesn’t vouch for a team. Doesn’t replace reading a signature. Doesn’t cancel phishing on the next click. Use filters to browse less junk — and keep skepticism.
---
Why “status” shows up exactly when you rush
“Catalog statuses: online, redirect, offline without magic” usually matters not on a calm Sunday night, but when the feed screams urgency. Hands outrun eyes. This block is intentionally slow: contour first, button second.
Frame in short: What each status means, why it lags, how not to dramatize it. If someone sells that frame as guaranteed yield — different genre, not a manual.
Telegram is almost always nearby: channel, bot, Mini App, DM. Distribution is fast — clones too. Any step on “status” starts with where the entry came from and which wallet is active.
A risk map for the “status” scenario
Risks around “status” mix technical and social. Technical: address, memo, network, spender, DNS. Social: “admin”, referral, urgent timer, comment screenshot. Different habits, one stop — Confirm.
Device risk: clipboard trojan, chat apk, screen share with seed in frame. If the hardware already feels foreign, “status” can wait; clean key contour first.
Money ceiling: an amount you can lose on a UI mistake without shame. Without a ceiling every guide becomes theater.
A no-heroics walkthrough — “status” focus
Reference entry → favorites → experimental wallet → read preview → dust → history check → size. Skipping dust “because the site looks familiar” is the costliest minute saved in “status”.
At preview, say aloud: action type, spender/recipient, amount. If your tongue trips — too early. Cancel doesn’t make you “not degen”; it leaves you tomorrow.
Private log: link/bot, time, tx. Season memory lies. Logs don’t.
How the catalog helps (and doesn’t) with “status”
TON Web Search next to “status” helps find a storefront and compare lookalikes. Card statuses are snapshots. Don’t read the index as an audit. Matching a brand pin is mandatory when a brand exists.
Filters remove noise. They don’t remove signature responsibility. If a card is offline — don’t grab a comment “mirror”; only an official entry-change announce.
A week after reading about “status”
One rule for seven days, tied to “status”. Example: no favorite, no entry; no dust, no large tap; no global brand username hunt. Check the rule at night — yes/no.
Review: approvals, bookmarks, junk tokens, client update from an official source. Seed offline. Main and experimental contours split. Then “Catalog statuses: online, redirect, offline without magic” becomes daily life, not a quest.