Link previews, run by Telegram.

What is TelegramBot? Telegram's link preview fetcher. It can't be verified beyond its name.

Run by Telegram.
Purpose: Link previews. A visit means someone shared a link to your page in a chat or social app, and the app fetched it to draw the preview card.
robots.txt name: TelegramBot.
Name only: no published list to check a visit against.

At a glance, the facts in one table.

TelegramBot at a glance. Taken from SenseGap's open bot directory, the same data that sorts every visit in the dashboard.

TelegramBot facts
	TelegramBot
Operator	Telegram
Purpose	Link previews
User agent contains	`TelegramBot`
robots.txt name	`TelegramBot`
Verification	Name only
Documentation	None listed

Purpose, what it does and why it came.

What TelegramBot does. SenseGap sorts every visit by purpose. TelegramBot is in the Link previews group.

TelegramBot is Telegram's fetcher that loads a page's title, description and image when someone shares a link in Telegram's apps.

What a visit means

A visit means someone shared a link to your page in a chat or social app, and the app fetched it to draw the preview card.

Detection, the header SenseGap matches.

How SenseGap recognizes TelegramBot. By its User-Agent header. A separate check then decides whether the visit is real.

Every request carries a User-Agent header naming the software that sent it. SenseGap counts a request as TelegramBot when that header contains TelegramBot, in any letter case. The header is plain text, so any script can copy it. Matching the name is where recognition starts, not where trust starts.

Pattern matched against User-Agent

/TelegramBot/i

Verification, how to tell a real visit from a fake.

TelegramBot can't be fully verified. SenseGap knows of no published IP ranges or DNS names for it, so the name is all there is.

How we verify bots

What this means

Not beyond the user agent. SenseGap knows of no published IP ranges or DNS names for TelegramBot, so anyone can send its name. SenseGap marks these visits Unverified rather than calling them real.

robots.txt, rules you can copy.

Block or allow TelegramBot in robots.txt. Its robots.txt name is TelegramBot. Paste a group into the robots.txt at your site's root.

Block the whole site

User-agent: TelegramBot
Disallow: /

Allow the whole site

User-agent: TelegramBot
Allow: /

Block one folder

User-agent: TelegramBot
Disallow: /private/

One rule catches people out. Under the robots.txt standard (RFC 9309), a crawler that finds a group naming it follows only that group and ignores your User-agent: * rules. If you add a TelegramBot group, repeat in it anything from the catch-all group you still want applied.

robots.txt is a request, not a lock. To enforce a block, match the User-Agent header at your server or CDN. In nginx:

Enforce it at the server

# nginx, inside a server block
if ($http_user_agent ~* "TelegramBot") {
    return 403;
}

SenseGap reads your robots.txt and shows, bot by bot, what you allow and which bots fetched pages you disallowed. See what you get.

Trade-off, what blocking changes.

Should you block TelegramBot? It depends on what you want from Telegram. Here is what each choice means.

If you allow it
Links to your pages show a title, description and image when people share them.
If you block it
Shared links to your pages appear as bare URLs, without a preview card.

Link previews, other bots with the same job.

TelegramBot, answered plainly