How to run a DMCA check on any domain

How to run a DMCA check on a domain

1. Enter the domain. Type the bare domain (example.com, without https:// or a path) into the checker. No Google Search Console access and no site verification is required, because the underlying records are public.
2. Read the request count and timeline. The result shows how many copyright-removal requests name the domain and when they were submitted, so you can see whether activity is historic or ongoing.
3. Open the request details. Each record can carry a reporting organisation, a copyright owner, the URLs listed in the request, a hit count and a status. A free account reveals these fields.
4. Confirm what actually happened. Check the status on each URL. A request is a claim, not a verdict — Google declines a meaningful share of them, so a listed URL is not necessarily a delisted URL.
5. Re-check on a schedule. Save the domain so later checks highlight only the requests that have appeared since last time.

What a DMCA check actually checks

"DMCA check" gets used for several different things, and they are worth separating before you start, because they answer completely different questions:

This guide covers the first one: finding out whether your domain appears in the copyright-removal requests Google receives for Search.

Why you can check a domain you do not own

Google publishes data on the copyright-removal requests it receives for Search in its Transparency Report, covering the large majority of request volume received since July 2011. The records name the reporting organisation, the copyright owner, the URLs specified, and what Google did about them. Where it can legally do so, Google also links to the underlying notice archived by Lumen, a Harvard Berkman Klein Center research project.

Because the records are public, a DMCA check needs no privileged access. You do not connect Search Console, you do not add a DNS record, and you do not prove ownership. That also means you can check a competitor, an acquisition target, a client site, or a domain you are about to buy.

How to read the result

Request count is context, not a score

A large site that has been online for a decade may accumulate requests simply because it is large. A handful of requests spread over years reads very differently from a cluster of requests filed last month by one sender. Look at the shape of the timeline before you react to the total.

The reporting organisation is often not the rights holder

Many requests are filed by enforcement vendors acting for a rights holder, so the reporting organisation and the copyright owner are frequently two different names. If you are trying to work out who to contact, the copyright owner field is usually the one that matters.

Listed is not the same as removed

This is the single most misread part of the data. Google reviews requests and declines to delist URLs when there is no evidence of infringement, when the submission is incomplete, when the use looks like fair use, or when the process is being abused. Some requests are rejected outright. Always read the status on the specific URL rather than assuming the request succeeded.

Bulk lists sweep in bystanders

Automated enforcement generates long URL lists, and those lists sometimes include pages that have nothing to do with the claimed work — a category page, a search results page, or a domain that merely resembles a target. Being named is a lead to investigate, not proof of wrongdoing.

What each result status means

A request record is not a single verdict — it carries a status per URL. These are the states you will actually encounter, and what each one should make you do:

The common mistake is reading a request count as a damage count. A domain with forty requests where every URL came back "no action" is in better shape than a domain with one request that removed its highest-earning page.

Is it a delisting, or something else?

Most pages that vanish from Google were not delisted for copyright. Before you conclude anything, rule out the ordinary explanations — they are far more common:

The decisive test is the exact-phrase check: take a distinctive full sentence from the page, search it in quotes, and see whether the page returns. A page that ranks poorly still surfaces for its own unique sentence. A delisted page does not surface at all.

Record checks, index checks and badges are three different things

Tools described as "DMCA checkers" fall into distinct categories that answer different questions. Using the wrong one is how people reach confident wrong conclusions:

• Record checks read the public copyright-removal data directly. They tell you whether a request exists, who filed it, which URLs it named and what Google did. This is primary-source evidence, and it is what DMCA Detector does.
• Index-status scanners test whether a URL currently appears in Google and infer a removal from its absence. Useful as a symptom check, but absence has many causes — a noindex tag produces the same signal as a copyright delisting, with no way to tell them apart from the result alone.
• Protection badges place a logo and a verification token on your site. They register you with a vendor. They do not check anything, and they have no bearing on whether requests have been filed against your domain — see dmca-site-verification.

The two useful categories are complementary: the record tells you what was claimed and decided, the index check tells you what is true right now. Run the record check first, because it is the only one that names the party involved. A fuller breakdown is in how DMCA checking tools compare.

What to do with what you find

• Nothing found. That is the common result. Save the domain so a later check surfaces anything new rather than making you re-read the whole history.
• Old requests, no recent activity. Record it and move on. Historic records rarely need action.
• A URL that matters was listed. Confirm the status, then work out whether the claim has merit. Our guide on what to do after a copyright-removal request walks through the options.
• Repeat requests from one sender. Patterns matter more than single events, especially if you may need to raise the pattern with counsel.
• Traffic dropped and you cannot explain it. A DMCA check is a cheap thing to rule out before you spend a week on a technical audit. See how removal from Google Search works.

What a DMCA check cannot tell you

Being honest about the boundaries saves you from over-reading the data:

• It does not cover YouTube, Blogger or other Google products — the Search dataset is Search only.
• It does not include notices sent to Google by fax or letter, or notices sent directly to your host or registrar rather than to Google.
• It does not tell you whether a claim is legally correct. That is a judgement, not a data field — the status recorded against a URL is an outcome, not a verdict. What each status means.
• It does not find copies of your content elsewhere on the web, and it does not file takedown notices for you.

If the check turns something up, the next question is what the request actually means — how a DMCA takedown works covers where the request came from and why it is an allegation rather than a finding. If you are the one who needs something removed, see how to report copyright infringement.

FAQs

Keep reading

Last reviewed 2026-08-26.