Step-by-step: draft a domain assignment agreement for a .mx domain

Step-by-step: draft a domain assignment agreement for a .mx domain. UDRP and ccTLD domain recovery and defense across .mx. Email the firm to assess your case.

A brand owner agrees to purchase a .mx domain from a private seller. The price is set, the handshake is done – and then the transfer fails because the agreement omitted a chain-of-title clause that NIC México requires before releasing the name. The deal collapses. That scenario is more common than it should be.

To draft a domain assignment agreement for a .mx domain you must satisfy the requirements of NIC México (the .mx registry) and account for Mexico's governing ccTLD dispute procedure – the LDRP (Política de Resolución de Disputas en Línea) – which governs .mx disputes much as the UDRP governs .com. The agreement must cover chain-of-title verification, the transfer mechanics at NIC México, escrow structure, representations about prior disputes, and post-transfer registrar confirmation. Skipping any step risks inheriting a disputed, locked, or legally encumbered domain.

This guide walks each drafting step, names the trap hidden inside it, and flags where prior-dispute history or LDRP exposure can derail an otherwise clean deal.

What governs .mx domain transfers? Understanding the LDRP and NIC México rules

The .mx zone is administered by NIC México, and the dispute procedure applicable to .mx is the LDRP – Mexico's country-code equivalent of the UDRP. The LDRP applies to .com.mx, .net.mx, .org.mx, .edu.mx, and the second-level .mx itself. Any buyer of a .mx domain must treat the LDRP as background law that travels with the domain: an assignment does not extinguish a pending or potential LDRP complaint filed by a trademark owner against the seller's registration.

Why does that matter at the drafting stage? Because if the domain is currently the subject of an LDRP proceeding, the registry will typically freeze transfers until the case resolves. A signed assignment agreement is worthless against a locked domain. The first rule of a .mx transaction is to confirm, before anything is executed, that the domain is not locked, not subject to a pending LDRP complaint, and not subject to a court injunction obtained in Mexico.

Beyond the LDRP, NIC México requires that the registrant of record authorize the transfer through its registrar portal. If the seller uses a Mexican accredited registrar, the process goes through that registrar's change-of-registrant workflow. If the registrar is international and accredited by ICANN rather than NIC México directly, confirm that the registrar supports .mx transfers under the current NIC México rules – not all do. The assignment agreement should name the registrar and recite the specific transfer method to be used, because a mismatch between the agreement and the actual registry mechanics is a common failure point.

Step 1: conduct the chain-of-title check before drafting a word

Chain-of-title verification is the due-diligence foundation of any domain assignment, and it is especially important for .mx because the LDRP does not offer the same breadth of publicly indexed prior-decision data that WIPO's UDRP database provides for .com. The buyer's counsel must actively investigate.

The checklist at this step covers four questions. First, who is the current registrant of record in RDDS (WHOIS) – is it the seller, or a privacy proxy? If a proxy, the seller must produce written proof that the underlying registrant is the contracting party. Second, has the domain been the subject of any prior LDRP proceeding? The LDRP administered through the relevant dispute-resolution provider for .mx maintains a published decision register; search it by domain name before proceeding. Third, is there any court record in Mexico of trademark or cybersquatting litigation touching this name? Mexican trademark records are searchable through the IMPI (Instituto Mexicano de la Propiedad Industrial) database; a COGNOMEN review of an .mx acquisition always includes a cross-check of IMPI registrations against the domain string. Fourth, is the domain currently under a registrar lock – whether a standard security lock, a redemption-grace-period lock, or a registry hold? An RDDS status code beginning with "client" or "server" lock means NIC México or the registrar has frozen outbound transfers.

The trap hidden in this step is assuming that a clean RDDS display equals a clean title. It does not. A domain can be unlocked, held by the correct registrant, and still carry a latent LDRP risk if a Mexican trademark owner has not yet filed but has clear grounds to do so. The assignment agreement should include a representation from the seller that no LDRP or court proceeding is pending or, to the seller's knowledge, threatened. That representation becomes the basis for an indemnification clause if a complaint surfaces post-closing.

