24 Jun 2026, 09:05 UTC32 viewsread 13 August 2026
有需要联系客服 @yunanquan101
Channel
域名防红_浏览器防红_域名防红_域名防封_微信防红
@gu661
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
122subscribers
+120 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002263828109 |
|---|---|
| Type | Channel |
| Username | @gu661 |
| Created | 30 November 2024 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 28 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 28 October 2026 |
| On Telegram | t.me/gu661 |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 25 September 2026 and assigned it the closest of 31 fixed categories, at 54% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 02:55 | 122 | -2 |
| 13 Oct 2026, 07:37 | 124 | -30 |
| 18 Sept 2026, 13:42 | 154 | +150 |
| 10 Sept 2026, 08:56 | 4 | +1 |
| 17 Aug 2026, 15:45 | 3 | +1 |
| 13 Aug 2026, 23:34 | 2 | no change |
| 9 Aug 2026, 06:15 | 2 | first reading |
Engagement
4 posts held, back to 30 November 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 4 posts for this entry, the most recent from 24 June 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
24 Jun 2026, 09:05 UTC31 viewsread 13 August 2026
😩🥶😭😤😡😠😖😳👽🎃😽🤑 ☹️☹️☹️☹️☹️☹️☹️ 🔠⚡️Ai云全网无对手⚡️🔠 1️⃣域名防红国外版：针对海外谷歌检测支持（tk海外市场专用支持自定义域名） 不报红📱📱📱📱 2️⃣域名防红国内：支持多版，掴内主流浏览器、华为、vivo、qq浏览器、oppo、小米等⚡️ 3️⃣域名防屏蔽国内：支持掴内各大地区的屏蔽例如、江浙沪、福建等地区屏蔽域名可以⚡️ 4️⃣QQ微信防红📱📱：适合场所-客服、打印快递、app下载等。 5️⃣APK报毒处理、可过市面上99%的机型、后台全自动处理、无需人工看守 6️⃣CDN加速防御、AI智能防御、全球高速访问、专治防不住、专治打不死、前天24小时帮您防御、同时也帮您攻击您的同行
24 Jun 2026, 09:04 UTC29 viewsread 13 August 2026
专业 域名防劫持_不死域名_域名防拦截_域名反诈_防红系统【浏览器屏蔽、劫持、污染、反诈、0.0.0.0、127.0.0.1】等域名防红项目，💯独立开发🌈无视任何投诉举报🌱防运营商拦截屏蔽劫持。💥 可根据你的情况定制防红，包你满意💯，用的满意还可买断系统！
30 Nov 2024, 15:03 UTCviews —
Channel created
Showing the 4 most recent of 4 posts we hold for @gu661. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 28 October 2026 — this entry's latest reading, not the date you are reading this.
“域名防红_浏览器防红_域名防红_域名防封_微信防红” (@gu661), 122 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/gu661.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.