Enter Anguilla market with a .COM.AI Domain

No. The .ai namespace and .com.ai beneath it are unrestricted: there is no residency requirement in Anguilla, no local address, no local representative and no trustee, and the extension can be registered from anywhere in the world. The published rules look not at who takes a name but at how it is used; abusive use covers malware distribution, phishing, DNS hijacking, spam, botnets and trademark infringement. Registrations are not filed with the registry directly but submitted through an accredited registrar. Measurement bears this out: among .com.ai records queried on 16 August 2026 the holders include companies in the United States and holders based in China, with no Anguilla connection required.

The difference is one of level, not of registry. The extension that sits in the root zone is .ai; .com.ai is not a separate delegation but a third-level branch served from inside that same zone. This is measurable: .com.ai has no name server set of its own and no DNSSEC key of its own, and queries for it are answered by the .ai zone. The practical result is that both fall under the same registry, the same whois server and the same term and dispute rules, with no extra eligibility test or document requirement for .com.ai. One detail matters: holding a name in .ai creates no right to the same name in .com.ai.

From two years up to ten. There is no one-year option in this zone: the floor is two years both for a new registration and for a renewal. A transfer carries its own consequence — once a change of registrar completes, the registration is extended by two years rather than one, so the cost of a transfer should be planned as a two-year renewal. Measurement supports this: for records created on the registry's current platform, the gap between creation and expiry always comes out as an even number of years — a .com.ai name registered on 4 April 2025, for instance, expires on 4 April 2027. Renewing early costs you nothing, because the new period starts from the end of the previous one.

One character, which is rare among country extensions and is confirmed by measurement. On 16 August 2026 the single-letter names a.com.ai, b.com.ai, x.com.ai and q.com.ai were all registered, as were the single-digit names 0, 2, 3, 5, 7 and 9. Most of those records were created in 2023 and 2024, so short names are a current option rather than a legacy leftover. Two limits apply: a name may not begin or end with a hyphen, and such queries are rejected as a malformed request. The registry also keeps an unpublished list of reserved names, which a lookup reports explicitly. Screen your candidates on the domain name search page.

Yes, they are. .com.ai records sit in a thick registry: registrant, administrative and technical contact details are all mandatory and all published in a public lookup. The «REDACTED FOR PRIVACY» masking familiar from generic extensions is not applied in this zone. In the measurement carried out on 16 August 2026, the holder's name, street address, city, postal code, telephone number and email address could be read straight off the .com.ai records queried. The practical consequence is direct: enter your home address and mobile number and they land in a record anyone can query, which is why a company address and a role mailbox are the sounder choice. Inspect your own record on the whois search page.

The name is not deleted immediately; it enters a two-stage chain. First comes an auto-renew grace period of forty-five (45) days, during which renewal is still possible. If the name is not renewed within that window it is deleted and enters a thirty (30) day redemption period, followed by a five (5) day hold, after which the name is released again. Measurement confirms this on live records: on 16 August 2026 a .com.ai name that expired on 12 June 2026 carried the status codes «redemptionPeriod» and «inactive». That second code is the critical one — even while the name is still recoverable it has been dropped from the name servers, so the site and email stop working.

A change of registrar runs on an authorisation code: you obtain the code from your current provider and hand it to the new one. Two points are worth knowing beforehand. First, once the transfer completes the registration is extended by two years, not one, which is unlike generic extensions and should be budgeted accordingly. Second, most .com.ai records carry a registrar-applied transfer lock; this is not a prohibition, but you must have your provider lift it before the request is filed, otherwise the transfer is refused. Measurement shows transfers working in practice: one of the records queried carries a transfer event dated 13 September 2024. Start the process on the domain transfer page.

Through the UDRP. The registry states it plainly on its own policy page: the .ai registry adheres to the Uniform Domain-Name Dispute Resolution Policy, and proceedings must be initiated through one of the ICANN-approved dispute resolution service providers. That is not a given for a country extension — .ai sits outside the ICANN registry agreement framework that binds generic extensions, so the registry has adopted the UDRP voluntarily. For a trademark owner the effect is favourable: instead of learning a local Anguillan procedure you follow a familiar and predictable route. Abuse reports are a separate track and go first to the name's registrar. For help with either, write to us from the contact page.