Telegram RegisterThe public register of Telegram
Telegram profile photo for Web Application Security

Channel

Web Application Security

@web_appsec

Not marked by Telegram, checked 29 August 2026

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Telegram's recommendations · Cite this entry

1,771subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002227270380
TypeChannel
Username@web_appsec
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/web_appsec

Growth

1,7691,7741,771.57 August 2026 — 1,773 subscribers7 August 2026 — 1,773 subscribers8 August 2026 — 1,772 subscribers11 August 2026 — 1,773 subscribers14 August 2026 — 1,771 subscribers18 August 2026 — 1,773 subscribers21 August 2026 — 1,774 subscribers24 August 2026 — 1,773 subscribers27 August 2026 — 1,771 subscribers30 August 2026 — 1,769 subscribers2 September 2026 — 1,771 subscribers1,7717 August 20262 September 2026
11 measurements spanning 26 days, net -2. 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 1,768–1,775 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 14:331,771+2
30 Aug 2026, 12:271,769-2
27 Aug 2026, 12:141,771-2
24 Aug 2026, 20:321,773-1
21 Aug 2026, 13:551,774+1
18 Aug 2026, 03:111,773+2
14 Aug 2026, 18:391,771-2
11 Aug 2026, 05:381,773+1
8 Aug 2026, 01:311,772-1
7 Aug 2026, 15:481,773no change
7 Aug 2026, 13:331,773first reading

Engagement

19 posts held, back to 13 July 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 19 posts for this entry, the most recent from 11 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 00s
Average length
3m 00s

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.

Reaction mix

584 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 66.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
38666.1%
👍11419.5%
🔥7512.8%
👎91.54%

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 19 of the 19 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 584 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 13 July 2025 to 11 July 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

11 Jul 2026, 18:35 UTC577 views29 reactionsread 7 August 2026

رایتاپ آسیب پذیری Improper Access Control چند تا Subdomain عمومی از تارگت داشتم که یکیش API بود. با استفاده از waybackurls به مسیر های زیر رسیدم. /portal/admin/login /portal/panel دومی بنظرم جذاب تر میومد چون به پنل مدیریت اشاره میکرد. خود صفحه 404 میداد و تصمیم گرفتم Fuzz بندازم. چندین مسیر مختلف پیدا شد که همشون 403 میدادن و یکیش categories/ بود. برگشتم به portal/admin/login/ و طبق عادت login/ رو از URL به regist

👍18🔥74

Signed Alireza

2 Jul 2026, 11:30 UTC≈1,040 views66 reactionsread 7 August 2026

مالیات جوانی پرداخت شد. پایان احترام گذاشتن به کسایی که لیاقتشو نداشتن. بعد یه ریکاوری فعالیت کانال به روال قبل برمیگرده.

55👍7👎4

Signed Alireza

22 Jun 2026, 04:34 UTC≈1,640 views20 reactionsread 7 August 2026
File

File, posted without a caption

16👍4

Signed Alireza

22 Jun 2026, 04:34 UTC≈1,530 views18 reactionsread 7 August 2026

بعد یه مدت طولانی رو یه تارگت ایرانی کار میکردم، یه قسمت برای File Upload داشت که PDF هم قبول میکرد، قبلا یه PDF آماده برای تست XSS داشتم. چند تا مشکل وجود داشت، فقط روی Google Chrome کار میکرد و Checker Function وقتی به کلمه JS و JavaScript میرسید واکنش نشون میداد و عملا جلوی آسیب پذیری گرفته میشد. با یکم تحقیق تونستم با استفاده از OpenAction روی Firefox و سایر مرورگرا هم کدم رو اجرا کنم. برای بایپس WAF هم کلمه های

16👍2

Signed Alireza

3 Jan 2026, 18:12 UTC≈2,940 views34 reactionsread 7 August 2026

نظریه شخصی : با مطالعه درباره گذشته امنیت سایبری، متوجه میشیم که از اوایل به وجود آمدن اسکنر های آسیب پذیری تا نهایتا سال 2014, 2015 ، اسکنر ها نتایج خیلی مطلوبی داشتند و میشد روی ابزار ها حساب باز کرد. بعدش کم‌کم با تغییر تکنولوژی ها و پیدایش آسیب پذیری های جدید و سخت، اسکنر ها کارایی قبلی رو از دست دادن و تست نفوذ دستی ارزش پیدا کرد. حالا دوباره طی این یکی دوسال، روند قبلی تکرار شده و ترکیب AI + اسکنر داره نتیجه مط

