FAQ: verify chain of title for a .group domain

FAQ: verify chain of title for a .group domain. UDRP and ccTLD domain recovery and defense across .group. Email the firm to assess your case.

A .group domain is a new generic top-level domain that carries all the transactional risk common to any gTLD purchase — plus the occasional complication that buyers underestimate how dispute history travels with a name. Following WIPO's 2025 record caseload of more than 6,000 arbitration proceedings, the risk of acquiring a domain with an undisclosed prior complaint, a transfer order, or a tainted chain of title has never been more concrete.

To verify chain of title for a .group domain, a buyer must trace every prior registrant through WHOIS/RDDS history, search the WIPO and Forum case databases for prior UDRP proceedings involving the name, check for any existing registrar lock or dispute entry, and confirm that the current registrant acquired the domain through a clean, documented transfer rather than through a default or forced assignment. The UDRP applies to .group as a new gTLD, so a prior panel decision — even an unenforced one — can resurface and affect a subsequent owner's position.

The questions below address what due diligence actually requires, how to structure the acquisition safely, and what happens when a dispute is already in motion.

When can I verify chain of title for a .group domain?

Chain-of-title verification for a .group domain can be conducted at any stage — before signing a purchase agreement, during the escrow period, or even after the fact if you are auditing a portfolio you already hold. The optimal window is before any funds change hands. Once escrow closes and the transfer completes, a buyer who discovers a prior UDRP transfer order or an unresolved dispute faces substantially fewer remedies than one who identified the problem in advance.

A pre-acquisition check typically takes days, not weeks, if the necessary access to WHOIS/RDDS history and arbitration databases is in place. What can the check miss? Sealed settlement agreements between prior parties are not publicly recorded. A domain that was the subject of a negotiated private settlement — rather than a panel decision — will not appear in any public database. That gap is precisely why a contractual warranty from the seller, backed by an indemnity, is a structural safeguard rather than a courtesy clause.

In our practice, we advise buyers to treat the verification window as a condition precedent to closing. If the seller resists a due-diligence period of reasonable length, that resistance is itself a data point worth noting.

Who can verify chain of title for a .group domain?

Domain-name counsel with access to WHOIS/RDDS history services, the WIPO case database, the Forum's case records, and registrar-level tools is the appropriate party to conduct a chain-of-title verification. A general corporate lawyer or a trademark attorney who does not practice in domain disputes may miss the specific signals that indicate a tainted registration — for instance, a prior cancellation decision that left the domain available for re-registration by a third party, or a pattern of prior registrants consistent with drop-catching after a forced transfer.

Self-verification by the buyer is possible for the surface layer. The public WHOIS/RDDS record shows the current registrant and, where privacy services are not in use, the registration date. WIPO's online case search and the Forum's equivalent let any user query a domain name for prior proceedings. What those tools do not reveal is chain-of-transfer documentation at the registrar level, the content the domain served at each historical registration, or contractual restrictions that a prior settlement may have placed on the name.

We regularly advise both buyers and sellers in .group domain transactions — reviewing registrar records, surfacing prior dispute history, and drafting escrow instructions that account for the risk of a post-transfer complaint. An acquisition without that layer of scrutiny is an acquisition whose purchase price does not fully account for the legal exposure being transferred alongside the domain.

To discuss a .group domain acquisition and the chain-of-title review it requires, contact info@cognomenlaw.com.

What is the deadline once a case starts?

Once a UDRP proceeding commences against a .group domain, the registrant has 20 days to file a response with the chosen provider — WIPO, the Forum, CAC, or ADNDRC. That window is fixed by the Rules and does not extend automatically. A registrant who misses it defaults, meaning the panel decides the case on the complainant's submission alone. Default does not guarantee a transfer order, but it removes the registrant's opportunity to present a Paragraph 4(c) safe-harbor defense.

What happens if you are the buyer and the dispute was filed against the seller before closing? The registrar will typically apply a transfer lock once proceedings commence. The lock prevents the domain from moving to a new registrant while the case is active. A buyer who closes escrow without knowing that a case has commenced may find the transfer blocked at the registrar level — and may inherit a dispute they were not party to, depending on how the purchase agreement is drafted.

For .group specifically, the 20-day response deadline and the standard two-month overall timeline both apply because .group operates under the UDRP administered by accredited providers. Speed matters: an unfiled response cannot be filed once the window closes without a formal request for extension, which the provider grants only in defined circumstances.

Does WIPO or a court decide a .group dispute?

