Step-by-step: verify chain of title for a .store domain

Step-by-step: verify chain of title for a .store domain. UDRP and ccTLD domain recovery and defense across .store. Email the firm to assess your case.

You have found the .store domain you want. The price is right, the seller looks credible, and the escrow platform is ready. But before any funds move, one question should stop the transaction cold: who has actually owned this domain, and what happened along the way?

To verify chain of title for a .store domain, a buyer must trace every registrant change from the original registration to the present holder, confirm the domain was never subject to an unresolved UDRP complaint or a registry dispute, and check that no trademark owner holds a viable claim against the name. The .store new generic top-level domain (new gTLD) operates under ICANN's standard UDRP framework, so all three elements of Paragraph 4(a) govern any challenge to ownership. A clean chain of title is the primary defense against a post-transfer dispute that strips the asset from its new owner.

This guide works through each step in sequence, flags the trap hidden in each one, and explains the realistic path to a defensible acquisition.

Why chain-of-title verification matters for .store specifically

The .store gTLD was delegated to encourage commerce-oriented domain registrations, and that commercial focus has made it a magnet for trademark-sensitive names. Panels deciding UDRP complaints about .store domains apply the same three-element test as any other gTLD: confusing similarity to a mark, absence of registrant rights, and registration and use in bad faith. A prior owner who held the domain abusively does not automatically taint the chain – but a buyer who takes the domain with notice of that history faces a serious legitimacy problem.

The commercial stakes are real. A retailer who acquires a clean-looking .store domain, rebrands around it, and then receives a UDRP complaint based on a prior registrant's conduct may be unable to demonstrate good faith at the moment of their own registration. Following WIPO's 2025 record caseload – 6,282 domain-name cases in a single year – panels are scrutinizing registration history with increasing care, particularly for commerce-sector gTLDs where confusingly similar marks are common.

In our practice, we regularly advise buyers who discover a prior dispute only after a transfer has closed. The options at that stage are narrower and more expensive. Doing the work before closing is always the better path.

Step 1: Pull the current WHOIS/RDDS record and confirm the registrant identity

The first step is also the most obvious – and the one where buyers most commonly skip to the next stage too quickly. Pull the current WHOIS/RDDS record for the domain and confirm the registrant name, registrant organization, and registrar of record. That baseline data anchors the rest of the chain.

The trap here is privacy and proxy services. Most .store registrations under current ICANN policy display privacy-masked contact data in the public RDDS query. You will see the registrar's proxy service as the listed registrant rather than the real holder. This is not itself suspicious – it is the default for most personal and small-business registrations. But it means the seller's claimed identity requires independent verification at this stage, not at closing.

Ask the seller to provide the underlying registrant account details as part of pre-contract disclosure, and cross-check the account creation date against the registration date the WHOIS record shows. A mismatch – where the seller's account was created recently but the domain is several years old – raises an immediate flag that the domain passed through at least one intermediate holder whose consent and authority you have not yet confirmed.

Step 2: Reconstruct the registrant history using RDDS snapshots and archive data

Current RDDS data shows only the present holder. To verify chain of title for a .store domain, you need the historical registrant sequence. That requires assembling snapshots from historical WHOIS archive sources, which capture registrant-field changes over time.

What you are looking for at this step: the total number of distinct registrant names or organizations over the life of the domain; the approximate dates of each transfer; and any gaps or anomalies in the timeline. A domain that has passed through five registrants in four years is not automatically tainted, but each transfer is a potential link in the chain that requires explanation.

The trap at this step is coverage gaps. Historical WHOIS archive sources do not capture every change, and privacy masking reduces the utility of older snapshots. If the record shows a registrant as a privacy proxy throughout a four-year period, you may not be able to reconstruct who actually held the domain in economic terms without asking the registrar directly – and the registrar will typically respond only to a formal legal process or to the current account holder's written request for their own transfer log.

Instruct the seller to produce the transfer authorization records from their registrar account. A cooperative seller in a legitimate transaction will have no objection to providing the full transfer log. Reluctance to produce that record is itself a material red flag.

If the historical record is incomplete or the seller is unable to produce a clean transfer log, the acquisition carries title risk. For a read on whether the chain you have assembled is sufficient to support the transaction, contact info@cognomenlaw.com.

Step 3: Search the prior-dispute record across UDRP providers and the registry

Once you have the registrant history, search for any UDRP complaints filed against any registrant in the chain. The .store domain operates under the UDRP, meaning WIPO and the Forum are the primary providers, with the Czech Arbitration Court (CAC) and ADNDRC handling a smaller proportion of filings. Each provider maintains a public decisions database.

Search by domain name across all four provider databases. A decided UDRP complaint against the domain – regardless of outcome – is the most important single data point in the verification exercise. Why? Because a complaint that was denied, or that was withdrawn by the complainant, may leave an unresolved trademark claim that can be refiled. Under the UDRP, a prior complaint does not create res judicata in the sense that precludes a later, better-pleaded case. A complainant who filed prematurely and withdrew can return.

The trap here is the partial search. Many buyers search one database – typically WIPO's – and stop. That misses Forum decisions, CAC decisions, and ADNDRC decisions. Given that WIPO and the Forum together account for roughly 97% of all UDRP proceedings, a two-database search covers the large majority – but the CAC and ADNDRC archives are small and searchable in minutes. Search all four.