👍235👎4🔥2

Signed Alireza

2 Jan 2026, 18:23 UTC≈2,240 views25 reactionsread 7 August 2026
Photo

رایتاپ ارسالی از دوستان

👍1310🔥2

Signed Alireza

30 Dec 2025, 18:29 UTC≈2,170 views31 reactionsread 7 August 2026

جاهایی که سامانه از regex استفاده میکنه، میتونیم آسیب پذیری regex dos یا redos رو تست کنیم. برای مثال سامانه یک ایمیل از کاربر میگیره و با regex معتبر بودن آن رو چک میکنه، در حالت عادی باید وقتی به اولین match رسید، regex متوقف بشه. اما اگر این regex به دنبال یک یا چندین match باشه، نفوذگر تعداد زیادی ایمیل قرار میده و regex parser مجبوره همه رو بررسی کنه و متوقف نمیشه، در نتیجه منجر به DOS میشه. #dos #redos

31

Signed Alireza

25 Dec 2025, 13:36 UTC≈2,340 views49 reactionsread 7 August 2026

General web application penetration testing methodology: اگه تازه کارین میتونین از این متودولوژی استفاده کنین تا وقتی که متودولوژی شخصی خودتونو بسازین. هدف: وقتی به یه domain یا subdomain رسیدین چیکار کنین. نیازمندی ها: آشنایی با تکنولوژی های مختلف استفاده شده در web application ها و آسیب پذیری های مختلف. ابزار های مورد استفاده: Burp suite Waybaclurls dig ffuf Google(for Google dork) Arjun or x8 Wappalyzer Nuclei

40👍9

Signed Alireza

19 Nov 2025, 13:06 UTC≈2,230 views33 reactionsread 7 August 2026

جاهایی که دوتا CSRF token داریم یکی تو body و یکی تو cookie، معمولا یکسان بودن این دو توسط سرور چک میشه. برای اکسپلویت نیاز به یک session fixation داریم که برای قربانی CSRF token دلخواه رو در cookie ست کنیم و فقط کافیه همون توکن رو در Body هم ارسال کنیم. #نکته‌هایی‌از‌کتاب‌ #CSRF

26👍7

Signed Alireza

22 Oct 2025, 17:14 UTC≈3,200 views56 reactionsread 7 August 2026

سلام بخاطر سربازی واسه یه مدت نسبتا طولانی نیستم و آماده کردن مطالب تخصصی هم ممکن نیست، اما سعی میکنم مطالب ساده و کاربردی که ممکنه باهاش آشنا نباشین رو به اشتراک بزارم. با این دورک شودان میتونین به کانفیگ های VPN برسین (اشتراک گذاریش به تعداد زیاد این روش رو منسوخ میکنه) html:"vless" http.title:"index of" با الگو قرار دادن این کوئری میتونین کوئری های کاستوم خودتون رو بنویسین. خیلی وقتا نیاز به نصب لابراتورهای آفل

50👍5👎1

Signed Alireza

27 Jul 2025, 21:13 UTC≈2,750 views15 reactionsread 7 August 2026
Photo

نمونه رجیستر های modbus

🔥113👍1

Signed Alireza

27 Jul 2025, 21:13 UTC≈2,440 views9 reactionsread 7 August 2026
File

File, posted without a caption

🔥8👍1

Signed Alireza

Showing the 12 most recent of 19 posts we hold for @web_appsec. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

24 Jul 2025, 05:57 UTCFinal Results155 voters

مقدمه ای به امنیت سیستم های کنترل صنعتی؟

  1. 👍86%
  2. 👎14%

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 19 most recent posts we hold, published 13 July 2025 to 11 July 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

طب الصادق علیه السلام
@tebosadegh · 43,489
Telegram ranks this channel #38 of 66 here — alongside 65 others — read 28 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Web Application Security” (@web_appsec), 1,771 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/web_appsec.

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.