The Registration-Date Problem in .ai Domain Disputes

How to evaluate plans, archived pages and later sale evidence

Wei Bin | LONG AN LAW FIRM | September 2026

The commercial value of an .ai domain can change rapidly. A name registered before a product launch may later attract attention from a brand owner. A domain acquired for a proposed artificial-intelligence project may remain unused, display a temporary page or later be offered for sale. By the time a UDRP complaint is filed, the available evidence may describe several different periods.

The central discipline is simple: do not compress those periods into one story.

Registration, acquisition and later use are separate events

Paragraph 4(a)(iii) of the ICANN UDRP Policy requires a complainant to prove that the domain was registered and is being used in bad faith. Paragraph 4(b) lists non-exclusive circumstances that may evidence bad faith, including acquisition primarily for sale to the trademark owner or a competitor, a pattern of blocking registrations, disruption of a competitor and intentionally attracting users for commercial gain through confusion.

The date that matters cannot always be identified from the current registrar record alone. A domain may have been registered on one date and acquired by the current holder later. Renewal, registrar transfer, account transfer and change of registrant should not automatically be treated as the same event. The factual investigation should ask:

• When was the domain first registered?
• When did the current holder acquire control?
• Was there a material change in registrant or beneficial ownership?
• When did the complainant’s relevant trademark rights and reputation arise?
• What use, preparations or communications existed at each stage?

The legal significance of an acquisition or change in control depends on the facts and applicable UDRP principles. The research record should first preserve the events accurately before characterising them.

Four dates for every item of evidence

A useful chronology assigns four possible dates to each piece of evidence:

1. Event date — when the act described actually occurred.
2. Creation date — when the document, file or webpage was created.
3. Collection date — when counsel or a party obtained the item.
4. Assertion date — when a party first used the item to explain its position.

These dates may be different. A declaration signed after the complaint can describe an earlier event. A screenshot collected after notice can capture a page created before notice. Metadata may show when a file was last modified but not prove when a business decision was made. An archived page may provide independent evidence that content was publicly available by the archive date, while leaving authorship or completeness unresolved.

The chronology should not force every item into the registration-date column. It should show the relationship between the evidence and the event it is offered to prove.

What CAC-UDRP-108841 shows

The decision in CAC-UDRP-108841, concerning 1688.ai, is a useful illustration because the panel did not treat all respondent material as equally probative.

The domain was registered on 11 July 2023. The respondent relied on an explanation involving the number 1688 and an asserted artificial-intelligence purpose. The panel stated that the numerical explanation, standing alone, was not sufficient.

The record also contained materials connected with an AI or QiaPi project. Their source files were created or modified in September 2023, and an interface design dated from October 2023—approximately two to three months after registration. The panel observed that these materials did not directly refer to 1688.ai. They nevertheless provided contemporaneous evidence of the respondent’s involvement in AI-related activities shortly after registration.

A different item carried greater weight: an archived webpage titled “The Way to AGI,” dated 2 April 2025. It predated the 2026 dispute and showed the domain resolving to a webpage presenting an AGI theme. The panel described its timing and content as more significant in the legitimate-interest analysis.

The case therefore does not establish that any later AI project proves a legitimate interest in an .ai domain. It shows a layered evaluation:

• numerical or cultural meaning was an explanation, not sufficient proof by itself;
• project material close in time to registration supported involvement in AI activity but lacked a direct domain connection;
• a later archived page had a stronger domain-specific connection and still predated the dispute;
• later sale evidence did not, on that record, establish the holder’s purpose at registration.

The complaint was denied, but the result should remain tied to the evidence and reasoning in that case.

Plans and preparations need a domain connection

Paragraph 4(c)(i) of the Policy refers to use, or demonstrable preparations to use, the domain or a name corresponding to the domain in connection with a bona fide offering before notice of the dispute.

For a proposed AI project, relevant materials may include:

• dated naming documents or product specifications;
• code repositories and development logs;
• designs identifying the domain or corresponding project name;
• hosting, cloud or software expenditure;
• contracts with developers or designers;
• internal approvals and budgets;
• test-user records;
• archived webpages;
• contemporaneous communications explaining the name selection.

Quantity is less important than connection. A large collection of generic AI materials may prove that the holder worked in artificial intelligence without proving preparations to use the disputed domain. A single dated document that identifies the domain, the project and the intended offering may be more useful.

Counsel should also test authenticity and context. Metadata can be altered. Internal documents can be created retrospectively. Repository dates may reflect migration rather than original work. The response should explain provenance and, where possible, corroborate the material through independent records.

The .ai suffix proves very little by itself

The country-code top-level domain .ai is widely used for artificial-intelligence projects, but the suffix should remain a separate variable from the holder’s purpose. The string can show that the registered name uses .ai. It does not establish that the registrant operated an AI business, selected the name independently or had no knowledge of another party’s mark.

This distinction works in both directions. A brand owner should not treat every .ai registration as proof of targeting simply because its business involves AI. A domain holder should not treat the suffix as proof of a bona fide AI plan.

The investigation should connect the second-level name, the proposed project, the holder’s activity and the relevant dates.

Sale evidence needs careful timing

An offer to sell may be relevant under paragraph 4(b)(i), but the existence and timing of the offer matter. Ask:

• Who made the offer?
• Was it directed to the complainant, a competitor or the public?
• When did the listing or communication first appear?
• What price or terms were stated?
• Did the holder initiate the approach, or respond to an enquiry?
• How long after registration did the offer occur?
• What use or preparations occurred before the offer?

A current marketplace listing should not automatically be back-filled to the registration date. Nor should a respondent assume that a late listing is irrelevant. It may form part of the overall record, particularly when combined with targeting, a pattern of conduct or inconsistent explanations.

Describe the proposition narrowly. “The domain was listed for sale on date X” is different from “the domain was registered primarily to sell it to the complainant.” The first may be directly evidenced; the second is an inference that must be supported by the full record.

Inactivity is a state, not a complete history

A blank or inactive website records what appeared at a particular time. It does not show automatically that the domain was never used, that no preparations existed or that the holder acted in good faith. Preserve:

• current DNS and website status;
• historical screenshots and web archives;
• hosting and email configuration;
• prior redirects;
• development and deployment records;
• communications explaining suspension or delay.

For a complainant, passive holding may still be relevant to bad faith under the circumstances described in UDRP practice. For a respondent, documented preparations may matter even without a public launch. Neither side should stop the analysis at “the page is blank.”

A chronology that counsel can audit

The final chronology should have one row per event and separate columns for the event date, evidence date, source, proposition, limitations and reviewer. It should visibly distinguish:

• facts found or recorded by the panel;
• a party’s assertion;
• an inference proposed by counsel;
• facts that remain unknown.

The discipline is particularly useful in fast-moving AI markets, where a later commercial narrative can appear plausible. The UDRP question still depends on what the evidence shows about the relevant times and the connection between the domain, the holder’s purpose and the complainant’s rights.

The cited decision is a public research source and was not presented as a matter handled by the author. This article provides general research commentary, not advice on any specific domain or proceeding.