Sending a DMCA Takedown Notice: A Compliance Checklist

By ·

A phase-by-phase compliance checklist for sending a DMCA takedown notice that a hosting provider cannot ignore, grounded in 17 U.S.C. Section 512. It runs the right-tool triage (the DMCA is a copyright statute only, not a trademark or patent weapon), the ownership-and-authority verification, and the pre-notice diligence the law requires, including the good-faith fair-use consideration mandated by Lenz v. Universal. It then drills the six statutory elements of a compliant Section 512(c)(3)(A) notice, supplies an annotated fill-in template, and quality-controls the draft against the defects that quietly doom most notices under the substantial-compliance rule. The back half covers submission and tracking, the 10-to-14-business-day restoration clock, the Section 512(h) subpoena for unmasking anonymous infringers, Section 512(f) misrepresentation exposure, the repeat-infringer record-keeping that gives a notice teeth, and when to escalate to a lawsuit or run parallel trademark, domain, and customs tracks. Every item carries a short Why note, a Trap warning where useful, and its controlling authority, with a running worked example, a common-mistakes list, and links to Rightsy's copyright and brand-enforcement resources. Educational only, not legal advice.

Intellectual Property -> Copyright | Published 28 June 2026 | rightsy.io

What this checklist is for. This is a working, start-to-finish checklist for sending a takedown notice under Section 512 of the Digital Millennium Copyright Act, 17 U.S.C. § 512 — the notice-and-takedown system that handles the overwhelming majority of online copyright disputes. Follow it in order and you will produce a notice a hosting provider cannot lawfully ignore, while staying clear of the misrepresentation liability that punishes careless senders.

Who should use it. Photographers, illustrators, writers, musicians, filmmakers, course creators, software authors, and the in-house teams and attorneys who police their content online. It is written for the sender. If you are on the receiving end and want to fight a takedown, start instead with the counter-notice half of DMCA Takedowns: How to Send One, How to Fight One.

What you'll need before you start. (1) A copy of the original work and the facts of its creation (date, author, first publication, registration number if any); (2) the exact web address(es) where the infringing copy appears; (3) dated screenshots of the infringement; (4) your contact information; and (5) the hosting provider's DMCA designated-agent details or takedown web form. Gather these first and the notice itself is a fifteen-minute task.

This is education, not legal advice. The DMCA is a copyright statute with limited reach, the case law varies by circuit, and platform procedures change. Confirm current law and consult qualified counsel about any specific matter.


A takedown notice is not an email. Parts of it are sworn under penalty of perjury, and the statute attaches liability to knowing misrepresentations. So the discipline this checklist enforces is not bureaucratic fussiness — it is the difference between a fast removal and a wasted clock, and between a clean enforcement record and a misrepresentation claim filed against you. The good news is that the system rewards preparation. A notice that does its homework first and checks every statutory box moves through a platform's queue in hours; a sloppy one languishes, or accomplishes nothing at all.

To keep the steps concrete, one invented character runs through the whole checklist. Devin Okafor is an independent wildlife and landscape photographer who licenses his prints to magazines and galleries. His signature image, Snowy Owl, First Light, keeps getting lifted: a dropshipping store is selling it on canvas using his exact file, and a lifestyle blog has reposted it as a page header without a license. Devin's facts are clean — he shot the photo, never assigned it, and registered it — which is exactly the kind of case the takedown system is built to resolve fast. We will watch him work the checklist from triage to escalation.

How to read each item

Every checkbox below follows the same micro-format so you can scan it quickly:

The legal logic in ninety seconds: Section 512 offers hosting platforms a safe harbor — immunity from liability for their users' infringement — but only if they "expeditiously" remove material once they receive a compliant notice. A compliant notice manufactures the very knowledge the safe harbor is conditioned on, so the platform's cheapest move is to take the material down. A defective notice does not pierce that safe harbor at all, which is why precision is everything. The phases below take you from "do I even have a copyright problem?" through drafting, sending, tracking, and escalating.


Phase 1 — Triage: Confirm You Actually Have a DMCA-Shaped Problem

Before anything else, make sure the takedown is the right tool. The single most expensive mistake in this whole area is firing a copyright takedown at a problem that is not a copyright problem.

