Demand Release of Domain Name

This contract is a formal brand-protection demand letter. It notifies the current domain registrant that the company owns federally registered trademarks and that the registrant is using a matching or confusingly similar domain. The letter requires the registrant to cease commerce tied to the mark, transfer domain control by completing a Domain Transfer Form, withdraw similar domains from sale, and respond within seven days. If the recipient does not respond, the company may file an action for trademark infringement seeking injunctions, damages, and costs.

In practice, complying often requires initiating the transfer process with the current registrar. The registered name holder should unlock the domain, verify identity, and obtain the authorization code, also called the auth code, EPP code, transfer code, or unique code, from the account. The gaining registrar or new registrar then submits a transfer request.

ICANN rules typically require confirmation sent to the registrant's email address (registrant email) to authorize the switch. The user may need to pay a transfer fee and confirm domain name registration details, DNS, and domain settings, and contact data before proceeding. One registrar can deny a transfer because of a lock, a new registration, a previous transfer within 60 days, or trouble confirming the holder's authorization. To avoid interruption, locate the expiration date, coordinate hosting and provider changes, and plan the future use of assigned names across .com,. net, and. org. Check redirects and DNS so the organization can proceed without service loss.

Examples of use cases include a company reclaiming a brand domain registered by a former developer, consolidating domains held at one registrar into a new registrar after a merger, or resolving confusion caused by a similar .net or .org domain.

A marketing team might search its portfolio, verify registration records, and contact third parties to request transfer domain actions. Legal or IT staff can initiate steps, confirm authorization, and manage price, pay, and account logistics while confirming identity and confirming future configurations.

Proposal Kit helps teams assemble documents like this demand and related materials fast. Its document assembly, AI Writer for supporting documents, automated line-item quoting for services, and extensive template library make it easier to write consistent requests, organize the process, and coordinate stakeholders.

This brand-protection letter serves two purposes: it demands that the registrant stop commercial use of trademarks on a confusing domain, and it requires a prompt transfer of that domain to the trademark owner. The company asks the registered name holder to complete a transfer domain form, withdraw similar domains from sale, and respond within seven days. If the recipient does not respond, the sender may file an infringement action seeking injunctions and damages.

Beyond the request itself, smart teams prepare by auditing assigned names across .com, .net, and .org, running a search for lookalike strings, and verifying domain name registration records. Locate the current registrar, confirm the registrant's email address in WHOIS, check the expiration date, and decide on the future use of the name. Document any use of the mark and capture evidence of traffic or redirects to support the organization's position.

To execute the transfer process, the registered name holder typically unlocks the domain, retrieves the authorization code (auth code, EPP code, transfer code, unique code), and shares it securely. The gaining registrar or new registrar uses that code to initiate a transfer request. ICANN practices often require confirmation sent to the registrant's email before the switch.

One registrar may deny movement due to a lock, a new registration, or a previous transfer within 60 days, non-matching contact data, or trouble confirming identity and authorization. Before you proceed, review DNS and domain settings, coordinate with your hosting provider or developer, and plan a window to avoid outages. Expect to pay a transfer fee; align price approvals and account access so a user with authority can confirm and complete the process.

Operationally, set a clear timeline for the holder to respond, and keep communications factual and professional. If the party cooperates, you can resolve the matter quickly; if not, the sender has preserved a record to support escalation. Keep internal stakeholders in the loop so legal, IT, and marketing can move in step.

Use cases include reclaiming a brand domain controlled by a former developer, consolidating names after a merger where everything sat at one registrar, or stopping confusion from a similar.net mapped to a competitor. Teams can verify registration, initiate the transfer, confirm identity, and proceed with minimal risk.

Proposal Kit helps organizations assemble this kind of letter and the related paperwork efficiently. Its document assembly, automated line-item quoting, AI Writer for supporting documents, and extensive template library help teams write, organize, and manage consistent communications with ease.

This demand letter is a focused tool to stop unauthorized commercial use of a brand and to recover control of a matching or confusingly similar domain. It identifies the current registrant, references the current registrar and the site or redirect in use, and sets a firm seven-day deadline to cease use, complete a domain transfer form, and confirm that similar domains have been removed from sale. If the recipient does not respond, the company states it may file an infringement action seeking injunctions, damages, and costs.

To make the transfer process smooth, prepare a verified inventory of assigned names, including .com, .net, and .org variants and likely typos.

Confirm the registrant's email address shown in public records to ensure authorization emails arrive. Build a transition plan for DNS and domain settings so the organization can switch without outages. Define future use of the domain, such as a holding page or redirect, so stakeholders can proceed immediately upon control. Maintain a file of evidence: timestamps of the live site, screenshots, redirect chains, and WHOIS data. This record supports any escalation referenced in the letter.

Operational readiness matters. Identify the account owner with authority to initiate and confirm actions at the gaining registrar or new registrar, approve the price, and pay any transfer fee. Coordinate with the hosting provider or developer so identity checks and authorization steps do not stall.

If the holder cooperates, they will unlock the domain and provide the authorization code (auth code, EPP code, transfer code), after which the new registrar submits a transfer request under ICANN rules. Watch for confirmation notices to the registrant's email and respond quickly.

High-level use cases include reclaiming a brand domain parked with ads that divert traffic, resolving a situation where a franchisee or reseller controls a local name, recovering domains registered by a departed employee, consolidating assets after an acquisition, or preventing confusion from a lookalike new registration controlled by a third party.

Proposal Kit supports teams executing this process by streamlining document assembly and helping write consistent communications. Its AI Writer can build supporting documents to accompany the demand, automated line-item quoting can estimate internal effort or provider tasks, and its extensive template library helps users initiate, confirm, and organize the process with clarity and ease.

Writing the Demand Release of Domain Name document - The Narrative

How to Build a Legal Contract with Proposal Kit

This video illustrates how to create a legal contract using the Proposal Pack Wizard software. It also shows how to create a proposal with an invoice and contract at the same time.