openDMCA

    Host Compliance Index

    The Host Compliance Index reports, per host, how often a DMCA notice actually results in removal, the median number of days from the first notice to a verified removal, which channel did it, and how often the content came back. Figures are computed from openDMCA's own resolved takedowns over a rolling ninety-day window.

    Not published yet, and here is the threshold

    A host's numbers appear here only after 30 resolved takedowns against that host, and the index as a whole is published only once at least 10 hosts each clear that bar. Until then this page is marked noindex and every host below the bar reports "not enough data" rather than a number.

    That is a deliberate cost. A removal rate computed on four takedowns is worse than no removal rate, because it gets the whole dataset dismissed on first read and there is no second read. Publishing openDMCA's own weakest hosts alongside its best is the only version of this page worth having.

    Per-host takedown outcomes over the last 90 days, from openDMCA's resolved takedown corpus
    HostResolved takedownsRemoval rateMedian days to removalChannel that workedCame backFound before Google
    Loading the index…

    What the numbers are computed from, and what they leave out

    Every figure comes from openDMCA's own corpus of resolved takedowns: leaks that reached a terminal state, joined to the first notice actually sent for them. The clock on median days starts when somebody asked the host to act, not when the leak was detected, because detection speed is a different claim.

    Nothing that identifies a creator, a client, a URL or an account crosses the boundary. The query returns per-host aggregates only, by construction rather than by policy.

    Known limitations, stated because a statistics page that hides its limitations is marketing: a leak that came back more than once counts once in the resurrection rate, since only its last return is stored. A removal is counted only when openDMCA's own check found the page gone; one a person marked by hand is left out until a check confirms it.

    Why openDMCA is building this instead of quoting a single removal rate

    A single site-wide removal percentage is the least useful number in this category. It averages a host that complies with a host that has never answered a notice, and it cannot be checked by anyone. What a creator needs before she pays anyone is narrower: for the specific hosts her content is on, does a notice work, and what happens next if it does not.

    The same corpus is what openDMCA routes on. A host whose ninety-day removal rate sits below 25%, across at least five resolved samples, skips the follow-up notice and moves up to search de-listing, with the rest of the escalation ladder still to follow. Publishing the corpus is publishing the routing logic's input, which is the only way to make the mechanism checkable rather than merely stated.

    While this page is gated, the honest comparison to make is on process rather than outcomes. The eight questions to ask any content-protection service is where that starts.

    Frequently asked questions

    Why are most hosts showing 'not enough data'?

    Because fewer than 30 takedowns against that host have reached a terminal state in the last ninety days. A rate computed on a handful of cases is noise. Showing the sample size instead of a percentage is the honest rendering of a number that does not exist yet.

    Is any creator or client data in this index?

    No. The query returns per-host aggregates only and selects no creator, client, URL or account identifier at all. That is enforced in the database function rather than in the page, so no future page change can widen it.

    What does 'channel that worked' mean?

    The rung of the escalation ladder whose notice most often came last before the page was found removed: the site itself, its hosting network, its CDN, its registrar, or search de-listing. Hosts differ enough that the winning channel is often the most actionable column here.

    Why is the window ninety days?

    Because host behaviour changes. A host that complied last year may have changed owners, and a rolling ninety-day window reports what is true now rather than what was true once. The same window drives openDMCA's routing decisions.

    When will this page be published?

    Once at least ten hosts each clear thirty resolved takedowns. The banner on this page reports the current count against that bar. Until it clears, the page carries a noindex tag and is excluded from the sitemap.