Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 why it has no browse page of its own yet.
Growth
29 measurements spanning 38 days, net +847. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 13,932–15,033 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)
Subscribers
Change
17 Sept 2026, 15:38
14,906
+62
15 Sept 2026, 10:40
14,844
+18
13 Sept 2026, 16:21
14,826
+28
11 Sept 2026, 19:01
14,798
+45
9 Sept 2026, 03:59
14,753
+30
5 Sept 2026, 20:01
14,723
+27
3 Sept 2026, 17:40
14,696
+17
2 Sept 2026, 08:42
14,679
+10
1 Sept 2026, 09:33
14,669
+31
31 Aug 2026, 06:44
14,638
+29
30 Aug 2026, 07:37
14,609
+32
29 Aug 2026, 07:38
14,577
+26
28 Aug 2026, 05:25
14,551
+14
27 Aug 2026, 07:23
14,537
+18
26 Aug 2026, 07:33
14,519
+29
25 Aug 2026, 05:39
14,490
+21
24 Aug 2026, 06:42
14,469
+22
22 Aug 2026, 15:13
14,447
+37
21 Aug 2026, 07:02
14,410
+26
20 Aug 2026, 08:15
14,384
first reading
Engagement
11 posts held, back to 1 December 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 38 pages 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 11 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
523 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 60.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
315
60.2%
👍
146
27.9%
👏
36
6.88%
🔥
11
2.10%
🥰
7
1.34%
👀
6
1.15%
👎
2
0.382%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 9 of the 11 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 523 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 1 December 2025 to 10 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
尊敬的 DNSHE域名用户：
为持续提升平台的稳定性、安全性与使用体验，DNSHE 近期完成了多项系统升级与功能优化。同时，我们对免费域名注册规则、额度体系及奖励机制进行了调整。
现将本次更新内容公告如下：
🎨 界面与体验全面升级
全新页面设计：我们对平台前端界面进行了全面优化，整体视觉风格更加统一，交互逻辑更加清晰，操作体验更加流畅，为用户带来更直观、高效的管理体验。
DNS 与 API 性能优化：
本次升级重新梳理了 DNS 解析记录管理逻辑，并优化了后台处理流程。同时对 API 架构进行了深度重构，有效降低请求延迟，进一步提升高并发场景下的稳定性与响应速度。
🗑 自助删除域名功能优化（灰度开放）:
为进一步提升域名管理体验，平台已灰度开放自助删除域名功能优化。
调整后，即使域名曾存在 DNS 解析记录历史，在满足删除条件的情况下，用户仍可直接自助删除域名。该功能目前正分批开放中，我们将持续观察运行情况，并逐步向所有用户开放…
Showing the 11 most recent of 11 posts we hold for @dnshecom. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“DNSHE” (@dnshecom), 14,906 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/dnshecom.
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.