Worked example. Devin's situation is cleanly copyright-shaped: both the dropshipping store and the blog reproduced and publicly displayed his photograph. No brand name of his is in play, the image is plainly expressive, and he owns the reproduction and display rights. Triage passes. The DMCA is the right tool.

Phase 2 — Verify Ownership and Authority to Send

The notice must come from the owner of the infringed exclusive right or from someone the owner authorized. This is less obvious than it sounds, and providers routinely demand proof of authority from anyone who looks like a third party.

Worked example. Devin created Snowy Owl, First Light on his own, never assigned it, and holds the registration certificate in his own name. Ownership is unambiguous, and he is sending on his own behalf, so there is no agency authority to paper. Phase 2 is a five-minute confirmation.

Phase 3 — Pre-Notice Due Diligence: Look Before You Swear

This is the phase that separates effective senders from cautionary tales. The good-faith statements in the notice are legally load-bearing, and the law requires you to do real thinking before you click send.

Worked example. Devin's diligence comes out clean and fast: he drew no license, the photo is plainly his, the dropshipping and blog uses are pixel-for-pixel commercial reproductions with no plausible fair-use story, and the work is registered. He can swear the good-faith statements with a clear conscience. Contrast a harder case: if a film-studies channel had used a three-second glimpse of his photo to discuss composition, that arguable fair use would change the calculus entirely and counsel caution.

Phase 4 — Find the Right Recipient: The Designated Agent

