File, posted without a caption
❤46❤🔥6🔥1🤔1

Channel
@whitedns
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Cite this entry
107,270subscribers
-1,225 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1003782242446 |
|---|---|
| Type | Channel |
| Username | @whitedns |
| Description | گروه : t.me/whitedns_group ادمين : @WhiteDnsChatBot |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/whitedns |
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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 15:39 | 107,270 | -98 |
| 15 Sept 2026, 14:59 | 107,368 | -130 |
| 13 Sept 2026, 22:40 | 107,498 | -130 |
| 12 Sept 2026, 06:21 | 107,628 | -126 |
| 9 Sept 2026, 21:37 | 107,754 | -46 |
| 6 Sept 2026, 13:01 | 107,800 | -108 |
| 4 Sept 2026, 06:20 | 107,908 | -14 |
| 2 Sept 2026, 20:54 | 107,922 | -38 |
| 1 Sept 2026, 16:13 | 107,960 | -58 |
| 31 Aug 2026, 18:29 | 108,018 | -190 |
| 30 Aug 2026, 19:28 | 108,208 | +231 |
| 29 Aug 2026, 19:35 | 107,977 | -31 |
| 28 Aug 2026, 21:44 | 108,008 | -64 |
| 27 Aug 2026, 20:44 | 108,072 | -41 |
| 26 Aug 2026, 20:12 | 108,113 | -83 |
| 25 Aug 2026, 22:38 | 108,196 | -13 |
| 24 Aug 2026, 21:05 | 108,209 | -66 |
| 23 Aug 2026, 06:12 | 108,275 | -75 |
| 21 Aug 2026, 17:38 | 108,350 | -79 |
| 20 Aug 2026, 14:54 | 108,429 | first reading |
234 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 102 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 19 September 2026 |
|---|---|
| Posts held | 234 (31 July 2026 – 19 September 2026) |
| Views total | 1,912,370 |
| Reactions total | 34,963 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Sept 2026, 06:03 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.
Lifetime counters from Telegram’s own channel header, read 20 September 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.
Measured directly from 10 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.
62,368 reactions across 225 posts, in 61 distinct kinds. The most used accounts for 79.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 49,609 | 79.5% | |
| 👍 | 3,861 | 6.19% | |
| 🔥 | 1,787 | 2.87% | |
| ❤🔥 | 1,744 | 2.80% | |
| 👏 | 1,428 | 2.29% | |
| 🙏 | 369 | 0.592% | |
| 😁 | 346 | 0.555% | |
| 😍 | 344 | 0.552% | |
| 🍓 | 334 | 0.536% | |
| 💩 | 297 | 0.476% | |
| 👎 | 268 | 0.43% | |
| 🕊 | 239 | 0.383% | |
| 🥰 | 199 | 0.319% | |
| 🍾 | 187 | 0.3% | |
| 🤣 | 154 | 0.247% | |
| 💘 | 138 | 0.221% | |
| 🤩 | 135 | 0.216% | |
| 🤡 | 114 | 0.183% | |
| 🦄 | 81 | 0.13% | |
| 🤝 | 70 | 0.112% | |
| 41 further kinds | 664 | 1.06% |
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 231 of the 234 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 64,289 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 234 most recent posts we hold, published 31 July 2026 to 19 September 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.
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 234 most recent posts we hold for this entry, published 31 July 2026 to 19 September 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.
File, posted without a caption
❤46❤🔥6🔥1🤔1
🍓 بچههااا یه آموزش جدید آپلود کردم 🥹✨ اگه Gemini خطای 403 میده یا Google Flow براتون باز نمیشه، این ویدیو رو از دست ندین 👀💗 توی ویدیو از صفر Blue Knight Panel رو میسازیم و آخرش با کانفیگهاش Gemini و Google Flow رو تست میکنیم 😭🔥 🎀 تماشای ویدیو: https://youtu.be/GK2PGDzkbh4
❤88❤🔥11💊1
File, posted without a caption
❤244👍21🥰8👏4🍓3🍾3👎3🕊3
WhiteAesther Mobile 1.9.3 — نسخه پایدار🔥 نسخه پایدار 1.9.3 منتشر شد. برای بهروزرسانی میتوانید از قابلیت جدید داخل اپ استفاده کنید یا فایل را مستقیماً روی نسخه فعلی نصب کنید. برنامه را حذف نکنید تا هویت و تنظیماتتان حفظ شوند. قابلیتهای جدید آپدیت مستقیم از داخل اپ کارت «نسخه جدید منتشر شده» حالا میتواند فایل بهروزرسانی را دانلود و نصب کند. این قابلیت فقط زمانی فعال است که: پوشش اتصال روی «کل دستگاه» باشد. فایل ب…
❤177👍13👎3🦄3😍3👏2💅2🔥2
🚀;کاتن روتر چیست؟ کاتن روتر یک ابزار سبک برای مدیریت چند سرویس DNS Tunnel روی یک سرور است. خیلی ساده بخواهیم بگوییم: فرض کنید چند سرویس مختلف دارید، اما فقط یک سرور و یک IP در اختیار دارید. CottenRouter درخواستها را دریافت میکند و بر اساس دامنه، هر درخواست را به سرویس مربوطه میفرستد. یعنی چند سرویس میتوانند از یک IP و پورت عمومی ۵۳ استفاده کنند. ⚠️ توجه: CottenRouter خودش VPN یا تونل ایجاد نمیکند؛ بلکه سرویسهای…
❤131👏12❤🔥6💘5🍓3🕊2🍾1👎1
🚀 نسخه CottenRouter v1.2.13 منتشر شد! سریعتر، پایدارتر و آماده برای ترافیک سنگین ⚡️ • رفع مشکلات نصب SlipGate روی سرورهای تازه • جلوگیری از Down شدن Router هنگام قطع نصب یا SSH • رفع تداخل Domain و Port بین Backendها • امنیت بهتر CottenDNS و StormDNS 0٪ Query Loss در تست ۵۱۲ کلاینت همزمان • پردازش بیش از ۲۲K Query/s • بهبود TUI، خطاها و سیستم Purge ✅ آپدیت مستقیم بدون حذف Routeها، Backendها و تنظیمات قبلی 💻 GitHub …
❤133👍14🥰3❤🔥2🕊2🍾1👎1👏1
Whiteaesther moblie pre-release 1.8.1 ⚠️ این نسخه برای کاربرانی هست که توی چند روز گذشته اختلال شدید گزارش کردند و نسخه آخر هم مشکل انها را حل نکرد برخلاف باور غلط عمومی ورژن ها در حال بدتر شدن نیستند بلکه امکانات بیشتری در حال اضافه شدن است - اما به دلیل گستردگی کاربران ما مجبوریم حداکثر بومی سازی را انجام بدهیم که این کار گاها زمان بر خواهد بود . اگر روی ورژن قبلی مشکلی ندارید فعلا اپدیت نکنید !!!!⚠️⚠️⚠️ دو اص…
❤169👍16❤🔥3👏3💘2🍾1🏆1💅1
😎 دیگه لازم نیست برای آپدیت از اپ خارج بشید. اپ اتوماتیک ورژن جدید رو دانلود و نصب میکنه. این به کسایی که اطلاعات فنی هم ندارن کمک میکنه.
❤302👍35💯8🍓4🍾3👎3❤🔥2💅2
🛡 انتشار نسخه جدید WhiteVPN 1.6.8 تغییرات نسخه جدید: 🟢 ویجت صفحهٔ اصلی برای اتصال، قطع اتصال و نمایش وضعیت VPN 🟢 بهروزرسانی از داخل برنامه، با نمایش پیشرفت دانلود، امکان رد کردن یک نسخه و بررسی صحت فایل و امضا پیش از نصب 🟢 اجرای Real Delay Test و تست سرعت در پسزمینه و هنگام خاموش بودن صفحه 📱 دانلود از گیتهاب
❤265👏12🔥11😍8👍5❤🔥4🍓2💅2
موقت : ⚠️ تعدادی از کابران گزارش دادند که توی استفاده از ورژن اخر whiteaesther دچار مشکل شدند . برای همین یک سری اصلاحیه زدیم و به زودی ورژن ازمایشی را منتشر میکنیم ممنون
❤73👍7😁5❤🔥4🔥2💘1🤝1
⭐️چطور API رایگان DeepSeek V4.1 Flash بگیریم؟ توی این ویدیو، قدمبهقدم نشون میدم چطور به API این مدل دسترسی رایگان بگیرید؛ اگه با API آشنا نیستید، خیلی ساده یعنی بهجای اینکه فقط توی سایت با هوش مصنوعی چت کنید، بتونید ازش داخل برنامهها و ابزارهای خودتون استفاده کنید. چه بخواید ایدهای رو تست کنید، چه روی یک پروژهٔ شخصی کار کنید یا تازه کار با API رو یاد بگیرید، این آموزش میتونه نقطهٔ شروع خوبی باشه. 📹 تماشا و…
❤189👍23🍓14🤣6🍾1👎1👏1💘1
✍️موقت دوستان هم نسخه مبایل و هم دسکتاپ برای کارایی بهتر اول ورژن قدیمی را uninstall کنید و بعد نسخه جدید را نصب کنید در نسخه ویندوز موقع uninstall کردن حتما گزینه delete app data را بزنید ممنون
❤219👍25🔥4🦄3👏2💘2🥰2👎1
Showing the 12 most recent of 234 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@whitedns edited 8 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.
The 5 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.
امشب ساعت 8 به وقت ایران لایو بگذاریم جواب سوالات را بدیم ؟
Shares as published. No per-option vote count is published by Telegram, so none is shown.
توی این نسخه ازمایشی whiteaesther مشکل شما برای اتصال و استفاده از هوش مصنوعی حل شد ؟
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
سرور های اختصاصی براتون وصل میشن؟
Shares as published. No per-option vote count is published by Telegram, so none is shown.
محدودیت حجم کانفیگ ربات را از 1 گیگ به چقدر تغییر بدیم که برای انجام کارهای روزمره کافی باشه ؟ 👀
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
با whitevpn desktop وصل هستید ؟
The shares total 104%, 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.
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 234 most recent posts we hold, published 31 July 2026 to 19 September 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.
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.
Named by 49 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@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.
References a handle that is not a live channel — we have no record it ever was one.
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.
“White DNS” (@whitedns), 107,270 subscribers as measured 17 September 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.