Step-by-step: draft a domain assignment agreement for a .sg domain
A Singapore brand acquires its competitor's .sg domain in a private deal. The escrow clears. The transfer is processed. Then, six months later, a third party produces evidence that the domain was registered in bad faith years earlier — and threatens to file under SGNIC's dispute procedure. The buyer inherits the taint. That scenario is preventable, but only if the assignment agreement is drafted to address it before money changes hands.
To draft a domain assignment agreement for a .sg domain, you must address SGNIC's transfer mechanics, the Singapore Domain Name Dispute Resolution Policy (SDRP), chain-of-title and prior-dispute checks, representations and warranties by the assignor, and escrow release conditions tied to a clean registry confirmation. A .sg assignment is not simply a bill of sale — it is a title transfer in a regulated namespace where the governing dispute procedure follows a structure closely related to the UDRP, and where a tainted registration can be challenged even after it changes hands.
This guide walks each drafting step in sequence. Each step names the trap a practitioner encounters most often at that stage.
What governs .sg domain assignments — and why it matters for your agreement
The Singapore Network Information Centre (SGNIC) is the registry authority for .sg, and its policies sit above any private contract between an assignor and an assignee. SGNIC's Registrant Agreement requires the domain holder to comply with SGNIC's published policies at all times. An assignment agreement that contradicts those policies — or simply ignores them — will not override them. The registry's terms prevail.
The Singapore Domain Name Dispute Resolution Policy (SDRP) is the ccTLD dispute mechanism for .sg. It follows a structure closely related to the UDRP: a complainant must show that the domain is identical or confusingly similar to a name in which it has rights, that the registrant has no rights or legitimate interests in the domain, and that it was registered or is being used in bad faith. Note the alternative phrasing: registered or used in bad faith — a slightly lower bar than the UDRP's cumulative standard. A domain that was registered innocently but is later used to mislead consumers can still be challenged under the SDRP.
What does this mean for drafting? The assignment agreement must allocate the risk that a completed transfer exposes the buyer to an SDRP complaint. It must also confirm SGNIC eligibility — .sg registrants are generally required to have a Singapore nexus, typically a registered Singapore entity or individual. An assignee who does not qualify cannot hold the domain, regardless of what the agreement says.
Trap: Many private .sg domain agreements are modeled on generic domain assignment templates drafted for .com transactions. They omit SGNIC eligibility confirmation and contain no representation about prior dispute history. Both omissions create avoidable risk for the buyer.
Step 1: Run a chain-of-title and prior-dispute check before drafting a single clause
Chain-of-title work belongs before drafting, not after. A draft agreement built on an unchecked domain is a document that may need to be unwound. Before any clause is written, the buyer's counsel should establish: the current registrant of record, the registration date, every documented transfer in SGNIC's records, and any prior dispute filings under the SDRP or its predecessors.
SGNIC's WHOIS (now reflected in RDDS data) will confirm the registrant, registrar, creation date, and expiry date. If the WHOIS record shows a registrant name that does not match the party presenting themselves as the seller, that discrepancy must be resolved before any agreement is executed. The seller must be the domain holder of record, or the agreement must include a representation that they are authorized to convey the domain on behalf of the registrant of record, with the source of that authority set out in writing.
Prior-dispute history is harder to verify through a single database query. The SDRP's published decisions are searchable, but a settlement or a withdrawn complaint will not appear in a published decision. The agreement must therefore require the assignor to warrant, expressly, that: (a) no SDRP proceeding is pending or threatened, (b) no prior SDRP or court proceeding concerning the domain has been settled, withdrawn, or decided against the assignor or any predecessor in title, and (c) the domain was not registered in breach of any third party's trademark rights to the assignor's actual knowledge.
The trap here is not the warranty itself — it is the absence of a remedy if the warranty proves false. Every warranty in the agreement must be backed by an indemnity. If an SDRP complaint is filed after closing and the assignor's warranty proves inaccurate, the assignee needs a contractual mechanism to recover defense costs and any losses, including the domain if it is transferred away from them.
Step 2: Draft the core assignment clause — and get the technical details right
The assignment clause must identify the domain precisely: the full domain name, the applicable registry (SGNIC), and the registrar through which the transfer will be processed. Generic language such as "the domain" or "the website" is insufficient. If the agreement covers both the domain and associated content, those assets must be identified separately — a domain assignment and a content assignment are distinct acts with distinct consequences for liability and tax.
The clause must also state clearly whether the assignment is absolute or conditional. A conditional assignment — for example, one where title passes only on full payment — requires the agreement to specify what happens to the domain during the period between execution and payment: who may use it, who bears registry renewal obligations, and who controls the DNS settings.
In our practice on .sg domain transactions, we routinely see agreements that specify a purchase price and a payment mechanism but say nothing about what the seller will do (and refrain from doing) between signing and transfer completion. That gap is an invitation for dispute. The agreement should include an interim use restriction: the assignor must not alter the DNS, transfer the domain to any third party, allow it to expire, or use it in a manner that could give rise to an SDRP complaint during the interim period.
How is the technical transfer actually initiated? Under SGNIC's procedures, the registrant must authorize the transfer through the registrar's platform. The agreement should specify which party is responsible for initiating the transfer request, the deadline for doing so after escrow release, and the fallback procedure if the registrar requires additional documentation. If either party's registrar requires a different form of authorization, the agreement should anticipate that and require cooperation.
For an assessment of your domain transaction — including chain-of-title review and SDRP risk — contact info@cognomenlaw.com.
Step 3: Structure the escrow to protect both sides
Escrow is the correct mechanism for a .sg domain transaction of any material value. Without escrow, either party bears the risk that the other performs first and the counterparty does not reciprocate — the buyer pays and the seller does not transfer, or the seller transfers and the buyer does not pay. Neither scenario requires bad faith; it can arise from a technical failure, a registrar delay, or a simple communication breakdown.
A domain escrow arrangement for .sg typically works as follows. The buyer deposits funds with a neutral escrow agent. The assignor initiates the domain transfer through SGNIC's registrar procedures. When the buyer's registrar confirms receipt of the domain in the buyer's account, the escrow agent releases funds to the seller. The agreement must specify the escrow agent, the escrow period, the confirmation trigger, and the consequences of a failed transfer — including whether funds are returned automatically or only on joint instruction.
The trap in escrow structuring is the confirmation trigger. "Transfer complete" can mean different things: the transfer may be initiated at the losing registrar, in transit, or confirmed at the gaining registrar. The agreement should define confirmation as SGNIC's WHOIS (RDDS) showing the buyer as the new registrant of record. That is the only objective, registrant-independent evidence of completed transfer.
Consider also what happens to the escrow if SGNIC requires an eligibility review of the incoming registrant and that review is not completed before the agreed transfer deadline. The agreement should address the possibility of a delayed or refused transfer, the refund of escrow funds in that event, and the costs allocation between the parties. In a recent matter involving a .sg domain (spring 2025), we advised a Singapore-based technology company on exactly this scenario: SGNIC's eligibility check for the incoming registrant added approximately two weeks to the transfer timeline, and the escrow agreement as originally drafted was silent on the extension mechanism. The gap required a supplemental letter agreement, which introduced delay and negotiation cost that could have been avoided.
Step 4: Include SDRP-specific risk allocations in the representations and warranties
General domain assignment agreements often include representations that the seller has good title and the right to convey. For a .sg transaction, those general representations are a baseline — not a ceiling. The SDRP introduces risks that generic title warranties do not address, and the agreement should name them explicitly.
The SDRP's "registered or used in bad faith" standard means that a domain transferred to a buyer in good faith is not automatically insulated from a later complaint based on the seller's use during their period of ownership. Panels in ccTLD disputes have considered the full history of a domain's use, not only its most recent registration. An assignee who used the domain entirely properly may still face a well-documented complaint that traces bad-faith use to the seller. The agreement's indemnity must explicitly cover SDRP proceedings that arise from events predating the transfer.
The representations should also address the trademark register. The assignor should warrant that, to their knowledge, the domain is not identical or confusingly similar to a registered trademark held by a third party in Singapore. That warranty does not require the seller to conduct a full trademark clearance search — the buyer's counsel should do that independently — but it allocates the risk of undisclosed knowledge to the party with the relevant information.
Finally, the agreement should include a survival clause: the warranties and indemnities survive closing for a defined period. Given the SDRP's complaint filing window and the typical timeline for an aggrieved trademark holder to discover and act on a transfer, a survival period of not less than two years is advisable. Shorter survival periods create a window of unallocated risk.
If you have already received an SDRP complaint or are facing a challenge to a recently acquired .sg domain, email info@cognomenlaw.com for a review of your position.
Step 5: Address what happens if the SDRP is invoked after closing
Even a well-drafted agreement cannot prevent a third party from filing an SDRP complaint after a .sg domain transfer. What the agreement can do is specify who controls the defense, who pays for it, and what happens to the domain — and to the purchase price — if the complaint succeeds.
The agreement should include a control clause: on receipt of an SDRP complaint, which party has authority to conduct the defense? If the buyer holds the domain at the time of the complaint, the buyer is the respondent and controls the response. The agreement should require the buyer to notify the assignor promptly — within the 20-day response window under the SDRP — so that the assignor can provide documentation needed for the defense. That window is tight. A contract term that requires notice "within a reasonable time" will not serve either party well when the clock is already running.
The indemnity structure must distinguish between two scenarios. First, where the SDRP complaint is grounded in events predating the transfer: the assignor bears the defense costs and any loss of the domain. Second, where the complaint arises entirely from the buyer's post-transfer conduct: the buyer bears costs. Mixed-period scenarios — complaints that rely on both pre- and post-transfer conduct — are common and should be addressed by allocating responsibility in proportion to the relevant periods of ownership, or by requiring joint defense with a cost-sharing mechanism.
If the SDRP complaint succeeds and the domain is transferred to the complainant, the buyer will have lost both the domain and the purchase price. The agreement must address this. A clawback provision — allowing the buyer to recover the purchase price from the assignor if the domain is lost to an SDRP proceeding arising from pre-transfer events — is the appropriate mechanism. Structuring the clawback correctly requires attention to Singapore contract law, and local counsel should review that clause before execution.
How does the .sg SDRP compare with a UDRP or a Singapore court action?
Buyers and sellers in .sg transactions sometimes ask why the SDRP is relevant at all if the UDRP is the more familiar procedure. The short answer is that the UDRP does not apply to .sg. SGNIC has its own SDRP, modeled on but distinct from the UDRP. For a domain assignment agreement, the practical question is what dispute exposure the agreement must address.
The right route for a challenge depends on the nature of the dispute. If the complaint concerns the domain registration itself — that it was registered or used in bad faith in violation of a third party's trademark rights — the SDRP is the designated mechanism, and it decides on the evidence presented to the appointed dispute resolution service provider. The SDRP remedy is limited: transfer or cancellation, no damages, no costs award.
Singapore courts offer broader remedies, including injunctive relief and damages, but at substantially greater cost and time. A court action may also address claims that an SDRP panel cannot — for example, a claim that the domain assignment agreement itself is void for misrepresentation. For that reason, the assignment agreement's governing law and dispute resolution clause should specify Singapore law and a Singapore-seated arbitration or court forum. Those choices are not just formalities — they determine which remedies are available if the agreement is challenged.
The comparison matters for drafting in a second way. An SDRP complaint and a contractual dispute over the assignment agreement can proceed simultaneously. The agreement should address that possibility — specifically, whether an SDRP proceeding suspends or affects the contractual dispute resolution mechanism, and vice versa.
For transactions that span a .sg domain and related assets in other zones — for example, a .sg and a .com with the same brand string — the agreement should identify each domain separately and ensure that the dispute exposure analysis is conducted for each zone. A .com assignment raises UDRP questions; a .sg raises SDRP questions. The remedies, the procedural standards, and the risk periods differ. We regularly advise on multi-zone domain portfolio transfers where the due diligence scope and the warranty structure must account for each governing procedure in parallel.
Related at COGNOMEN
Frequently asked questions about drafting a .sg domain assignment agreement
When should I draft a domain assignment agreement for a .sg domain?
A written assignment agreement should be prepared before any funds are committed and before the technical transfer is initiated. The agreement must be in place to govern the escrow structure, the transfer mechanics, and the representations about title and dispute history. Completing a .sg transfer without a signed agreement leaves both parties exposed to liability for events that occurred before or during the transfer process, with no contractual mechanism to allocate that risk or recover losses.
What happens if the other side ignores the case?
Under the SDRP, a respondent who does not file a response within the applicable period is typically treated as having defaulted. The panel will still examine the complaint on its merits, but the absence of a response removes any factual rebuttal to the complainant's evidence. In a contractual dispute over the assignment agreement itself, a party who ignores proceedings risks a default judgment or arbitral award. A well-drafted agreement should include notice provisions that make it difficult for a party to claim they were unaware of a proceeding.
How is the SDRP different from a national court for .sg?
The SDRP is an administrative procedure that delivers a narrow remedy — transfer or cancellation of the domain — typically within a matter of weeks and at a fraction of the cost of litigation. Singapore courts offer broader remedies, including damages and injunctions, but require substantially more time and expense. The two routes are not mutually exclusive: a trademark owner may pursue an SDRP complaint for the domain and a court claim for damages arising from the same conduct. An assignment agreement should address both possibilities in its dispute resolution and indemnity provisions.
About COGNOMEN
COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants — including respondent-side defense and reverse domain name hijacking. We advise on domain transactions including .sg assignments, conducting chain-of-title review, prior-dispute analysis, escrow structuring, and SDRP risk allocation across the full life of a transaction. To discuss a domain transfer or dispute, contact info@cognomenlaw.com.
To weigh SDRP exposure against your .sg assignment terms, or to plan a domain transaction from chain-of-title check through escrow, email info@cognomenlaw.com.
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.