What coomer.su is, from the removal side
Coomer is a aggregator surface. Bulk-scrapes and re-hosts paid OnlyFans and Fansly posts, indexed by creator handle. Direct API monitoring catches new posts before Google indexes them; DMCA notice per URL, then search delisting.
Route openDMCA holds: No published contact. No host_handlers row and no RDAP service for the .su registry, so the resolver falls through to abuse@coomer.su. openDMCA does not claim a working host contact for coomer.su. Cloudflare abuse report against the fronting network, then Google and Bing delisting of every indexed URL.
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 coomer.su
Each task below is a separate route with a separate outcome on coomer.su. 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 coomer.su | abuse contact |
| How to deindex coomer.su links from Google | search delisting |
| How to stop reuploads on coomer.su after a takedown | reupload monitoring |
| How to check if a coomer.su link is still live after filing | removal verification |
Where a takedown for coomer.su stalls
Cloudflare abuse report against the fronting network, then Google and Bing delisting of every indexed URL.
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 coomer.su 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.