Step 2: draft the core assignment clauses – and where each one hides a trap

A .mx domain assignment agreement is a commercial contract. It must stand up under Mexican law (the governing law should be stated explicitly – typically federal Mexican law, with jurisdiction in Mexico City or the seller's state). These are the clauses that matter, and the drafting trap in each.

Identification of the domain. State the full domain string precisely – for example, "marca.com.mx" rather than "the domain". Include the registrar name, current registrant account reference, and the NIC México registration expiry date. The trap: an expiry date within 30 days of the signing date means the registration may lapse before the transfer clears. Build in a pre-closing renewal obligation on the seller, or reduce the purchase price to account for buyer-side renewal on day one.

Consideration and payment mechanics. The agreement must state the purchase price and currency, the payment method, and the release trigger. The trap: releasing funds before the registry confirms a successful change of registrant. A properly structured deal uses escrow – the buyer deposits funds with a reputable domain-escrow provider; the escrow agent releases to the seller only upon written confirmation from the registrar that the registrant of record is now the buyer. Do not close this loop with a screenshot; require the official registrar confirmation email or API confirmation.

Representations and warranties. The seller must warrant that: (a) it is the sole legal owner of the domain; (b) no LDRP or court proceeding is pending or threatened; (c) the registration is in good standing and no outstanding renewal fee is due; (d) the domain has not been pledged, liened, or encumbered; and (e) the seller has the authority to convey the domain without third-party consent. The trap: a seller who registered the domain through a corporate entity but is signing in their personal name. Require either a corporate resolution authorizing the transfer or a personal guarantee that the signer has authority.

Transfer mechanics. The agreement should specify the timeline for initiating the transfer (for example, within five business days of escrow confirmation), the registrar steps required, and what happens if the transfer fails for technical or registry reasons. The trap: .mx transfers can fail if the domain is in the first 60 days of a new registration or the first 60 days after a prior registrar transfer, because NIC México imposes a standard post-registration lock period. Verify the lock-out date before setting the closing timeline.

Post-transfer obligations. Include a clause requiring the seller to cooperate with any follow-up actions – such as providing authorization codes, updating contact details, or responding to registry queries – for a defined period after closing (30–60 days is standard). The trap: sellers who become unresponsive after receiving payment and cannot be compelled to cooperate without this clause.

At this stage, the legal architecture of the agreement is in place. The structure above is the standard path; your domain, your counterparty, and the specific LDRP exposure decide which clauses need strengthening. For an assessment of your domain transaction, contact info@cognomenlaw.com.

Step 3: structure the escrow – and why .mx deals specifically need it

Escrow is not optional in a .mx domain transaction. It is the single mechanism that aligns the incentives of buyer and seller when the registry transfer is asynchronous.

The structural logic is straightforward. The buyer has already paid the registrant; the registrant is therefore indifferent to completing the transfer. An escrow arrangement holds the funds until the domain appears in the buyer's registrant account. In practice, domain-escrow providers offer a standardized workflow: the buyer and seller both authenticate, the buyer deposits funds, the seller initiates the transfer, the escrow provider monitors the RDDS for the change-of-registrant confirmation, and then releases. For .mx, that RDDS confirmation step must be calibrated to NIC México's propagation timeline, which can differ from the gTLD norm.

Two escrow-specific traps for .mx deals. First, verify that the escrow provider's standard workflow accommodates ccTLD transfers generally and .mx specifically. Some providers default to a gTLD confirmation flow and may not detect a successful .mx transfer correctly. Confirm the operational procedure before depositing funds. Second, if the domain is being purchased with associated web content, social accounts, or brand assets, those ancillary items must be covered by the escrow release trigger or handled in a separate closing statement – the domain transfer alone does not carry associated assets.

In a recent matter involving a .mx brand domain (spring 2025), a buyer had structured payment outside escrow and released funds on a verbal commitment from the seller. The seller initiated the transfer but then reversed it through a registrar change-of-heart request before the new registrant account was confirmed. Recovery required a registrar escalation and a formal LDRP threat letter before the seller completed the transfer. The lesson is straightforward: funds out, domain confirmed – in that order, never simultaneously.

Step 4: address LDRP exposure – how a prior dispute history can taint the domain

A .mx domain that has been the subject of a prior LDRP complaint, even one that was dismissed, carries reputational and legal risk for the next owner. Panels deciding future LDRP or UDRP proceedings (where the same domain migrates to a gTLD or vice versa) may note prior dispute history when assessing the chain of use. More immediately, a buyer who acquires a domain knowing it has been the subject of a trademark complaint is in a weaker position if a new complaint is filed post-acquisition.

What does a thorough LDRP history check look like? It requires searching the decision registry of the LDRP dispute-resolution provider, reviewing any NIC México administrative correspondence on file, and checking Mexican federal court records for trademark or unfair-competition claims tied to the domain string. A clean bill here is not just a warranty talking point – it is the foundation of the buyer's own legitimate-interest defense if a trademark owner later files an LDRP complaint against the new registrant.

The trap in this step is treating the LDRP check as a box to tick rather than a substantive analysis. The domain string must be assessed against live IMPI trademark registrations. If a Mexican trademark owner holds a registration in a class relevant to the domain's apparent use, that is a material risk factor. The assignment agreement should include a clause allowing the buyer to terminate the agreement without penalty if the pre-closing LDRP/IMPI review reveals a materially elevated risk of a post-acquisition complaint.

What happens when the domain is tainted but the buyer still wants to proceed? The agreement should include an indemnification and escrow hold-back: a portion of the purchase price (commonly 10–20% in tainted-domain situations) is held in escrow for a defined period post-closing (six to twelve months) as a reserve against a successful LDRP complaint. The hold-back is released to the seller if no complaint is filed within that window. This structure aligns the seller's incentive to disclose material information and gives the buyer a funded cushion against an adverse outcome.

If a prior filing or a known trademark conflict has surfaced during due diligence, a focused review of the domain's LDRP and IMPI exposure can define what hold-back amount is warranted. Email info@cognomenlaw.com to reach COGNOMEN's transactions team.

Step 5: governing law, jurisdiction, and cross-border considerations for .mx

Governing law for a .mx assignment agreement is a decision, not a default. Mexican federal law is the natural choice where both parties are in Mexico, but cross-border transactions – a US or European buyer acquiring from a Mexican registrant – raise a genuine conflict-of-laws question. Parties sometimes choose the buyer's home jurisdiction; this is generally a mistake for .mx domains because the registry and any LDRP proceeding are both anchored in Mexico, and a non-Mexican court order directing a registry action against NIC México may not be enforceable.

The sensible structure for a cross-border .mx acquisition is: (a) Mexican federal law as governing law; (b) jurisdiction in Mexico City (federal courts) for disputes arising from the agreement; (c) a dispute-resolution clause providing for arbitration in Mexico (if both parties prefer private resolution) with English as the arbitral language if the buyer is non-Mexican; and (d) a separate acknowledgment that any LDRP proceeding arising post-closing is governed by the LDRP rules themselves, not by the assignment agreement's dispute clause – those two tracks run in parallel and neither forecloses the other.

One cross-zone consideration that arises regularly in our practice: a buyer acquiring a .mx domain often also wants the corresponding .com.mx, the gTLD .com, or both. Where the .com is held by a different party, the UDRP or a direct purchase negotiation runs on a separate track entirely. A .mx assignment agreement should explicitly state that it covers only the named ccTLD domain and does not purport to convey any rights in other zones. Conflating zones in a single agreement creates ambiguity about what was transferred and on what terms.

For cross-border deals where the buyer is domiciled in the United States, the US anticybersquatting legislation (applicable to .com and other domains with a nexus to US commerce) does not apply directly to .mx – but it may apply to a corresponding .com held by the same Mexican registrant. Understanding that cross-zone exposure is part of a complete pre-acquisition due diligence review.

Step 6: complete the closing and confirm registration – the final traps

Closing a .mx domain assignment has two distinct moments: execution of the agreement and actual change of registrant in the NIC México record. Both must be documented.

At execution, both parties should sign the agreement in counterparts, with electronic signatures acceptable under Mexican law for commercial transactions (México's Código de Comercio recognizes electronic signatures for commercial contracts, though the precise form of electronic signature may matter for evidentiary purposes – verify current rules with local counsel in Mexico). The seller should simultaneously provide the authorization code (EPP/auth code) for the domain to the escrow provider in trust, not directly to the buyer, to prevent the buyer from initiating the transfer before escrow funds are confirmed.

After the registrar processes the change of registrant, the buyer must verify three things: that the registrant of record in RDDS matches the buyer's details, that the registration expiry date is as expected (or has been updated if a renewal was part of the deal), and that no registrar lock has been applied to the domain post-transfer that would restrict future management actions. A registry lock applied immediately post-transfer can catch buyers off guard – it is often a security measure by the new registrar and can be lifted, but it requires knowing it is there.

Document the post-transfer RDDS confirmation with a timestamped screenshot and preserve the registrar's confirmation email. In a recent .mx transaction we handled (autumn 2024), a dispute arose between buyer and seller about whether the transfer had completed when a registrar system error caused a 72-hour delay in RDDS propagation. The timestamped documentation resolved the dispute without litigation. Without it, the outcome would have depended on the registrar's internal records.

Finally, update any associated services that depend on the domain – DNS hosting, SSL certificates, email routing, and web platform configurations – within the timeframe specified in the agreement. Domain registrant changes do not automatically carry over DNS management credentials; the buyer must actively claim those from the seller at closing.

How does the LDRP compare with the UDRP for buyers choosing between .mx and .com?

Buyers sometimes ask whether they should acquire the .mx or the .com – or both – and what the dispute exposure looks like for each. The answer depends on the commercial use and the trademark situation, but the procedural comparison is useful.

The UDRP at WIPO (for .com) and the LDRP (for .mx) share a common conceptual structure – both require the complainant to show confusing similarity to a mark, lack of legitimate interest in the registrant, and bad-faith registration and use. The filing fee at WIPO for a single .com domain starts at USD 1,500 for a single-member panel, and a standard case is normally completed within about two months. The LDRP procedure's timelines and fees are governed by the applicable Mexican dispute-resolution provider; the buyer should verify current rules with counsel, as these figures are not fixed by the UDRP schedule.

The important practical difference for a buyer is this: if you acquire a .com in bad faith, a UDRP complaint is available to a trademark owner worldwide – any holder of a registered trademark in any country can file. If you acquire a .mx in questionable circumstances, the trademark owner filing an LDRP complaint is more likely to be a Mexican brand owner with an IMPI registration. That does not make the risk smaller; it makes it more specific. A buyer who conducts a careful IMPI search and LDRP history check has taken the steps that a legitimate buyer would take – and those steps are also the evidence that supports a legitimate-interest defense if a complaint is ever filed.

What if a dispute spans both zones? A trademark owner may file a UDRP at WIPO for the .com and an LDRP for the .mx simultaneously, as separate proceedings under separate rules. There is no consolidation mechanism between them. A buyer who owns both zones under a properly structured assignment agreement, with clean title in each, is in the strongest defensive position – but only if the due diligence for each zone was done separately and documented.

Related at COGNOMEN

• Domain purchase, sale, escrow, and pre-acquisition due diligence services
• Analysis: recovering a lapsed domain – strategies and legal routes
• URS vs. UDRP: choosing the right route for new gTLD disputes