Also check the .store registry directly for any registry-level dispute notation. Registries handling new gTLDs have mechanisms to flag domains under hold or dispute status. A domain in "serverHold" status or flagged with a registrar lock that predates the current transaction should halt the process pending explanation.

In a matter we handled in spring 2025 – a .store domain purchase for a mid-size retailer – a full four-database search revealed a Forum complaint filed approximately eighteen months earlier and then withdrawn by the complainant. The withdrawal had no finding on the merits. The complainant's trademark registration remained active. We advised the client that the name carried residual litigation risk and recommended they either renegotiate the price to reflect that risk or identify an alternative name. The transaction closed on revised terms.

Step 4: Run a trademark clearinghouse and live trademark search against the domain string

A clean dispute record tells you no one has yet filed – not that no one can. The fourth step is a prospective trademark analysis: does the domain string, or any dominant element of it, correspond to a mark that a third party holds and could assert in a UDRP complaint against the new registrant?

The UDRP's first element requires only confusing similarity to a mark in which the complainant has rights. The .store extension is typically discounted as a generic TLD suffix by panels, meaning the substantive comparison runs between the second-level string and the asserted mark. A domain like "brandname.store" is assessed against "BRANDNAME" or similar marks exactly as "brandname.com" would be.

Search the relevant trademark registers – at minimum the USPTO, EUIPO, and WIPO's Madrid database – for live registrations that correspond to the dominant element of the domain. Expand the search to pending applications, which do not yet confer enforceable trademark rights but signal a future risk. A pending application in the relevant commercial class, filed before the domain's registration date, is a fact a panel will consider when assessing bad faith at the moment of registration.

The trap at this step is assuming that because the domain is a dictionary word or a descriptive phrase, no trademark claim can attach. Panels have consistently held that a generic term can form the basis of a UDRP complaint if the complainant's mark is registered and the domain was registered with the complainant in mind. The domain's commercial use context – a .store suffix pointing to a retail operation – makes that inference easier, not harder, for a complainant to draw.

If the trademark search reveals overlapping registrations or a prior complaint history, a forum analysis can map the realistic exposure before you commit. Email info@cognomenlaw.com to weigh the UDRP exposure against the transaction value.

Step 5: Structure the escrow and confirm the transfer mechanism

Chain-of-title verification does not end with the legal analysis. The fifth step addresses the transfer mechanics: how the domain will move from the seller's registrar account to the buyer's, and how to ensure that process is documented and protected by escrow.

Use a regulated escrow provider for any .store transaction of material value. The escrow structure should hold the purchase funds in trust until the domain has completed a full registrar-side transfer to the buyer's designated account and the WHOIS/RDDS record reflects the buyer as the new registrant of record. Release of funds before that confirmation is complete is the single most common cause of transaction disputes in the domain market.

Confirm the registrar's transfer policy for the .store zone. ICANN's inter-registrar transfer policy applies to all gTLDs, including .store, and a domain cannot normally be transferred within 60 days of a prior transfer. If the seller acquired the domain recently – within that 60-day window – the transfer to the buyer may be blocked at the registrar level. A seller who did not disclose a recent prior transfer should be treated with heightened suspicion at this stage.

The trap here is the auth-code delivery risk. The seller may offer to deliver the EPP auth-code before funds are released from escrow, relying on the buyer's trust to not use it until payment clears. Do not accept that structure. A properly organized escrow and transfer process coordinates auth-code delivery, registrar-side push or pull, and fund release within a single controlled sequence. Any deviation from that sequence benefits the seller at the buyer's expense.

Step 6: Execute the assignment agreement and record the transfer

The registrar-side transfer moves the domain administratively. It does not, by itself, create a documented contractual chain of title. Step six is a written domain assignment agreement that records the legal transfer of all rights in the domain from the seller to the buyer.

The assignment agreement should identify the domain by full name including the .store extension, reference the consideration, confirm the seller's warranty that they hold the domain free of any undisclosed dispute or encumbrance, and include an indemnity from the seller for any UDRP complaint, court claim, or third-party demand arising from the seller's registration or use of the domain prior to the transfer date.

For .store domains used in commerce – the obvious intended use for the extension – the agreement should also address trademark rights. If the seller also holds a trademark registration that covers the domain string, that registration should be assigned or licensed alongside the domain. A domain transferred without the underlying trademark is an asset with a structural gap: the buyer holds the name but another party holds the mark, creating the conditions for a future UDRP complaint by the same seller who just sold them the domain.

We have defended registrants in exactly this scenario. In a matter from autumn 2024, a .store domain buyer acquired the name in a well-structured registrar transfer but omitted a written assignment. The original seller later filed a UDRP complaint asserting trademark rights in the exact string. The buyer's defense rested on establishing legitimate interest through the purchase, but the absence of a written agreement meant the legitimacy argument relied entirely on extrinsic evidence. The panel ultimately found for the respondent on the facts, but the litigation cost substantially exceeded what a one-page assignment agreement would have cost at closing.

Related at COGNOMEN

• Domain transactions, due diligence, and brand-protection services
• Domain assignment agreements: structure, drafting, and cross-border issues
• How to suspend a new-gTLD domain under the URS in finance disputes