Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 71% 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
60 measurements spanning 90 days, net +3,133. 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 106,022–112,364 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)
Subscribers
Change
3 Nov 2026, 20:45
111,628
-4
2 Nov 2026, 18:01
111,632
+43
1 Nov 2026, 21:25
111,589
+36
31 Oct 2026, 23:56
111,553
+240
30 Oct 2026, 21:36
111,313
+303
29 Oct 2026, 20:46
111,010
+256
28 Oct 2026, 21:38
110,754
+130
27 Oct 2026, 23:45
110,624
+498
26 Oct 2026, 21:55
110,126
+888
25 Oct 2026, 21:46
109,238
+761
24 Oct 2026, 18:57
108,477
+492
23 Oct 2026, 19:20
107,985
+269
22 Oct 2026, 18:55
107,716
+635
21 Oct 2026, 11:07
107,081
+242
20 Oct 2026, 09:36
106,839
-26
19 Oct 2026, 10:28
106,865
+2
18 Oct 2026, 11:49
106,863
+45
17 Oct 2026, 15:01
106,818
+40
16 Oct 2026, 17:57
106,778
-24
15 Oct 2026, 17:11
106,802
first reading
Engagement
508 posts held, back to 31 July 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 199 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
11.1%
avg views ÷ 111,628 subscribers
Avg views / post
12,400
212 posts measured
Reaction rate
1.64%
reactions ÷ views · ER floor
Posts in window
213
of 508 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
Window
Rolling 30 days · latest post in window 4 November 2026
Posts held
508 (31 July 2026 – 4 November 2026)
Views total
2,636,200
Reactions total
43,234
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
4 Nov 2026, 11:27 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
498
Videos
49
Links
630
Lifetime counters from Telegram’s own channel header, read 4 November 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.
Video runtime
22m 31s
Average length
1m 24s
Measured directly from 16 videos 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.
Reaction mix
119,601 reactions across 498 posts, in 69 distinct kinds. The most used accounts for 78.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
93,273
78.0%
👍
6,976
5.83%
❤🔥
4,604
3.85%
🔥
2,867
2.40%
👏
2,233
1.87%
🤣
1,666
1.39%
🍓
1,149
0.961%
🙏
962
0.804%
👎
747
0.625%
🕊
687
0.574%
😍
457
0.382%
😁
417
0.349%
💔
408
0.341%
💩
297
0.248%
🥰
282
0.236%
🫡
234
0.196%
🍾
226
0.189%
💘
195
0.163%
🤩
188
0.157%
⚡
164
0.137%
49 further kinds
1,569
1.31%
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 504 of the 508 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 121,522 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 508 most recent posts we hold, published 31 July 2026 to 4 November 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.
Telegram Stars
Stars received
771
across the posts below
Posts paid on
143
of 504 we hold a reading for · 28%
Most on one post
150
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @whitedns. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 508 most recent posts we hold for this entry, published 31 July 2026 to 4 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 73 of 213 posts held from the last 30 days (34.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
📥 دنبال ابزار مناسب برای دسترسی آزاد و امن به اینترنت هستی، اما نمیدونی کدومش به کارت میاد؟ 🤔
سایت WhiteDNS یه راهنمای فوقالعاده و ۱۰۰٪ رایگان براتون آماده کرده که بدون پیچیدگی، دقیقا دست میذاره روی نیاز شما! 💡
«چه کاری میخواهی انجام بدهی؟»
👇 این صفحه بهت کمک میکنه بر اساس نیازت، بهترین ابزار رو انتخاب کنی:
🔹 اتصال روزمره و مدیریت ساب؟ ➡️ WhiteVPN (با اشتراک داخلی و امکان اضافه کردن ساب شخصی)
🔹 تنظیم مسیرهای …
📢 اطلاعیه مهم:
از دسترس خارج شدن سرورهای عمومی
سلام به همه همراهان گرامی WhiteDNS 👋
به اطلاع میرسانیم که با توجه به شرایط ترافیکی اخیر و تصمیم تیم فنی، کلیه سرورهای عمومی و اضطراری قبلی (از جمله Soar، Cotton و MasterDNS) از دسترس خارج شدند.
علت این تصمیم:
این سرورها با ظرفیت و منابع محدود، صرفاً برای مواقع بحرانی و قطعیهای سراسری پیشبینی شده بودند؛ اما حجم بسیار بالای اتصالات همزمان و مصرف ترافیک سنگین بی مو…
🟢 پنل WhiteDNS نسخهٔ 0.14.2 منتشر شد
🔀 اتصال پایدارتر
سقف مقصد حالا برای هر حساب جداست؛ یک حساب پرمصرف راه Telegram یا CDN را برای بقیه نمیبندد. خرابی پراکسی یا قطع اینترنت سرور هم حسابها را قرنطینه نمیکند.
🌐 با DNS سالمتر
نامهای داخل دامنهٔ پنل دیگر REFUSED نمیگیرند. DNS روی پراکسی SOCKS5 بدون UDP هم با TCP کار میکند.
🔏 آپدیت امضاشده
از این نسخه به بعد، پنل فقط آپدیت دارای امضای آفلاین را نشان میدهد و نصب…
⭕️⭕️⭕️⭕️⭕️⭕️⭕️
سلام به همه همراهان گرامی 👋
یک نکته بسیار مهم درباره سرورهای عمومی و اضطراری Soar , cotton , masterdns کانال:
این سرورها صرفاً برای مواقع بحرانی، قطعیهای سراسری و اختلال شدید اینترنت فعال شدهاند تا دسترسی کاربران در لحظات ضروری به طور کامل قطع نشود.
منابع سختافزاری و پهنای باند این سرورها محدود است و متأسفانه به دلیل هجوم بالای اتصالات، در اکثر ساعات در وضعیت Overload (بار ترافیکی بیش از حد) قر…
🌐 وبسایت رسمی WhiteDNS 🤩
اگر برای انتخاب ابزار اتصال سردرگم هستید، نمیدانید کدام نسخه مناسب دستگاه شماست، یا نگران قطعی تلگرام و از دست رفتن دسترسی به کانفیگها هستید؛ وبسایت رسمی WhiteDNS همهٔ این نیازها را در یک نشانی سرراست و بدون فیلتر پاسخ میدهد:
🔗 https://whitedns.online
━━━━━━━━━━━━━━━━━━━━━
🔍 در این وبسایت چه کارهایی میتوانید انجام دهید؟
۱️⃣ انتخاب و دانلود ابزار متناسب با دستگاه شما (بدون سردرگمی)
…
نصب و راهاندازی WhiteDNS فقط با یک ربات تلگرامی!😌
توی این آموزش یاد میگیریم چطور با ربات WhiteDNS Server Manager سرورمون رو راهاندازی کنیم، پنل رو نصب کنیم و کانفیگ بسازیم. در ادامه هم اتصال با Resolverهای جدید و راهاندازی پروکسی تلگرام رو تست میکنیم! 🥹✨
🎬تماشا در یوتیوب : https://youtu.be/YrIX1YxRxf0
·:¨༺ @BlueKnight_Net ༻¨:·
🚀 نصب پنل WhiteDNS در چند دقیقه، فقط با یک ربات تلگرام
@WhitednsServerManagementbot
بدون ترمینال، بدون دستور دستی. ربات روی سرور شما پنل را نصب، تعمیر و حذف میکند و رکوردهای کلودفلر را هم خودش میسازد.
📋 پیشنیاز
• سرور Ubuntu 22/24/26 یا Debian 12/13 (amd64 یا arm64)
• یک IPv4 عمومی و دسترسی root (یا sudo)
• پورتهای ۵۳ (UDP/TCP) و ۸۰ و ۴۴۳ باز در فایروال پرووایدر
• یک دامنه در کلودفلر
🧭 روش کار
1️⃣ ربات را باز…
آخرین پیامهای کانال تلگرام در وبسایت whitedns🔥
مشاهده و دسترسی به ۵۰ پیام اخیر کانال رسمی WhiteDNS از طریق مرورگر 🌐؛ شامل اطلاعیهها، انتشارهای جدید، هشدارهای وضعیت شبکه، آموزشها و کانفیگهای عمومی برای مواقعی که تلگرام شما دچار اختلال است.
@whitedns
https://whitedns.online/feed/
🔍 ابزار WhiteDNS Clean IP Finder؛ کشف آیپی تمیز و اسکن پیشرفته
پروژه WhiteDNS Clean IP Finder ابزاری با هسته سریع Go برای یافتن آیپیهای تمیز، بررسی TLS/SNI و اعتبارسنجی پراکسی در شرایط فیلترینگ است.
امکانات کلیدی:
اسکن IP و CIDR: سنجش تاخیر واقعی نودها و دور زدن اختلالات •
اسکنر DNS Resolver: تست DoH/DoT با uTLS و ضد مسمومیت DNS •
تست پراکسی: اعتبارسنجی پراکسیهای HTTP و SOCKS5 •
دستهبندی ASN: استخراج تارگتهای…
❤170🔥16❤🔥6🙏6🕊4👍3💯2🤩2
Showing the 12 most recent of 508 posts we hold for @whitedns. 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.
Posts edited after publishing
@whitedns edited 20 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
16 August 2026
Most recent edit
30 October 2026
Posts recorded as deleted after publishing
We recorded 24 posts on @whitedns as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
23 August 2026
Most recent seen missing
1 November 2026
Median time before seen missing
20 hours
Seen missing in the last 30 days
7
Polls
The 6 most recent of 13 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
The shares total 107%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
The shares total 110%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
دوستان
لطف کنید اول این فایل ها را ذخیره کنید بعد از قسمت پروفابل - افزودن- amneziaWG -وارد کردن فایل پیکربندی این فایل را وارد کنید و امتحان کنید که ایا وصل میشید یا نه
بله38%
خیر62%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
The shares total 168%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 508 most recent posts we hold, published 31 July 2026 to 4 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Mentions
Named by 59 registered channels — 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@whitedns named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@whitevpn named in 5 posts, 8 August 2026 – 4 October 2026
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 3 November 2026 — this
entry's latest reading, not the date you are reading this.
“White DNS” (@whitedns), 111,628 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/whitedns.
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.