How to find the DMCA contact for coomer.su

    coomer.su publishes no abuse address, and an RDAP lookup returns no service at all for the .su registry, so no registrar contact comes back either. What remains is the fallback address abuse@coomer.su, an abuse report to the network in front of the site, and search delisting. Filing all three together is the working route.

    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, contact job.

    Step by step

    1. Capture the evidence before anything else. Screenshot the coomer.su page with the URL bar visible, save the full link, and note the date. A notice filed after the page changes is much harder to support, and evidence gathered afterwards is worth less.
    2. Send to the fallback address. Address the notice to abuse@coomer.su. That address is a convention rather than a published contact, so treat a silent reply as the expected outcome and keep the sent copy as the record that the host route was attempted.
    3. Find the network in front of coomer.su. Resolve the domain's DNS records to see which network answers for it. Most aggregators sit behind a large CDN, and the CDN — not the site — is the party with a published abuse process and a reason to respond.
    4. File the network abuse report. Submit the CDN's abuse form with the same URL list and the same evidence. The CDN does not remove content, but it forwards the report to the origin host and to that host's provider, which is the rung that reaches a human.
    5. File search delisting in parallel, not afterwards. Submit each indexed coomer.su URL for copyright delisting on Google and Bing at the same time as the host notice. Delisting has its own outcome and does not depend on the host answering.
    6. Record what you sent and when. Keep the recipient, the URL list and the date for every round. Without that record there is no way to tell a host that never replied from one that replied and did nothing, and those two need different next steps.

    Where the manual way breaks on coomer.su

    The manual route works once. It stops working at volume, because coomer.su indexes by creator handle: one handle can carry hundreds of posts, and each post is its own URL with its own delisting request. Doing that by hand is an evening a week, forever.

    openDMCA routes every infringing 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 a host like coomer.su that has never answered, the graph is what stops the system spending two email rounds finding that out again.

    The measurable version: a host whose resolved notices end in removal less than a quarter of the time, over a ninety-day window with at least five samples, is fast-pathed straight to search delisting instead of receiving a second email round.

    openDMCA gives the first two hops away: you can open look a host's contact up yourself and run it on a URL of your own, with no account and nothing uploaded.

    One thing that catches people out on coomer.su

    The RDAP lookup in openDMCA's dispatcher calls the same public bootstrap service any takedown tool would. Probed on 4 September, that service answered "no RDAP service is available for this resource" for every .su domain tested, coomer.su included. Any contact-lookup tool that stops at RDAP returns an empty result for this host — not because the tool failed, but because the registry publishes nothing.

    Frequently asked questions

    Is abuse@coomer.su a real address?

    Unknown. The abuse@ convention is defined for domains generally, but coomer.su does not publish a contact confirming it is monitored. openDMCA sends there because attempting the host route is part of a complete record, not because a reply is expected.

    Do I have to give coomer.su my legal name?

    A valid copyright notice names a complainant. When openDMCA files as your authorized agent, its agent details appear on the notice rather than your home address. Filing personally means your own details go on it, which is worth knowing before you send one.

    Will filing make coomer.su repost more of my content?

    Nothing in openDMCA's data supports the fear either way, and honest reporting matters more than reassurance here. What is measurable is that delisting reduces how many people find the page at all, whatever the host does next.

    Can openDMCA promise the content comes down?

    No. openDMCA never promises a removal or a timeline, on any host. What it does is route each URL to the channel that has historically worked for that host, verify whether the URL is actually gone, and reopen it when it comes back.

    Resolve the contact for a host you are dealing with — free, no account.