Update: changes affecting how to structure escrow for a .sg domain pu…

Update: changes affecting how to structure escrow for a .sg domain pu. UDRP and ccTLD domain recovery and defense across .sg. Email the firm to assess your cas…

Acquiring a premium .sg domain in Singapore carries a specific complication that gTLD buyers often underestimate. The Singapore domain namespace sits under SGNIC and operates its own dispute-resolution procedure – the SDRP – whose decisions and ongoing disputes attach to a domain name, not to the prior registrant. A buyer who closes without checking that record may inherit a tainted asset.

Structuring escrow for a .sg domain purchase now requires a chain-of-title review that explicitly covers prior SDRP dispute history, SGNIC transfer eligibility, and registrant-identity verification before funds are released. The SDRP applies an abusive-registration test broadly analogous to the UDRP, meaning a prior adverse finding can affect the legitimacy of the domain going forward. Escrow release should be conditional on a clean dispute-history certificate and confirmed transfer completion at SGNIC.

This alert covers what has changed, who is affected, and the concrete steps buyers and sellers should take now.

What Changed for .sg Domain Transactions?

SGNIC has continued to refine transfer-eligibility rules and registrant-verification requirements for .sg domains, with compliance checks applied more rigorously at the point of transfer. For buyers, this tightens the window between execution of a purchase agreement and registrar confirmation of a completed transfer. Funds held in escrow must now be structured so that release is contingent on verified transfer completion – not merely on the seller's confirmation that a transfer was initiated.

The practical effect is significant. A standard gTLD escrow workflow – where the buyer receives a push and confirms receipt before funds release – maps onto .sg only if the escrow agreement expressly defines transfer completion as SGNIC registry confirmation, not registrar-side processing alone. That distinction matters because .sg transfers can stall at the registry level even after a registrar has accepted an outgoing transfer request.

Additionally, Singapore's SDRP dispute decisions remain part of the domain's public record and survive a change of registrant. Any domain that carries an adverse SDRP ruling – or an active proceeding – presents a legal encumbrance that standard due diligence must surface. In our practice, we have seen buyers proceed on incomplete chain-of-title checks and inherit exactly this problem.

Who Is Affected by These .sg Escrow and Transfer Rules?

Any party buying or selling a .sg domain for commercial value is directly affected. That includes brand owners acquiring a .sg to complement an existing .com or regional portfolio, domain investors transacting in the Singapore secondary market, and businesses purchasing a .sg as part of a broader brand-consolidation exercise.

Sellers are equally exposed. A seller who cannot produce a clean dispute history or who is subject to an active SDRP proceeding may find that a buyer's escrow agent legitimately refuses to release funds – and that the purchase agreement does not contemplate that scenario. Without clear contractual mechanics, both sides face delay and potential litigation over escrow release conditions.

The issue is not confined to high-value domains. Even a modestly priced .sg with a dormant trademark conflict in its history can become a disputed asset the moment a brand owner investigates the new registrant.

For an assessment of your domain dispute, contact info@cognomenlaw.com.

What Should You Do Now to Structure Escrow for a .sg Domain Purchase?

Four actions reduce the main risks in a .sg domain transaction structured through escrow.

First, run a chain-of-title check before signing. Verify the full registrant history at SGNIC, confirm that no SDRP proceeding is active or has produced an adverse ruling, and identify any prior trademark disputes associated with the domain string. This check should be documented in writing and attached to the purchase agreement.

Second, define transfer completion in the escrow agreement precisely. The release trigger should be SGNIC registry confirmation of the new registrant's details – not registrar acceptance of a transfer request and not the seller's self-certification. Building a defined waiting period – typically the SGNIC transfer propagation window – into the escrow timeline eliminates ambiguity about when release occurs.

Third, include a dispute-representation warranty. The seller should warrant, as of the closing date, that no SDRP proceeding is pending, threatened, or has resulted in an adverse order affecting the domain. The warranty should survive closing for a commercially reasonable period.

Fourth, confirm .sg registrant eligibility. SGNIC imposes local-presence or eligibility requirements for certain .sg registrations. A buyer who does not satisfy those requirements cannot hold the domain, making the transaction void regardless of how the escrow is structured. Eligibility must be confirmed before funds are released.

For cross-zone buyers – those simultaneously acquiring a .sg and a .com, .sg and a .asia, or other paired names – the due-diligence scope should cover both zones independently. A clean .com chain of title does not guarantee a clean .sg record, and dispute proceedings in one zone do not automatically carry over to the other.

To plan a cross-zone acquisition or review an escrow structure for a .sg domain, email info@cognomenlaw.com.

Related at COGNOMEN

• Domain transactions, due diligence, escrow, and portfolio protection services
• Structuring domain escrow for .ae and UAE zone acquisitions
• FAQ: reversing an unauthorized domain transfer in the .cn zone