A .group domain dispute is resolved under the UDRP, typically before WIPO or the Forum, not a national court. Because .group is a new gTLD operated under an ICANN registry agreement, all three UDRP elements must be proved by a complainant: confusing similarity to a trademark the complainant holds, the registrant's absence of rights or legitimate interests, and registration together with bad-faith use. The only remedies a UDRP panel can order are transfer or cancellation — no monetary damages, no injunction.

A court remains an option in parallel or as an alternative. US anticybersquatting litigation, for example, can reach money damages and can operate where the UDRP does not produce an adequate remedy. The choice between UDRP and court depends on what the complainant needs: speed and a transfer order point to UDRP; damages or injunctive relief covering conduct beyond domain registration point to court. We have advised on both routes for .group and related new-gTLD disputes.

WIPO administered approximately 6,282 domain-name cases in 2025 — a record — and handles a significant share of new-gTLD proceedings. The Forum is the second major provider by volume. The Czech Arbitration Court (CAC) and ADNDRC also accept .group complaints but are used less frequently.

What if the registrant does not respond?

A registrant who does not file a response within the 20-day window is in default. The panel proceeds on the record before it — typically the complaint alone — and applies the standard three-element test. Default is not concession. The panel still requires the complainant to demonstrate all three Paragraph 4(a) elements; a weak complaint can fail even without opposition.

In practice, default significantly increases the likelihood of transfer because the respondent has not placed any Paragraph 4(c) safe-harbor evidence before the panel. Panels in UDRP proceedings have consistently held that default does not shift the burden of proof in a formal sense, but the absence of any counter-narrative leaves the complainant's evidence largely unrebutted. That asymmetry is relevant for buyers conducting chain-of-title checks: a domain that was transferred by default order may have a prior registrant with an ongoing grievance, even if the procedural route to re-opening the UDRP is narrow.

Can a defaulting registrant challenge the outcome? The UDRP itself does not provide an appeal. A former registrant who believes a transfer was wrongly ordered may seek relief in a court of competent jurisdiction — typically the jurisdiction specified in the registrar's registration agreement. That path is slower and more expensive than the original proceeding.

Can the decision be appealed or challenged?

The UDRP has no built-in appellate mechanism. Once a panel issues a transfer or cancellation order, the provider notifies the registrar, and the registrar implements the decision after a brief waiting period — typically 10 business days — during which the losing party may seek a court injunction to stay implementation. After that window closes without a court order, the transfer is final at the registrar level.

A respondent who believes the panel erred can pursue court action in the jurisdiction that the registrar's agreement designates, or in a court with jurisdiction over the complainant. Courts have in limited circumstances reversed UDRP transfer orders where the panel's reasoning was demonstrably incorrect or where the complainant's rights were not what they appeared. That route is fact-specific, time-consuming, and involves costs far exceeding the original arbitration. It is not a routine remedy.

Reverse Domain Name Hijacking (RDNH) — a panel finding that a complaint was brought in bad faith — is the intra-UDRP mechanism for addressing an abusive complaint. An RDNH finding carries no monetary penalty but creates a public record against the complainant. We have defended .group and related gTLD registrants through to RDNH findings where the facts supported that outcome. No RDNH finding guarantees a particular outcome in a future proceeding, but the record has practical deterrent value.

How does escrow protect a .group buyer from a tainted domain?

An escrow structure holds the purchase funds with a neutral third-party escrow agent until defined conditions are satisfied — typically confirmation that the domain has transferred cleanly, that no UDRP proceeding is pending, and that no registrar lock is in place. For a .group acquisition where chain-of-title verification has identified prior dispute history, escrow conditions can be drafted to require the seller to represent and warrant that no undisclosed proceedings exist, with indemnity provisions that survive closing.

What escrow cannot do is cure a tainted chain of title retroactively. If the domain was previously transferred by a UDRP default order and the original registrant retains a colorable claim, indemnity from the seller is only as valuable as the seller's ability to pay. That is why verification before closing — not indemnity after closing — is the primary protection.

In a recent matter (a new-gTLD acquisition, early 2026), we identified a prior UDRP proceeding against the same domain name that had not been disclosed by the seller. The proceeding had ended in a settlement before a panel decision, meaning it did not appear in public case databases. The discovery came from registrar-level transfer history and seller due-diligence representations. Closing was conditioned on additional representations; the transaction completed without the buyer assuming the associated risk.

For an assessment of a .group domain acquisition, including chain-of-title review and escrow structuring, contact info@cognomenlaw.com.

Related at COGNOMEN

• Domain transactions, escrow, and pre-acquisition due diligence across gTLDs and ccTLDs
• Case study: domain due diligence in an online brand acquisition
• Guide to court action for cybersquatting where arbitration is insufficient