To write a DMCA takedown notice to a web host, identify the copyrighted work you own, list the exact URL of every allegedly infringing copy, provide contact information, include the required good-faith and accuracy statements, sign the notice, and send it to the service provider's designated agent. Those are legal representations, not a customer-support shortcut. Verify ownership, authorization, licensing, and possible permitted use before filing. This guide is operational information, not legal advice; disputed, high-value, international, or counter-noticed matters deserve advice from a qualified lawyer.
Start by choosing the right removal route
The DMCA section 512 process addresses claimed copyright infringement through eligible online service providers. It is not automatically the right tool for every harmful page. A fake profile may be better reported under impersonation rules. A non-consensual intimate image may qualify for a dedicated NCII or safety form. A copied brand name may raise trademark questions. Defamation, doxing, threats, and extortion have different elements and urgency. Using the correct path gives the reviewer a claim it can actually evaluate and reduces the risk of misrepresenting a copyright issue.
Confirm who owns the rights. The person who pressed the shutter, recorded the video, wrote the text, or employed a creator may not always be the same person who controls the relevant exclusive right. Review photographer agreements, agency contracts, work-for-hire terms, platform licenses, collaboration releases, and assignments. If you act for someone else, retain written authority. Copyright registration is not one of the six notice elements listed by the Copyright Office, but registration and ownership records can matter if the dispute escalates.
Preserve evidence before contacting the host
Create one case folder per site. Save the full infringing URL, not just the domain or a search-result screenshot. Record the page title, date and time observed, uploader or account identifier, direct media URL if visible, and a screenshot that shows enough page context to locate the item. Pair every reported item with an authorized source URL or a concise description of the original work. If many works appear on one site, build a numbered schedule so the reviewer can match each original to each reported location.
Do not download more intimate material than you need or circulate the evidence packet widely. A URL, contextual screenshot, hash, and authorized source may be safer than copying an entire private library into email. Store access logs and use a restricted folder if a manager or service is helping. Evidence preservation and data minimization can coexist: the goal is a reviewable record, not a second uncontrolled archive of the leak.
- Original work: title or description, creation date if known, and an authorized publication or ownership record.
- Infringement: exact page and media URLs, account name, observed timestamp, and a contextual screenshot.
- Authority: your role as owner or authorized agent and the document supporting agency when applicable.
- Routing: site copyright policy, provider identity, designated-agent result, and the submission channel used.
- Case history: sent notice, automated acknowledgment, ticket number, follow-up, result, and any counter-notice.
Find the provider that can act
A page can involve several companies: the site operator controls the account; a hosting provider stores the page; a CDN or reverse proxy serves traffic; a domain registrar maintains registration; and a search engine indexes the URL. Start with the site's copyright policy and designated contact. The U.S. Copyright Office maintains a searchable directory of agents for providers seeking section 512(c) safe-harbor treatment. Search the legal entity and known alternative names, then compare the directory record with the contact published on the service's own site.
Do not assume the registrar hosts the content or that a CDN can edit the origin. A correct notice to the correct operational layer is more effective than a mass email to every company in a DNS lookup. If a platform provides a structured form, use it: the form usually collects the fields its review team needs and produces a case reference. Search delisting is a second track. Removing a result from Google or Bing does not delete the source, and removing the source does not guarantee that cached or alternate URLs vanish immediately.
Include the six required notice elements
The Copyright Office's designated-agent page summarizes section 512(c)(3)(A). A legally effective notification must substantially include six items: a physical or electronic signature of an authorized person; identification of the copyrighted work or a representative list for multiple works at one site; identification and location information for the material to remove or disable; information reasonably sufficient to contact the complaining party; a statement of good-faith belief that the complained-of use is not authorized by the owner, its agent, or law; and a statement that the information is accurate and, under penalty of perjury, that the sender is authorized to act for the owner of the relevant exclusive right.
Write for the reviewer. Use a descriptive subject, name the site and number of URLs, present originals and reported locations in a table, and keep legal statements distinct from background. Avoid inflated allegations, threats, irrelevant personal history, and vague instructions to remove everything associated with a username. The host needs enough information to locate the specified material; it does not need to guess which item on a homepage you mean.
A complete notice is specific: this protected work, at this exact unauthorized location, sent by this owner or authorized agent, with the required representations and signature.
A practical notice structure
Use a short opening that identifies the notice as a notification of claimed copyright infringement under 17 U.S.C. § 512(c). State your name and whether you are the copyright owner or authorized agent. Add a numbered schedule with each work, authorized source or identifying description, and exact reported URL. Provide your email, telephone number, and mailing address as required by the provider's process. Then include the good-faith and accuracy/authority statements in clear language and add your physical or electronic signature and date.
A template is only a checklist; it cannot decide whether you own the work, whether a license exists, or whether the use is lawful. Do not copy a declaration you do not understand. If publishing your home address creates a safety risk, ask a qualified service or lawyer how it can act as an authorized agent and what information a provider may forward. Never invent agent details or use a false identity to avoid the contact requirement.
Submit once, preserve the record, and follow the process
Send the notice through the designated method and save the submitted text, attachments, confirmation page, message headers, ticket number, and timestamp. Record the provider's stated review window. If it asks for missing information, respond in the same thread with a corrected, complete schedule. Repeated daily duplicates can fragment the case and look like spam. Escalate only after you understand whether the first request was received, rejected as incomplete, forwarded to a customer, or still under review.
The provider may remove or disable access, ask questions, decline because it cannot locate the material, or forward a counter-notice. A counter-notice is not another support reply; it can trigger statutory timelines and a decision about court action. Preserve it and seek legal advice rather than bluffing. The Copyright Office notes that section 512 also intersects with claims for misrepresentation in notices and counter-notices, which is another reason to verify every statement before submission.
Monitor the result without confusing visibility with removal
Check the exact source URL, the media URL, search results, mirrors, and known aliases separately. Mark outcomes such as removed, access disabled, delisted, rejected, needs information, disputed, or reuploaded. Take a final timestamped screenshot. If the same media reappears at a new URL, create a linked case rather than overwriting the old record. That history shows which hosts respond, which routes need escalation, and whether manual work has grown large enough to justify automation.
For a small clean queue, this workflow may be enough. For hundreds of recurring URLs, multiple stage names, or frequent reuploads, a content-protection service can automate discovery, routing, tracking, and follow-up. Evaluate the service on evidence quality and accurate claims—not only total notices sent. The objective is a defensible removal operation with fewer leaks and fewer false reports.