How to Send a Cease and Desist Letter
A cease and desist letter is often the first formal step in a domain dispute: it puts the registrant on notice and creates a record. It is also optional, sometimes ignored, and can be turned against the sender through a declaratory judgment suit in a court the registrant chooses.
Updated
- Legal status
- Optional, not a required step
- What it creates
- Documented notice of your rights
- Main risk
- Declaratory judgment lawsuit
A cease and desist letter is a written demand asserting your rights over a mark and requiring the recipient to stop a specific use. It is not a court filing and initiates no proceeding by itself. Its power comes from notice: once the registrant has been told in writing that their domain conflicts with your mark, continued use is harder to excuse as innocent, and the letter becomes part of the record in whatever comes next.
For brand owners dealing with a lookalike domain, the letter sits between informal contact and formal proceedings: cheaper than a UDRP complaint, more serious than an email, and often the first written trace that the registrant knew about the mark.
Step 1: Confirm the letter is the right tool
A demand letter works when the registrant is identifiable, reachable, and has something to lose. It is a poor fit in two situations:
- Abusive infrastructure. A phishing or malware domain run through privacy shields and bulletproof hosting is unlikely to comply with a letter. Report deceptive content to the registrar or hosting provider instead, where suspension does not depend on the operator’s cooperation.
- A weak claim. If the domain predates your mark, targets a descriptive term, or plausibly belongs to a legitimate use, a demand letter is more likely to draw a challenge than compliance.
Step 2: Weigh the risks before sending
Depending on its wording and the surrounding circumstances, the letter can create an “actual controversy” under the Declaratory Judgment Act. A recipient who believes your claim is weak may then sue you first, asking a court in their chosen jurisdiction to declare their domain non-infringing. You lose control of forum and timing.
The letter also warns the registrant. They can respond by deleting hosted content, transferring the domain to a new registrar, or registering additional lookalikes. Preserve your evidence before anything goes out: capture the site, the DNS records, and the registration data while they still exist.
Finally, proportionality matters. The USPTO warns recipients that some demand letters are sent to intimidate them into stopping a use they are entitled to, and an overreaching UDRP complaint that follows can end in a reverse domain name hijacking finding. The demand should match what the observed facts support.
Step 3: What the letter needs to contain
Effective demand letters share a factual structure. The letter identifies:
- Your rights: the mark, its registration numbers and offices if registered, or the goods and services and first-use facts supporting common-law rights.
- The specific subject: the exact domain in dispute and what was observed there, with dates: parked monetization, a copied site, a phishing form, an offer of sale.
- The legal basis: confusing similarity under trademark law, and bad-faith registration and use under the UDRP or the Anticybersquatting Consumer Protection Act where the facts support it.
- The demand: cessation of use and transfer of the domain, or whatever remedy you intend to pursue.
- A deadline: a fixed date for a response, with a statement that you reserve all other remedies.
Stick to facts you can document. Assertions beyond the record read as bluff, and everything in the letter is potentially an exhibit later.
Step 4: Send it where it will be read
Registration data often hides the registrant’s address: where redaction applies, ICANN’s Registration Data Policy has registrars withhold the registrant’s name and street address and publish an email address or web form for contacting the registrant instead. The letter is meant for the registrant, so send it to the registrant contact in the RDAP record, through that email address or web form, or, where a privacy or proxy service is listed, through that service’s relay address or contact form. Where the registrant is a business with a reachable address, send there too. The registrar’s abuse contact, which the abuse contacts tool looks up, is the channel for abuse reports rather than demand letters. Keep proof of delivery for the file.
Step 5: Use the response, whatever it is
Each outcome produces something:
- Compliance or transfer: the cheapest possible resolution. Get the transfer documented.
- An offer to sell: document it. UDRP panels tend to treat settlement communications as admissible where they bear on the registrant’s motive, although negotiations are not necessarily indicative of bad faith. In court, settlement communications may be excluded, so counsel decides how to use them.
- Silence: keep the dated record of the unanswered letter. You escalate to a UDRP complaint or, where statutory damages matter, an ACPA claim through counsel.
- A substantive denial: evaluate it on the merits before spending on a proceeding.
A demand letter only helps while the facts underneath it are current. Domain monitoring keeps the registration, DNS, and site records a letter cites, and keeps recording so a reappearing subject generates a fresh record rather than a stale claim.
Sources
- USPTO: guidance on responding to a trademark cease and desist letter, including declaratory judgment
- Anticybersquatting Consumer Protection Act, 15 U.S.C. § 1125(d)
- Declaratory Judgment Act, 28 U.S.C. § 2201
- Remedies for trademark infringement, including statutory damages for cybersquatting, 15 U.S.C. § 1117
- MedImmune, Inc. v. Genentech, Inc., 549 U.S. 118 (2007): actual controversy judged on all the circumstances
- Federal Rule of Evidence 408: compromise offers and negotiations
- WIPO Overview 3.1: panel views on bad faith factors and settlement discussions (section 3.10)
- ICANN: Uniform Domain-Name Dispute-Resolution Policy
- ICANN: Registration Data Policy (redaction and contact web forms)
Frequently asked questions
No. Nothing in the UDRP or the Anticybersquatting Consumer Protection Act requires a demand letter first. It is a tactical choice: it can produce a quick transfer or generate useful evidence, but it also warns the registrant and gives them time to react.
Demand letters typically set a fixed response date, and its length is a drafting choice rather than a legal rule. The deadline has no legal force on its own, since a letter by itself is not a lawsuit, but it establishes a documented timeline and signals that escalation follows silence.
You proceed to the next remedy: a registrar or hosting abuse report for deceptive content, a UDRP complaint for the domain itself, or counsel for an ACPA claim.
A poorly drafted letter can concede ground or trigger a declaratory judgment suit in a court the registrant chooses. The USPTO recommends that recipients of a demand letter consult an attorney experienced in trademark disputes, so expect counsel on the other side. For anything beyond a clear-cut case, involve trademark counsel.
Related tools and resources
Ongoing brand monitoring
notolens checks new domain registrations across 1,570 TLDs and app store results daily, search ads multiple times a day, and trademark registers weekly. When a lookalike domain, conflicting mark, copycat app, or ad using your name appears, notolens checks it, explains the risk, and hands you the records and possible next steps.