Fix connection errors
❤60🤬41👍9

Channel
@khoinDNS
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
31,672subscribers
+2,463 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1003204609553 |
|---|---|
| Type | Channel |
| Username | @khoinDNS |
| Created | Between 1 October 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/khoinDNS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 15:48 | 31,672 | +81 |
| 1 Sept 2026, 14:35 | 31,591 | +97 |
| 31 Aug 2026, 12:04 | 31,494 | +104 |
| 30 Aug 2026, 10:47 | 31,390 | +118 |
| 29 Aug 2026, 07:55 | 31,272 | +82 |
| 28 Aug 2026, 08:14 | 31,190 | +118 |
| 27 Aug 2026, 09:35 | 31,072 | +100 |
| 26 Aug 2026, 11:33 | 30,972 | +105 |
| 25 Aug 2026, 13:22 | 30,867 | +77 |
| 24 Aug 2026, 15:56 | 30,790 | +129 |
| 23 Aug 2026, 00:13 | 30,661 | +116 |
| 21 Aug 2026, 14:37 | 30,545 | +82 |
| 20 Aug 2026, 14:57 | 30,463 | +117 |
| 19 Aug 2026, 12:15 | 30,346 | +114 |
| 18 Aug 2026, 09:33 | 30,232 | +88 |
| 17 Aug 2026, 12:33 | 30,144 | +111 |
| 16 Aug 2026, 03:49 | 30,033 | +185 |
| 14 Aug 2026, 17:15 | 29,848 | +219 |
| 13 Aug 2026, 04:05 | 29,629 | +75 |
| 12 Aug 2026, 07:12 | 29,554 | first reading |
18 posts held, back to 7 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 54 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 18 (7 May 2026 – 22 August 2026) |
| Views total | 50,150 |
| Reactions total | 419 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 08:37 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
3,328 reactions across 17 posts, in 33 distinct kinds. The most used accounts for 33.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,112 | 33.4% | |
| 🤬 | 607 | 18.2% | |
| 👎 | 563 | 16.9% | |
| 💔 | 154 | 4.63% | |
| 🖕 | 133 | 4.00% | |
| 👍 | 119 | 3.58% | |
| 🔥 | 111 | 3.34% | |
| 😭 | 101 | 3.03% | |
| 💩 | 85 | 2.55% | |
| 😢 | 67 | 2.01% | |
| ❤🔥 | 46 | 1.38% | |
| 🤮 | 44 | 1.32% | |
| 👏 | 22 | 0.661% | |
| 🤣 | 20 | 0.601% | |
| 🍓 | 17 | 0.511% | |
| 💘 | 16 | 0.481% | |
| 🆒 | 15 | 0.451% | |
| 😁 | 12 | 0.361% | |
| 🍾 | 11 | 0.331% | |
| 💋 | 10 | 0.3% | |
| 13 further kinds | 63 | 1.89% |
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 17 of the 18 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 3,328 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 7 May 2026 to 22 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.
Fix connection errors
❤60🤬41👍9
New cert Name: HSBC Bank plc Status: 🟢 Active Websiste khoindvn.io.vn
❤56💩28❤🔥15👎13🔥11👏6😁3
EN : New cert revoke VI : Chứng chỉ mới đã bị thu hồi CENTRAL POWER INFORMATION TECHNOLOGY COMPANY - POWER CORPORATION EN : Ensure the VPN device is configured as shown in the second image. The VPN should be disconnected and the DNS set to "Anti-Revoke"; only then should you proceed to install the app from khoindvn.io.vn. It is best to remove all DNS settings from your device and reconfigure the DNS according to t…
❤87👎73👍9😱7🔥1
Channel KhoinDNS - Esign Bypass Revoke pinned «Group chat Link»
Group chat Link
🤬79❤33👎13🖕6🍾5
If you are using DNS, absolutely do not use a VPN and avoid restarting your device. If you do, the certificate will work stably after you successfully install the application.
👎150❤56🤬44😢23💘12😈3
Fixed a crash that occurred after agreeing to the terms in the ESign app. If you encounter any other issues, please continue to report them. @depzaisix A revoked certificate doesn’t install successfully for everyone. Please keep in mind that DNS revocation blocking isn’t 100% reliable—it’s roughly a 50/50 chance, not a guarantee. Đã khắc phục sự cố gây ra lỗi ứng dụng bị sập sau khi đồng ý với các điều khoản trong…
❤80🤬77💩53👎47🍓17👍4👏3
If you encounter any errors or problems while using the ESign template, please let me know so I can fix them. Nếu bạn gặp bất kỳ lỗi hoặc sự cố nào khi sử dụng ESign, vui lòng cho tôi biết để tôi có thể khắc phục. @depzaisix
🖕87❤37👍11❤🔥7🤡2
Please ensure you are using our DNS correctly. This is an important file. No VPN
🤬57❤18🔥7😭6❤🔥5🆒4👍2🥰2
I just found a recently revoked certificate. Please try downloading it and see if the download is successful. A revoked certificate doesn’t install successfully for everyone. Please keep in mind that DNS revocation blocking isn’t 100% reliable—it’s roughly a 50/50 chance, not a guarantee. Mình vừa tìm thấy một chứng chỉ mới bị thu hồi gần đây. Vui lòng thử tải xuống và xem quá trình tải có thành công hay không. Ch…
🤬55❤49👍15👎13❤🔥9
EN : New cert VI : Chứng chỉ mới VIETNAM AIRLINES JSC EN : Before installation, please ensure you are using our DNS server at khoindvn.io.vn and not a VPN or other DNS service. VI : Trước khi cài đặt, vui lòng đảm bảo bạn đang sử dụng máy chủ DNS của chúng tôi tại khoindvn.io.vn chứ không phải VPN hoặc dịch vụ DNS khác.
❤105👎52💋10💔10👍9😡6👏3😁2
EN : New cert VI : Chứng chỉ mới China Telecom Corporation Limited EN : Before installation, please ensure you are using our DNS server at khoindvn.io.vn and not a VPN or other DNS service. VI : Trước khi cài đặt, vui lòng đảm bảo bạn đang sử dụng máy chủ DNS của chúng tôi tại khoindvn.io.vn chứ không phải VPN hoặc dịch vụ DNS khác.
❤105👎28🤬11🆒11🔥8🍌4💩4💘3
Showing the 12 most recent of 18 posts we hold for @khoinDNS. 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 — 841,353 of 1,629,571 entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“Channel KhoinDNS - Esign Bypass Revoke” (@khoinDNS), 31,672 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/khoinDNS.
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.