A perfect notice sent to the wrong inbox accomplishes nothing. Every provider that wants the hosting safe harbor must register a designated agent to receive notices, and you must reach that agent (or the platform's official intake).

Worked example. Devin pulls the dropshipping marketplace's designated agent from the Copyright Office directory and finds it also runs an IP-report web form; he will use the form. For the blog, he identifies the web host's abuse/DMCA contact, because the blogger has no takedown form of their own. Two recipients, two correct addresses.

Phase 5 — Draft the Notice: The Six Statutory Elements

Here is the core of the whole exercise. Section 512(c)(3)(A) lists six things a notice must contain. Miss one and the notice may not legally count. Treat each as a non-negotiable box.

An Annotated Fill-In Template

Use the skeleton below and replace every bracket. The italic notes are drafting guidance, not part of the notice.


DMCA TAKEDOWN NOTICE

Date: [Current Date]

To: DMCA Designated Agent, [Provider Name], [Address / DMCA-notice email or form] [Identify the agent from the Copyright Office directory or the platform's published DMCA contact — not a generic support address.]

From: [Your Name], [Mailing Address], [Phone], [Email] [Element 4 — complete contact information, and the address any counter-notice comes back to.]

Re: Notice of Copyright Infringement under 17 U.S.C. § 512(c)(3)

The copyrighted work (Element 2). The infringed work is [describe: e.g., an original photograph titled Snowy Owl, First Light], created by me on [date], first published at [URL] on [date], and registered with the U.S. Copyright Office under Reg. No. [number, if any]. A copy is attached as Exhibit A. [Registration is not required to send, but attaching a copy lets the provider verify quickly — and registration matters enormously if this becomes a lawsuit.]

The infringing material (Element 3). The infringing copy appears at this exact URL: [URL]. [If multiple, list each.] A screenshot captured on [date] is attached as Exhibit B. [The exact URL is the most important field in the entire notice.]

Good-faith statement (Element 5). I have a good-faith belief that the use described above is not authorized by me (the copyright owner), my agent, or the law.

Accuracy and authorization (Element 6). The information in this notification is accurate. Under penalty of perjury, I am authorized to act on behalf of the owner of the exclusive right that is allegedly infringed.

Signature (Element 1): /s/ [Your Name]


Phase 6 — Quality-Control the Draft Before You Send

A notice that "substantially" fails the requirements is not considered in determining whether the provider has disqualifying knowledge — meaning a defective notice does not pierce the safe harbor even if the platform ignores it. Run this pre-flight check.

Phase 7 — Submit, Confirm, and Track

Worked example. Devin submits the marketplace form for the canvas listing and emails the blog's host with his notice and exhibits. The marketplace pulls the listing within a day; the host disables the image within two. He logs both, including the dropshipping seller's account handle, in case the same seller resurfaces.

Phase 8 — After You Send: Anticipate the Counter-Notice

The system cuts both ways. The person whose content you removed can file a counter-notice, and the timing that follows is mechanical. Understanding it is half the strategy.

Worked example. The blogger does not respond — the repost was indefensible, and no counter-notice arrives. The dropshipping seller, however, files a counter-notice claiming "licensed stock." Devin checks it: it is facially complete, so the clock is running. Because he registered the photo early, statutory damages are on the table, which makes a suit credible. He sends the seller's "license" claim to counsel to test before deciding whether to file within the window.

Phase 9 — Escalate: Subpoenas, Repeat Infringers, and Parallel Tracks

A takedown alone plays whack-a-mole. When you need to reach the person behind the screen, terminate a serial account, or attack a multi-right problem, the DMCA and its neighbors offer more tools.

Worked example. When the Snowy Owl file reappears under a throwaway account, Devin escalates: a § 512(h) subpoena to the hosting platform unmasks the person behind the burner, his log of repeated notices against that account pressures the platform toward terminating it under its § 512(i) policy, and a demand letter follows. The takedown was the start, not the finish.

Common Mistakes

The failures in this area are predictable, and almost all of them are avoidable:

Related Resources


Rightsy publishes clear, carefully sourced guides and checklists to intellectual-property law — copyright and trademark alike — for creators, in-house teams, and the attorneys who advise them. Facing an online infringement, or unsure whether your problem is even a copyright problem? Rightsy's trademark and logo search, brand monitoring, assignment records, and virtual attorneys can help you figure out which right is actually at stake and route the dispute to the right channel. Reach the team at admin@rightsy.io. This checklist is educational and not legal advice; the DMCA is a copyright statute with limited reach, the case law varies by circuit, and platform procedures change, so confirm current law and consult qualified counsel about any specific matter.


Selected Authorities

Statutes and instruments. Digital Millennium Copyright Act, Pub. L. No. 105-304 (1998); 17 U.S.C. § 512 (safe harbors; § 512(c)(2) designated agent; § 512(c)(3)(A) notice elements; § 512(c)(3)(B) substantial compliance; § 512(f) misrepresentation; § 512(g) counter-notification and restoration clock; § 512(h) subpoena; § 512(i) repeat-infringer policies); 17 U.S.C. § 106 (exclusive rights); § 107 (fair use); § 102(a)-(b) (subject matter; idea/expression); § 204-205 (transfers and recordation); § 411(a) (registration prerequisite to suit); § 412 (timely registration prerequisite to statutory damages and fees); § 504(c) (statutory damages, up to $150,000 per work for willful infringement); Regulation (EU) 2022/2065 (Digital Services Act, fully applicable Feb. 17, 2024); Directive (EU) 2019/790 (EU Copyright Directive).

Cases. Lenz v. Universal Music Corp., 815 F.3d 1145 (9th Cir. 2016) (duty to consider fair use before noticing); Rossi v. Motion Picture Ass'n of America, Inc., 391 F.3d 1000 (9th Cir. 2004) (subjective good-faith standard under § 512(f)); Online Policy Group v. Diebold, Inc., 337 F. Supp. 2d 1195 (N.D. Cal. 2004) (knowing misrepresentation actionable); Perfect 10, Inc. v. CCBill LLC, 488 F.3d 1102 (9th Cir. 2007) (substantial compliance; reasonable implementation of repeat-infringer policy); RIAA v. Verizon Internet Services, Inc., 351 F.3d 1229 (D.C. Cir. 2003) (§ 512(h) subpoena does not reach mere-conduit providers); BMG Rights Mgmt. (US) LLC v. Cox Communications, Inc., 881 F.3d 293 (4th Cir. 2018) (loss of safe harbor for paper-only repeat-infringer policy); Viacom Int'l, Inc. v. YouTube, Inc., 676 F.3d 19 (2d Cir. 2012) (specific knowledge; no general duty to monitor); Fourth Estate Public Benefit Corp. v. Wall-Street.com, LLC, 586 U.S. 296 (2019) (registration as a prerequisite to suit); Feist Publications, Inc. v. Rural Telephone Service Co., 499 U.S. 340 (1991) (originality; no copyright in facts).

Agency and secondary sources. U.S. Copyright Office, Section 512 of Title 17: A Report of the Register of Copyrights (2020), and the DMCA Designated Agent Directory; Nimmer on Copyright (treatise discussion of § 512). No statutory amendment to Section 512 had been enacted as of mid-2026; confirm current law and platform procedures before relying on anything described here.

Read this article on Rightsy