Telegram RegisterThe public register of Telegram
Telegram profile photo for DNSHE

Channel

DNSHE

@dnshecom

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

14,320subscribers

+261 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003258073004
TypeChannel
Username@dnshecom
Description这里是dnshe.com社区频道
Created1 December 2025measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live17 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/dnshecom

Growth

14,05914,32014,189.510 August 2026 — 14,059 subscribers10 August 2026 — 14,076 subscribers12 August 2026 — 14,161 subscribers13 August 2026 — 14,193 subscribers14 August 2026 — 14,225 subscribers16 August 2026 — 14,264 subscribers17 August 2026 — 14,320 subscribers10 August 202617 August 2026
7 measurements spanning 7 days, net +261. 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 14,020–14,359 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 13:0314,320+56
16 Aug 2026, 03:1814,264+39
14 Aug 2026, 11:4714,225+32
13 Aug 2026, 03:2414,193+32
12 Aug 2026, 00:3214,161+85
10 Aug 2026, 22:0614,076+17
10 Aug 2026, 16:3014,059first reading

Engagement

11 posts held, back to 1 December 2025the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 10 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
63.1%
avg views ÷ 14,320 subscribers
Avg views / post
9,030
1 post measured
Reaction rate
1.10%
reactions ÷ views · ER floor
Posts in window
1
of 11 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held11 (1 December 202510 August 2026)
Views total9,030
Reactions total99
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 06:57 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
1
Links
6

Lifetime counters from Telegram’s own channel header, read 18 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

504 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 59.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
30059.5%
👍14629.0%
👏326.35%
🔥112.18%
🥰71.39%
👀61.19%
👎20.397%

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 504reactions 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.

Recent posts

10 Aug 2026, 11:34 UTC≈9,030 views99 reactionsread 18 August 2026

DNSHE GitHub 项目 Star 突破 10,000 大关! 感谢广大开发者与用户一路以来的支持与厚爱!为庆祝 DNSHE 在 GitHub 上达成 10,000+ Stars 这一重要里程碑,我们特别推出限时感恩回馈福利! 全员福利送不停,两大重磅专属兑换码现已开启: 🎁 福利一:额外域名注册配额 兑换路径:进入官网系统 域名 -> 奖励中心 -> 额度兑换 兑换代码:github10000 专属奖励:输入即可额外获得 2 个域名注册配额。 🎁 福利二:域名升级永久代金券 兑换路径:进入官网系统 账户 -> 财务管理 -> 代金券兑换 兑换代码:GITHUB10000-WOK29U-7VGL2DPF 使用说明: 完成兑换后,前往 域名页面 -> 功能中心 -> 域名永久升级; 选择需要升级的域名(付费直升); 系统生成账单后,将自动抵扣相关费用。 ⚠️ 重要提醒:代金券有效期仅为 24 小时,请在兑换后尽快使用,切勿错

76👏22🔥1

11 Jul 2026, 02:06 UTC≈11,100 views36 reactionsread 18 August 2026

各位 DNSHE 用户:为了持续提供更加安全、稳定、便捷的域名服务,进一步完善平台生态建设,DNSHE 将于 2026 年 7 月 11 日 12:00(UTC+8) 起陆续上线新功能、恢复部分域名注册服务、新增合作域名,并持续推进平台生态建设。 本次更新内容如下: 一、免费邮箱服务即将上线,为了满足用户日常通信需求,DNSHE 即将推出免费邮箱服务。未来可注册并使用专属邮箱地址,例如[email protected]、在正式上线前,我们希望收集用户对于邮箱功能的建议。 您希望邮箱支持哪些功能?例如:邮箱别名,自动转发,邮箱转让,多邮箱管理或者其他实用功能欢迎通过社群或邮件向我们反馈。 邮箱注册方式及详细使用说明将在后续公告中发布。 二、de5.net 恢复注册 & DNSSEC 开放注册: 经过暂停注册期间的运行观察,de5.net 当前整体运行稳定。DNSHE 将于:2026 年 7 月 11 日 12:00(UTC+8)正式恢复 de5.

26👍8👏2

10 Jul 2026, 11:13 UTC≈8,190 views29 reactionsread 18 August 2026

DNSHE 服务升级公告:新功能上线、域名开放注册及社群招募计划 各位 DNSHE 用户:为了持续提供更加安全、稳定、便捷的域名服务,进一步完善平台生态建设,DNSHE 将于 2026 年 7 月 11 日 12:00(UTC+8)起陆续推出多项功能升级、恢复部分域名注册服务,并新增合作域名注册服务,同时正式启动社群志愿者招募计划。,并正式启动社群志愿者招募计划。现将本次更新内容公告如下: 一、系统优化与全新功能上线: 免费邮箱服务即将上线(欢迎提供建议) 为了满足用户日常通信需求,DNSHE 即将推出免费邮箱服务。 未来您可以注册并使用属于自己的专属邮箱地址,例如:[email protected] 在正式上线前,我们非常重视用户的意见与建议。关于邮箱功能,您最希望支持哪些特性?例如:邮箱别名,自动转发,邮箱转让,多邮箱管理或者其他实用功能欢迎通过社群回复或发送邮件向我们提出您的想法与需求。邮箱注册方式及详细使用说明,将在近期通过后续公告发布。

27🥰2

20 Jun 2026, 03:09 UTC≈11,200 views73 reactionsread 18 August 2026

