openDMCA

    How to find the DMCA contact for kemono.su

    No abuse address is published for kemono.su, and a registry lookup for the domain returns nothing to fall back on. A notice therefore goes to the conventional abuse mailbox, an abuse report goes to the network answering for the domain, and delisting requests go to the search engines. All three at once.

    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 kemono.su

    Resolved live · no account · nothing uploaded

    Nothing publishes a contact for kemono.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 kemono.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@kemono.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 kemono.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 kemono.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 kemono.su removal hub.

    Removal route demo for kemono.su, contact job.

    Step by step

    1. Work out which platform the post came from. kemono.su republishes from Patreon, Fanbox, Gumroad and SubscribeStar rather than from the adult platforms. Naming the original platform and the original post is what makes the notice specific enough to act on.
    2. Capture the page and the date. Save the kemono.su URL, a screenshot showing the URL bar, and the date you found it. Evidence collected after the page changes is weaker, and pages on aggregators change often.
    3. Send to the conventional address. Address the notice to abuse@kemono.su. Expect silence, and keep the sent copy: an attempted host route is part of a complete record even when it produces nothing, and later rungs are stronger when the record is complete.
    4. Report to the network answering for kemono.su. Look up which network the domain resolves through and file that network's abuse report with the same URL list. The network forwards to the origin host and its provider, which is where a response usually comes from.
    5. File delisting at the same time. Submit each indexed kemono.su URL for copyright delisting on Google and on Bing. Delisting is a separate outcome that does not depend on the host or the network doing anything.

    What a contact lookup can and cannot tell you about kemono.su

    A contact lookup answers one question: who is published as responsible for this domain. For kemono.su the honest answer is nobody, and a tool that returns a confident-looking address for it is guessing rather than resolving.

    openDMCA's resolver runs four rungs in order — a curated routing table, a shared contact cache, a registry lookup, then the conventional fallback address — and records which rung produced the recipient. That recorded rung is what later tells the system whether a notice failed because nobody read it or because nobody received it.

    The contact cache matters more than it looks: a domain resolved once is reused across every customer, so the second creator filing on kemono.su does not repeat the lookup or the wait.

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

    One thing that catches people out on kemono.su

    kemono.su and its sister aggregator share a registry that publishes no lookup service at all, which means the registrar rung returns nothing rather than returning a wrong answer. That is a meaningfully different failure from a host that answers with an unmonitored mailbox: there is no party to escalate to at the domain level, so the network in front of kemono.su is the first rung with a real recipient.

    Frequently asked questions

    Why does a lookup tool return nothing for kemono.su?

    Because the registry behind the domain publishes no record to look up. An empty result there is accurate rather than broken, and it is the reason the network route matters more on this host than the email route.

    Should I still send the email if nobody reads it?

    Yes, once. A documented attempt at the host route is what makes the later network and provider reports stronger, and it costs one message. Sending it repeatedly achieves nothing and looks like bulk mail.

    Does openDMCA claim it can reach kemono.su directly?

    No. openDMCA does not claim a working host contact for kemono.su. What it claims is a routing decision: attempt the host rung once, then spend the effort on the network and search routes that have a real recipient.

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