Step-by-step: draft a domain assignment agreement for a .es domain
You have agreed a price for a .es domain. The seller holds it today; you want it in your registrar account tomorrow. Between that handshake and that transfer sits a document most buyers never read carefully enough – the domain assignment agreement. Skip it or sign a poorly drafted version, and you may acquire a name encumbered by a prior dispute, a flawed chain of title, or an eligibility problem that Red.es can use to revoke the registration entirely.
To draft a domain assignment agreement for a .es domain, you must address five structural layers: Red.es eligibility verification, chain-of-title confirmation, prior-dispute history clearance, escrow mechanics, and the formal change-of-registrant procedure with the accredited registrar. The governing body for .es is Red.es, Spain's public entity that administers the zone under its own registration policy – distinct from ICANN's UDRP system, though Red.es has its own dispute procedure. Get any of these layers wrong, and the transfer completes on paper but fails in the registry, or worse, succeeds and then unravels.
This guide walks each step in sequence, names the trap inside it, and explains what a properly built agreement looks like at the end of the process.
Step 1: Confirm Red.es eligibility before drafting a single clause
The first sentence of any .es assignment analysis is not about contract law – it is about eligibility. Red.es restricts .es registration to entities and individuals with a qualifying connection to Spain or the European Economic Area. Before you draft anything, verify that the transferee meets the current Red.es eligibility criteria: an EU/EEA natural person, a legal entity with a registered address or branch in Spain or the EU, or a holder of a trademark with effect in Spain, among other qualifying grounds.
The trap here is deceptively simple. A buyer who qualifies today may not have documented that qualification in a form Red.es accepts. Eligibility must be stated in the registration record, and the registrar will require supporting evidence at the change-of-registrant stage. If the documentation is missing or inconsistent, the transfer stalls or is refused even when the agreement is otherwise perfect.
In our practice, we routinely see buyers who assume that holding an EU company registration is self-evidently sufficient. It is – but only if the registrar receives the correct proof in the correct format. Build an eligibility checklist into the assignment agreement itself, as a condition precedent to closing: the agreement does not complete until Red.es-compliant eligibility documentation is confirmed. That single clause prevents a category of post-signing disputes that are painful and slow to resolve.
Step 2: Conduct a chain-of-title review – and understand why .es makes this harder
A chain-of-title review for a .es domain is more opaque than for a .com. WHOIS data for .es registrations is subject to GDPR-aligned redaction enforced by Red.es, which means the registration history you can pull publicly is thin. You will see the current registrar, the creation date, and the expiry date – but often not the name of the current registrant or prior holders.
How do you fill that gap? Through the registrar directly, with the seller's cooperation. A well-drafted assignment agreement obliges the seller to produce, as a disclosure schedule, a written history of all registrations, transfers, and any change-of-registrant events since the domain's creation. That history is then cross-referenced against Red.es's own published dispute decisions, the WIPO UDRP database (for any .es domains that were subject to WIPO proceedings), and any available court records in Spain.
The hidden trap in this step is the unrecorded informal transfer. Many .es domains have changed hands through account credential hand-offs – the original registrant simply gave login details to a buyer who never formally completed a change-of-registrant with Red.es. The registry record still shows the original holder. If that original holder is a dissolved company, a deceased individual, or a party in insolvency, the transfer you are about to sign may be legally void or challengeable. Require the seller to warrant and represent that the registration record reflects the true current holder and that no undocumented transfers have occurred. Attach a copy of the registrar's current WHOIS output to the agreement as a schedule.
For a read on whether the three UDRP elements are met – or whether a Red.es dispute history affects your acquisition – reach us at info@cognomenlaw.com.
Step 3: Clear the prior-dispute history – the step most buyers skip entirely
A domain that was the subject of a prior UDRP complaint, a Red.es dispute proceeding, or a court injunction in Spain carries a residual risk that does not automatically extinguish on transfer. Panels and courts have consistently held that a transferee who acquires a domain with actual or constructive knowledge of a prior adverse finding does so at their own risk. If the domain was previously ordered to be transferred and that order was not executed, or if a dispute is pending, acquiring it compounds the problem rather than solving it.
The Red.es dispute procedure – distinct from the UDRP – applies to .es registrations and can result in cancellation or transfer of the domain if an abusive registration is found. Red.es publishes its dispute decisions. Search them. Also search WIPO's UDRP database for the exact domain string: some .es domain disputes have been filed as UDRP complaints where the registrant chose an accredited UDRP provider rather than the national procedure, particularly in the period before Red.es's own procedure was fully established.
In a recent matter (a .es acquisition, spring 2025), we identified a prior Red.es dispute decision against the seller's predecessor in title that the seller had not disclosed. The domain had been subject to a cancellation order that was never enforced because the complainant withdrew before implementation. The buyer's intended trademark use would have reignited the same complaint grounds. We restructured the transaction to include an indemnity provision and a six-month escrow holdback against the risk of a re-filed proceeding.
Build three express representations into the agreement: (1) no dispute proceedings are pending or threatened; (2) no prior decision ordered transfer or cancellation of the domain; (3) the seller has no knowledge of any third party asserting trademark rights in the domain string. These are not boilerplate. They are the clauses that determine whether you have recourse if a dispute surfaces after closing.
Step 4: Structure the escrow – Red.es mechanics control the sequence
Escrow in a domain transaction is not merely financial prudence. For .es, the sequence of the escrow release and the Red.es change-of-registrant procedure must be synchronized, or the buyer pays before the transfer is confirmed and the seller can walk away with both the money and the domain.
The standard structure works as follows. Funds are deposited with a neutral escrow agent at signing. The seller initiates the change-of-registrant request with the accredited registrar. Red.es and the registrar process the request, which involves the registrar sending a confirmation email to the new registrant (the buyer) for acceptance. Once the buyer's registrar account reflects the domain as registered in the buyer's name – and this is verified against the registrar's panel, not against a screenshot – the escrow releases. If the transfer is not confirmed within an agreed window (typically 10–15 business days), the escrow reverts to the buyer.
What breaks this structure in practice? Two things. First, buyers sometimes agree to release escrow on receipt of the change-of-registrant request confirmation email rather than on actual registry transfer. That email is not proof of transfer – it is proof of initiation. The registrar can still reject the request on eligibility grounds after sending it. Second, sellers sometimes delay accepting the change-of-registrant workflow in the registrar's system, particularly where the registrar requires the current registrant (the seller) to take an affirmative action to authorize the outbound transfer. Name both triggers in the agreement: the seller's obligation to initiate and to complete all required authorization steps within a fixed number of business days, with the buyer's right to terminate and recover escrow if either deadline is missed.
Step 5: Draft the assignment clauses – what the document must actually say
With eligibility confirmed, title cleared, dispute history reviewed, and escrow structured, you are ready to draft the assignment itself. A .es domain assignment agreement is a contract under Spanish law or the law of another jurisdiction by mutual agreement – but because the registry operates under Spanish and EU law, and because any dispute about the registration post-transfer will be handled by Red.es or Spanish courts, it is generally advisable to choose Spanish law as the governing law and Madrid or Barcelona courts as the forum, unless both parties have a stronger connection to another jurisdiction.
The core operative clauses are: (1) the assignment of all right, title, and interest in the domain from seller to buyer, effective on registry transfer completion; (2) the seller's agreement to take all steps required by Red.es and the registrar to complete the change-of-registrant; (3) the representations and warranties on eligibility, title, and dispute history (as described in Steps 1–3 above); (4) the escrow mechanics (as described in Step 4); and (5) an indemnity from the seller for any pre-closing dispute, lien, or encumbrance on the domain. Add a clause covering the domain's DNS configuration at transfer: agree whether the seller hands over the domain with DNS pointed to a holding page, with the existing DNS records, or blank. DNS surprises at closing are a recurring friction point that a single sentence resolves.
One element that distinguishes .es assignments from gTLD assignments: the purchase price declaration. Spanish transfer taxes may apply depending on the classification of the domain as an asset in the transaction. This is a matter for local taxation counsel in Spain; the assignment agreement should include a clause allocating tax liability and requiring each party to make its own filings. Do not leave it silent – silence means the buyer assumes all tax risk by default in many interpretations.
Step 6: Execute, register the change-of-registrant, and verify
Signature is not closing. Closing is confirmed registry transfer. These two events must be treated as distinct. The agreement should specify the form of execution (electronic signatures are generally sufficient for domain assignment agreements, but Spanish law has specific rules for notarized instruments in certain asset classes – verify with local counsel whether the domain's value or context requires a notarial act).
After execution, the sequence is: seller instructs the registrar to initiate change-of-registrant; buyer receives and accepts the confirmation email from the registrar; both parties monitor the registrar's WHOIS output until the buyer's registrant details appear; escrow releases on confirmed transfer. The agreement should identify who is responsible for the registrar's change-of-registrant fee (typically a nominal amount, but assign it explicitly to avoid post-closing friction).
Verification is the final step most parties neglect. Once the WHOIS reflects the buyer's name, pull a full registrar RDDS output, save it with a timestamp, and attach it to your closing file. That timestamped output is your proof of completed transfer if a future dispute, a Red.es audit, or a successor in interest ever challenges the assignment. In a second matter we handled (a .es brand domain, autumn 2024), a buyer who had completed transfer without saving any post-transfer registry output faced a challenge from a third party nearly a year later. Reconstructing the transfer timeline from registrar logs took weeks and cost more in legal time than the timestamped screenshot would have taken to produce.
If a prior filing or response in a Red.es or UDRP proceeding has produced a complication for your intended acquisition, a focused second read can identify the element that was missed. Email info@cognomenlaw.com to discuss.
Choosing between Red.es dispute resolution and court action if the deal goes wrong
Even a well-drafted agreement can be followed by a dispute – typically where the seller fails to complete the change-of-registrant, where a third-party trademark holder surfaces after closing, or where a pre-closing dispute proceeding was concealed. The remedies available depend on the nature of the problem.
If a third party asserts trademark rights in the domain string and files a complaint with Red.es, the buyer faces that proceeding as the new registrant. Red.es's dispute procedure is distinct from the UDRP: it applies Spanish and EU trademark law, and the remedy is transfer or cancellation. There is no monetary damages award. If the assignment agreement contained the indemnity clause described in Step 5, the buyer has contractual recourse against the seller – but the regulatory proceeding proceeds independently of the contract.
If the seller refuses to complete the transfer after the agreement is signed, the remedy is contractual – specific performance or damages through Spanish courts, or through whichever courts the agreement designates. Red.es itself has no mechanism to compel a seller to execute a private assignment. Only a court order achieves that, and it takes time. That is precisely why the escrow structure in Step 4 matters: the buyer should not release funds until transfer is confirmed, so that non-performance by the seller leaves the buyer with its money, not just a contractual claim.
If the buyer discovers post-closing that the domain was the subject of an undisclosed prior dispute proceeding, or that the chain of title is defective, the contractual indemnity is the primary avenue. Where the defect is serious enough to constitute fraud or misrepresentation, Spanish civil law remedies may allow rescission. That analysis requires local litigation counsel in Spain.
The decision matrix, briefly: dispute by a third-party trademark holder after transfer → defend the Red.es or UDRP proceeding and pursue the seller's contractual indemnity; seller refuses to complete transfer → enforce through the designated courts; defective title discovered post-closing → contractual indemnity, and consult local litigation counsel in Spain on rescission.
Related at COGNOMEN
Frequently asked questions
Is it worth it to draft a domain assignment agreement for a .es domain?
Yes – and the value is not proportional to the domain's price. Even a modestly valued .es name carries registry-specific eligibility rules, GDPR-redacted WHOIS history, and a Red.es dispute procedure that can unwind a transfer after the fact. A properly drafted agreement with chain-of-title representations, escrow mechanics tied to confirmed registry transfer, and an indemnity against prior disputes costs far less than the litigation or proceeding that follows an undocumented hand-off. The agreement is the buyer's primary recourse if the deal goes wrong after funds move.
What are the most common mistakes when you draft a domain assignment agreement for a .es domain?
Four mistakes appear repeatedly. First, releasing escrow on the change-of-registrant initiation email rather than on confirmed registry transfer – those are not the same event. Second, omitting representations on prior dispute history, leaving the buyer with no contractual recourse if a Red.es proceeding surfaces post-closing. Third, failing to address Spanish tax treatment of the domain as an asset, leaving tax liability unallocated. Fourth, skipping the post-transfer WHOIS verification and timestamped record – without it, proving the transfer date becomes an expensive reconstruction exercise if challenged.
Can a three-member panel change the outcome?
In the context of a Red.es dispute proceeding triggered after a .es assignment closes, the procedural structure differs from UDRP. Red.es proceedings are decided by a single expert under its own rules; there is no three-member panel option comparable to the UDRP. In a UDRP proceeding involving a .es-adjacent matter filed before a UDRP provider, a three-member panel may apply where a party requests it and pays the higher fee – at WIPO, the three-member fee begins at USD 4,000. A three-member panel can produce a more nuanced or contrary result, particularly in close cases, but it also costs more and takes longer. The decision whether to request one is fact-specific.
Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. Meet the team.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.