尊敬的 DNSHE域名用户: 为持续提升平台的稳定性、安全性与使用体验,DNSHE 近期完成了多项系统升级与功能优化。同时,我们对免费域名注册规则、额度体系及奖励机制进行了调整。 现将本次更新内容公告如下: 🎨 界面与体验全面升级 全新页面设计:我们对平台前端界面进行了全面优化,整体视觉风格更加统一,交互逻辑更加清晰,操作体验更加流畅,为用户带来更直观、高效的管理体验。 DNS 与 API 性能优化: 本次升级重新梳理了 DNS 解析记录管理逻辑,并优化了后台处理流程。同时对 API 架构进行了深度重构,有效降低请求延迟,进一步提升高并发场景下的稳定性与响应速度。 🗑 自助删除域名功能优化(灰度开放): 为进一步提升域名管理体验,平台已灰度开放自助删除域名功能优化。 调整后,即使域名曾存在 DNS 解析记录历史,在满足删除条件的情况下,用户仍可直接自助删除域名。该功能目前正分批开放中,我们将持续观察运行情况,并逐步向所有用户开放

71🔥2

23 Apr 2026, 03:55 UTC≈19,000 views140 reactionsread 18 August 2026

DNSHE 平台运营模式与准入机制升级公告 各位 DNSHE 用户与朋友们: 自 DNSHE 成立以来,我们始终致力于为开发者提供稳定、公益的免费域名和解析服务。随着平台规模不断扩大,为了应对高强度的运维需求并确保核心资产的长期安全性,我们决定对平台的运营模式与准入机制进行全面升级。 🤝 强强联手:专业团队与站长协同管理 为保证 DNSHE 服务质量不因我个人精力受限(身体原因)而受到影响,平台现已正式引入全新专业技术团队共同参与管理。 双重保障:站长依然深度参与平台日常管理、核心决策及安全风控,确保 DNSHE 初心不改。 资源背书:特别感谢合作伙伴 DigitalOcean 与 AlphaVPS.com 提供的优质资源赞助,为平台稳健运行提供坚实底层基础设施。 🔐 准入机制调整:由 “开放注册” 转为 “邀请注册模式” 为降低钓鱼、诈骗,色情等恶意滥用行为风险,DNSHE 将于近日关闭开放注册,正式推行以下准入

👍9624👏8👀6🔥6

4 Feb 2026, 05:11 UTC≈16,400 views30 reactionsread 18 August 2026

致 DNSHE 全体用户: 经过与注册商的合规沟通,de5.net 及其子域名解析现已全面恢复。 为保障平台长期稳定,现调整如下: 服务恢复: 现有合规用户的解析记录已自动恢复,请检查业务状态。 暂停新注册: 即日起 de5.net 进入 180 天注册调整期,期间停止 de5.net 域名申请,后续开放时间视情况而定。 老用户保障: 已注册的存量用户不受影响,我们将继续提供解析与维护服务。 持续清理: 平台将常态化清理涉诈、钓鱼等违规子域名,请务必合规使用。 感谢您的耐心等待与支持。

23👍4🥰2👎1

24 Jan 2026, 12:24 UTC≈14,400 views37 reactionsread 18 August 2026

🎉 DNSHE 2026 新年活动公告 为迎接新年,DNSHE 现已开启限时福利活动。本次活动通过系统自动识别生效,全面优化域名资源分配,为您提供更广阔的域名服务。 📅 活动时间 2026 年 1 月 24 日 – 3 月 24 日 🌐 域名配额·全自动升级 为回馈长期支持的用户,平台将自动提升免费域名持有上限。 升级方案:域名配额由原 3 + 2配额用户自动上调至 5 + 5。 触发方式:活动期间,只需登录 DNSHE 域名管理控制面板 即可即时完成升级。 说明:升级过程由系统自动识别,无需人工申请或审核。 🔑 全新免费根域名(邀请注册制) 全新根域名资源已正式上线!为维护域名安全降低滥用风险,新域名采用邀请机制: 邀请码获取:登录账户后,进入 「域名注册邀请」 页面即可查看您的专属邀请码。 分享规则:邀请码可分享给可信任的好友使用,用于注册全新根域名。 风险提示:平台实行连带责任机制。若被邀请用户出现违规行为(如滥

👍2314

1 Jan 2026, 03:45 UTC≈9,120 views9 reactionsread 18 August 2026
Photo

Photo, posted without a caption

6🥰3

23 Dec 2025, 10:06 UTC≈8,110 views51 reactionsread 18 August 2026

【公告】服务全面恢复与 DNS 迁移补偿说明 尊敬的用户: 感谢您一直以来的支持与耐心等待。此前,根域名de5.net 域名因故受到封禁(HOLD),加之技术同步出现延迟,给您带来了不便,我们深表歉意。目前,域名状态已恢复正常。为感谢您的理解与陪伴,我们特别准备了专属补偿礼包,聊表心意。 🎁 专属补偿礼包详情: 补偿内容:域名注册配额 + 3 兑换码:DNSHE20251223 使用方式:登录 DNSHE 控制台 → 进入“域名管理页面” → 选择“兑换额度” 兑换码有效期:至2025-12-25 23:59(请您及时兑换,逾期将失效) ⚠️ DNS迁移说明:

33👍15🔥2👎1

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.

Citation-graph rank

Citation-graph rank — 499,395 of 1,549,376entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 August 2026 — this entry's latest reading, not the date you are reading this.

“DNSHE” (@dnshecom), 14,320 subscribers as measured 17 August 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.