What t.me is, from the removal side
Telegram is a network surface. Public channels that redistribute paid content at high velocity, often minutes after a post goes up. Channel monitoring plus a DMCA notice to Telegram's published copyright address.
Route openDMCA holds: Curated abuse address. host_handlers seed row in supabase/migrations/20260607183000_scan_provenance.sql. A notice about t.me therefore reaches a route that is published and documented.
RDAP probe run 2026-09-04 against the same bootstrap service the takedown dispatcher queries. It returned no RDAP service for this registry at all.
Removal tasks for t.me
Each task below is a separate route with a separate outcome on t.me. Start with the one that matches what you are actually holding — a link, a search result, or a profile.
| Task | What it acts on |
|---|---|
| How to find the DMCA contact for a t.me channel | abuse contact |
| How to deindex t.me links from Google | search delisting |
| How to stop reuploads on t.me channels | reupload monitoring |
| How to check if a t.me channel is still live | removal verification |
| How to report non-consensual imagery on t.me | the non-copyright route |
Where a takedown for t.me stalls
Channel-level reporting inside the app, then delisting of any t.me link that reached a search index.
openDMCA routes every URL through the Removal Graph — a live map of which hosts actually remove content, how fast, and through which channel — so each takedown takes the shortest path that has historically worked for that host. For t.me that means the rungs above are not run in a fixed order: a host with fewer than a quarter of its resolved notices ending in a removal, measured over ninety days with at least five samples, is fast-pathed straight to search delisting instead of spending a second email round on it.