Step-by-step: verify chain of title for a .ai domain
A buyer agrees to pay a substantial sum for a premium .ai domain. Escrow is ready. Then due diligence turns up a registrar transfer from three years ago with no documented consent from the original registrant, a prior UDRP complaint that was withdrawn under undisclosed terms, and a WHOIS history that skips two registration cycles. The deal is now a liability, not an asset.
To verify chain of title for a .ai domain, you need to confirm that every transfer in the domain's history was authorized, that no unresolved dispute or court order clouds the current holder's title, and that the registration itself is in good standing with the Anguilla Internet Corporation (AIC). The .ai zone has adopted WIPO as its dispute-resolution provider, meaning UDRP complaints can follow the domain into a buyer's hands if prior bad faith is established. A clean chain of title review involves at minimum five sequential checks before any funds move.
This guide sets out each step, the trap hidden in it, and the practical remedies available when something surfaces.
Why .ai chain-of-title verification is different from a standard .com check
The .ai zone is administered by the Anguilla Internet Corporation and operates under its own registration policies, which are distinct from the ICANN Registrar Accreditation Agreement that governs .com. That jurisdictional gap matters at every step of a title check.
Registrar choice is narrower. A smaller number of accredited registrars service .ai, and some do not support the same WHOIS history exports that generic-TLD registrars provide as a routine function. A buyer who relies on a single RDDS query is looking at a snapshot, not a film. The full registration timeline – original creation date, all expiration and renewal events, every recorded transfer – must be reconstructed from multiple sources, including the AIC registry itself, historical WHOIS archives, and escrow or transaction records from prior sales.
At the same time, .ai has adopted WIPO as its dispute-resolution provider. This means the UDRP applies: a complainant with trademark rights can challenge a registrant who acquired the domain with knowledge of prior bad faith, and that challenge can proceed even after a sale. Buying a tainted domain is not a clean break. In our practice, we have seen acquirers face UDRP filings within months of closing, where the complainant's case rested entirely on the prior holder's conduct rather than the buyer's own.
The combination – limited registry transparency and full UDRP exposure – makes .ai one of the higher-risk ccTLDs for unverified acquisitions.
Step 1: pull the registration record from the AIC registry and cross-reference it with historical WHOIS archives
The first step is to obtain the current registration record directly from the AIC registry or through an accredited .ai registrar, and then cross-reference it against at least two independent WHOIS history services to identify gaps. This is the baseline. Without it, every subsequent step is anchored to incomplete data.
What you are looking for: the original creation date, the current expiration date, the registered name server history, and every recorded sponsoring registrar change. A sponsoring registrar change is not the same as a registrant transfer, but it sometimes masks one. When a domain moves from one registrar to another, the WHOIS record is often partially reset – a trap that catches buyers who interpret a short WHOIS age as proof of a recently created domain, when in fact it reflects a registrar migration of a decade-old registration.
The trap in Step 1: WHOIS history archives are incomplete for .ai. Unlike .com, where several commercial services maintain deep crawl archives dating back to the late 1990s, .ai records in third-party archives often begin only in the mid-2010s or later. Gaps in that archive do not mean the domain was unregistered during those periods. They mean data was not captured. The only authoritative source for the full creation timeline is the AIC registry itself. Request the registry's own registration history record – some registrars can pull this on your behalf; for direct access, a formal request to the registry may be required.
Confirm: creation date, all expiry and renewal events, and whether the domain has ever lapsed into redemption grace period or dropped status. A domain that briefly dropped and was re-registered by a new party has, in substance, a new title chain from that drop date – prior rights and prior disputes do not automatically attach, but a gap in the chain must be documented, not assumed.
Step 2: map every recorded transfer and obtain the authorizing instrument for each
Each transfer in the domain's recorded history should have a corresponding instrument: a sale agreement, a registrar-to-registrar transfer confirmation, a corporate succession document, or in the case of an estate, a grant of administration. Map them chronologically. Any transfer without a documented instrument is a gap that must be resolved before closing.
In practice, most private domain sales before 2018 were informal. A buyer paid; the seller pushed the transfer; no written agreement exists. That informality does not automatically invalidate the transfer, but it creates two risks. First, if the original transferor later claims the domain was taken without consent – because an account was compromised, because a business partner acted outside their authority, or because the transfer was induced by fraud – the current holder's title may be challenged. Second, under the UDRP, a panel examining bad-faith registration looks at the intent at the time of registration. A murky transfer history makes it harder to establish that the current registrant (the buyer) acquired in good faith and for value, which is a factor panels consider.
The trap in Step 2: corporate chain-of-title breaks. A domain originally registered to Company A, which merged into Company B, which was then acquired by an individual who later sold it to the current holder, requires a complete corporate succession trail. A gap in that corporate trail – a dissolved entity that appears in the chain without a successor instrument – is a serious defect. We have advised buyers who only discovered a dissolved-entity gap after escrow closed, requiring registrar escalation and registry correction before the domain could be put to commercial use.
For a read on whether the three UDRP elements are met in a .ai acquisition dispute, reach us at info@cognomenlaw.com.
Step 3: search the WIPO and Forum case databases for prior dispute history
Before any funds move, run a complete dispute-history search across the WIPO and Forum case databases using the domain name as a search term. This surfaces every UDRP complaint that named the domain – whether decided, withdrawn, or settled – and any URS filing, if applicable. This step cannot be skipped and cannot be delegated to a general trademark search.
A decided complaint is not automatically disqualifying, but it requires analysis. If the complaint was denied – the panel found for the respondent – that decision does not bind a future complainant; the UDRP is not a court and prior panel decisions do not create issue preclusion in the legal sense. A complainant with stronger evidence or a more recent trademark registration can refile. In our practice, we have seen serial UDRP campaigns where a first complaint failed and a second, filed after additional trademark registrations were obtained, succeeded against a subsequent acquirer who had not investigated the first proceeding.
A complaint that was withdrawn before a decision is more ambiguous. Withdrawal before panel appointment often reflects a settlement. That settlement may contain a standstill agreement, a license, or a covenant not to sue – obligations that may bind the current holder if the settlement was between the prior registrant and the complainant. If you are buying a domain and the WIPO or Forum record shows a withdrawal, you must obtain and review the settlement agreement before closing. Buying into an undisclosed settlement is buying into an undisclosed obligation.
What about the WIPO Jurisprudential Overview's treatment of serial complainants or known cybersquatting patterns? If the prior registrant appears in WIPO case records as a respondent in multiple cases – a pattern of abusive registrations under Paragraph 4(b) of the UDRP – that history does not automatically infect the buyer. But it signals that the domain may have been held in bad faith, that a future complainant knows the prior record, and that any offer to purchase made before due diligence closes might later be characterized as notice of a dispute. Time the due diligence accordingly: complete it before making any written offer or paying any deposit.
Step 4: assess trademark risk against the domain's literal string
A clean transfer history and a clear dispute record do not resolve the trademark question. The domain may be free of prior UDRP proceedings simply because the mark owner has not yet filed. Assess the domain's literal string against live trademark registers – at minimum, the USPTO, EUIPO, UKIPO, and WIPO's Madrid database – and against unregistered rights in the key markets where the domain will be used.
The UDRP's first element is satisfied if a complainant holds a trademark that is identical or confusingly similar to the domain. That trademark need not predate the domain's creation; panels have accepted trademarks registered after the domain was created where the complainant can show the domain was registered in anticipation of the mark or with knowledge of unregistered rights. That is a harder case for a complainant, but it is not a foreclosed one.
For .ai domains in particular, the artificial-intelligence sector has generated a wave of trademark filings since 2022, many of them for terms that are descriptive or weakly distinctive standing alone. A buyer of a generic or descriptive .ai domain faces lower risk from established marks, but higher risk from the proliferation of new filings in a crowded field. The practical check: run a live trademark search on the exact string plus any dominant element, note any marks registered in Classes 9, 35, 38, and 42 (the classes most associated with software and technology services), and flag any that are confusingly close to the domain. If any are found, assess the registrant's plausible legitimate interest before closing.
The trap in Step 4: pending applications. A trademark application that is pending at the USPTO or EUIPO does not currently give the applicant UDRP rights, but it may be published, allowed, and registered within twelve to eighteen months of a closing date. A buyer who acquires in good faith today may face a UDRP complaint from a recently matured registration. If a pending application for a confusingly similar mark is identified during due diligence, factor the risk into the purchase price or negotiate a representation and warranty from the seller covering any UDRP exposure arising from pre-sale trademark filings.
How do prior owners' actions affect your UDRP exposure after acquisition?
A buyer who acquires a domain does not inherit the prior registrant's bad faith as a matter of UDRP doctrine – but the prior conduct of the domain affects the buyer's practical exposure in three concrete ways. Understanding these is central to structuring a safe acquisition.
First, a known dispute history is notice. Under the UDRP, one element of bad faith is that the registrant registered the domain primarily to sell it to the mark owner at a price in excess of out-of-pocket costs. A buyer who acquires a domain with knowledge of a pending or prior complaint, and who then attempts to sell it to the mark owner at a premium, may satisfy that element. The knowledge gathered in Step 3 of this guide must be factored into any post-closing strategy for the domain.
Second, passive holding after acquisition carries risk. Panels have consistently held that holding a domain without active use – the "passive holding" doctrine – can constitute bad faith use, particularly where the domain corresponds to a well-known mark and the registrant has no obvious legitimate interest. A buyer who parks a .ai domain corresponding to a mark, even without monetizing it, is not automatically safe. The better posture: put the domain to its intended commercial use promptly after closing, and document that use.
Third, the timing of acquisition matters. Acquiring a domain at a time when the buyer knew – or should have known – that a complainant was likely to file is a factor panels have weighed. If due diligence surfaces a trademark owner who has sent a cease-and-desist letter to the prior registrant, that letter may be producible in a UDRP proceeding. Insist on full seller disclosure of any correspondence from third parties about the domain as a condition of closing.
In a matter handled in spring 2025 (a premium .ai domain in the technology sector, five-figure acquisition price), we identified a prior undisclosed settlement in the WIPO database during pre-closing review. The settlement contained a license limited to the prior registrant. The buyer's counsel renegotiated the transaction to include a seller indemnity and a price reduction reflecting the settlement liability. The domain transferred without incident, but only because the due-diligence step was taken before, not after, the deposit was paid.
Step 5: structure the escrow and the representations in the purchase agreement
Escrow is not optional for domain acquisitions above a minimal threshold. It protects both parties, but it does not substitute for due diligence. Structure the escrow to hold funds until the full post-transfer verification is complete – not until the registrar push, which may take place before the registry and WHOIS record fully reflect the new registrant.
A well-structured .ai domain purchase agreement should include at minimum the following representations from the seller: (1) the seller is the registered holder of record and has full authority to transfer; (2) no UDRP, URS, court, or registry dispute is pending or, to the seller's knowledge, threatened; (3) no settlement, license, or covenant relating to the domain exists with any third party; (4) the registration is in good standing, paid current, and not subject to registrar lock arising from a dispute, non-payment, or administrative hold; and (5) the seller has not received any written claim or cease-and-desist from any party regarding the domain in the preceding period (define the period in the agreement).
The trap in Step 5: domain-specific escrow mechanics for .ai. Not all mainstream escrow providers support .ai registrar mechanics equally well. Confirm before opening escrow that the provider has a working relationship with the specific registrar holding the domain and can facilitate a verified push or auth-code transfer without requiring the domain to move to an intermediate registrar. An unauthorized mid-transaction registrar change can trigger a 60-day transfer lock, delaying the buyer's ability to use the domain and, in the worst case, creating a gap in the chain of title at exactly the moment funds are released.
To assess whether a .ai domain acquisition is structured to minimize UDRP and title risk, email info@cognomenlaw.com.
What evidence decides the outcome when a title dispute arises after acquisition?
When a UDRP complaint is filed against a buyer who completed due diligence in good faith, the evidence assembled during that due diligence is the defense. A buyer who can produce a complete chain-of-title record, the results of trademark searches run before closing, the WIPO and Forum history review, the seller's representations, and documented post-transfer use of the domain for legitimate commercial purposes is in a materially stronger position than one who cannot.
Panels assess legitimate interest under Paragraph 4(c) of the UDRP, which lists three safe harbors: a bona fide offering of goods or services before notice of the dispute; the respondent's being commonly known by the domain name; and legitimate noncommercial or fair use. For a buyer who uses a .ai domain for its artificial-intelligence product or service, the first safe harbor is directly available. Establishing it requires concrete evidence: launch records, product documentation, marketing spend, or customer records that predate any complaint filing.
The fact pattern that decides most post-acquisition disputes is straightforward: what did the buyer know at the time of acquisition, and what did the buyer do with the domain afterward? A buyer who acquired without review, parked the domain, and then received a complaint has limited documentary defenses. A buyer who followed the steps in this guide – and documented each step – has a paper trail that serves both as a factual defense and as the foundation for an RDNH claim if the complaint is itself abusive.
Reverse Domain Name Hijacking (RDNH) is a finding available where a panel concludes the complaint was brought in bad faith to strip a legitimate registrant of the domain. An RDNH finding is reputational rather than financial – it carries no monetary award – but it is a significant outcome for a buyer who has invested in due diligence and can demonstrate it.
In a second matter, handled in autumn 2025 (a .ai domain acquired by a technology startup for active product use, a six-figure acquisition), a complainant filed a UDRP complaint arguing the registrant held the domain to prevent the complainant from reflecting its mark in the zone. We produced the pre-closing due-diligence record, the escrow documentation, the seller's representations, and six months of active product use. The panel denied the complaint and made an RDNH finding against the complainant. The key was documentation assembled before the complaint arrived, not after.
Cross-zone and cross-forum considerations: .ai versus .com and other zones
A .ai acquisition does not exist in isolation. If the target brand also holds or seeks to hold the corresponding .com, .io, or other zone registrations, the title verification work should be coordinated across zones – because a UDRP won or lost in the .com space can influence, though does not bind, a subsequent panel in a .ai proceeding over the same string.
If the .com corresponding to the .ai domain you are acquiring is held by a third party, consider the implications before closing. A brand owner who holds the .com and discovers you have acquired the .ai may file a UDRP against both. If the .com is also available for acquisition, the coordinated purchase of both zones – subject to the same due-diligence process run in parallel – reduces the exposure materially.
For .eu domains, the EURid ADR procedure at the Czech Arbitration Court is the applicable forum, and eligibility to hold a .eu registration requires an EU or EEA nexus. For .de, there is no UDRP at all – a dispute requires German court proceedings, with a DENIC DISPUTE entry available to block transfer while litigation proceeds. For .uk under the Nominet DRS, the test is "abusive registration" under a "registered or used" standard, which is a lower threshold than the cumulative "registered and used" requirement under the UDRP. Each of these distinctions matters when a brand dispute spans multiple zones.
Within the gTLD space, a buyer acquiring a .ai domain who also intends to pursue URS relief in a new gTLD should note that the URS remedy is suspension, not transfer. The remedial difference is significant: URS protects but does not acquire.
Where a dispute cannot be resolved through an arbitral procedure – whether because the domain is in a zone without an ADR mechanism or because the relief sought includes monetary damages – anticybersquatting litigation with local litigation counsel in the relevant jurisdiction is the available path. That route is substantially more expensive and slower than a UDRP proceeding, and it should be assessed only where the domain's value or the severity of the conduct warrants it.
Related at COGNOMEN
Frequently asked questions: verify chain of title for a .ai domain
How do I start to verify chain of title for a .ai domain?
Begin by pulling the registration record directly from the AIC registry or through an accredited .ai registrar, and cross-reference it against at least two independent WHOIS history archives. Identify every recorded transfer, every sponsoring registrar change, and every lapse or redemption event. That baseline record drives each subsequent step – trademark search, prior-dispute review, corporate succession check, and escrow structure. Starting with a single RDDS query is not sufficient for a domain acquisition of material value.
What are the realistic outcomes when you verify chain of title for a .ai domain?
Due diligence produces one of three outcomes: a clean title with no obstacles to closing; a curable defect such as a gap in the corporate chain or an undisclosed registrar lock, which can be resolved by seller action or by a price adjustment and warranty before closing; or a non-curable defect such as a pending UDRP complaint or an unresolved settlement obligation, which should halt the transaction or require structured indemnification. The review does not guarantee a clean result – it defines the risk so the buyer can price it accurately.
How do fees split if the case escalates?
If a UDRP complaint is filed after acquisition, the respondent bears the cost of defense. Forum filing fees are paid by the complainant: USD 1,500 at WIPO for a single-member panel covering one to five domains, or the Forum's comparable rate. Legal fees for respondent defense are separate and fact-dependent. If the complainant requested a single panelist but the respondent seeks a three-member panel, the parties generally split the higher three-member fee. Pre-acquisition due-diligence fees are a fixed cost; post-complaint defense fees are variable and substantially higher.
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. Our practice handles .ai and other ccTLD transactions, including pre-acquisition due diligence, chain-of-title verification, and escrow structuring. To discuss a domain acquisition or a .ai dispute, contact 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.