How to stop reuploads on coomer.su after a takedown

    A coomer.su post that comes down is often replaced rather than abandoned, because the site re-scrapes the source platform on a schedule. Stopping the cycle means watching the source rather than the copy: catch the repost when it appears, keep the URL history, and file again immediately rather than starting over.

    Left up, 120 exposed copies work out to an estimated $701 a month in diverted subscriptions. Estimate, not a measurement: it assumes 0.45 diverted subscribers per exposed post at an average subscription price of $12.99. Your number depends on your pricing and audience.

    Removal route for coomer.su

    Resolved live · no account · nothing uploaded

    Nothing publishes a contact for coomer.su. The notice goes to the fallback address, and the network and search routes carry the weight.

    1. 1 · Curated host route silent. No host_handlers row for coomer.su.
    2. 2 · RDAP abuse contact silent. rdap.org returns no RDAP service for the .su registry. Probed 2026-09-04.
    3. 3 · Fallback address resolves. abuse@coomer.su — the address the resolver falls back to. It may not be monitored.
    4. 4 · Network and search runs next. Cloudflare detection over DNS-over-HTTPS, then Google and Bing delisting of every indexed coomer.su URL.

    What happens to what you type: nothing. The domain is matched against openDMCA's routing table in your browser. No request is made to coomer.su, no page is fetched, and the text is not stored or sent anywhere.

    Every removal route on this page is also listed on the coomer.su removal hub.

    Removal route demo for coomer.su, reuploads job.

    Step by step

    1. Keep the URL history rather than deleting it. Store every coomer.su URL you have already filed on, with the date and the outcome. A repost at a new URL is easy to recognise when the history exists and almost impossible to prove when it does not.
    2. Watch the source, not only the copy. coomer.su republishes from the platform you post on. A repost therefore follows your own posting schedule, which makes the days after a new paid drop the window worth checking rather than a random weekly sweep.
    3. Re-file quickly and reference the earlier notice. When a coomer.su post returns, file again and cite the previous notice and its date. A repeat notice that shows a pattern is a materially stronger document than a first notice about a single URL.
    4. Keep the delisting request current. A new URL is a new search result. Add each returning coomer.su URL to the delisting request rather than assuming the earlier one still covers the content.
    5. Use image matching when the title changes. Reposts frequently drop the stage name from the title to defeat keyword matching. Perceptual hashing of a reference image finds those, because the image is what did not change.

    What monitoring on coomer.su can honestly claim

    openDMCA polls the aggregator sources directly rather than waiting for a search engine to index a new post, and tags each leak with where it was first seen. Posts found that way are caught before they are searchable, which is a different and more useful event than finding them afterwards.

    The honest limit: monitoring finds a repost, it does not prevent one. Nothing openDMCA does stops coomer.su from scraping a new post. What changes is the gap between the repost appearing and the notice going out, and how much of that work you personally have to do.

    A daily liveness sweep re-checks URLs that were already marked removed, and reopens any that returned — which is how the system learns that on some hosts "removed" means removed for six days.

    openDMCA gives the first two hops away: you can open the still-indexed check and run it on a URL of your own, with no account and nothing uploaded.

    One thing that catches people out on coomer.su

    openDMCA's takedown table enforces one notice per leak per dispatch round through a uniqueness constraint, which means a coomer.su URL that reappears cannot be re-filed inside the same round even by accident. A returning URL is therefore recorded as a new round rather than a duplicate send, and that round counter is what later distinguishes a host that removes once from a host that removes repeatedly.

    Frequently asked questions

    Why does coomer.su repost the same set?

    The site republishes from the source platform on a schedule rather than curating by hand. A removal deletes the copy; the next scrape of the source can produce a new one, which is why timing the check around your own posting matters.

    Does anything stop the reupload happening at all?

    No tool prevents a third party scraping a platform you post on. What can be shortened is the time between a repost appearing and a notice being filed on it, which is the part that is actually under your control.

    Is a repost worth filing on again?

    Yes, and the second notice is stronger than the first. It documents a pattern rather than an incident, which matters at the network and provider rungs where a single URL rarely gets attention.

    Check whether a URL you already reported has come back — free, no account.