.ai WHOIS Lookup
.ai is the country-code extension of Anguilla, widely used by technology sites. This page explains which fields the registry publishes.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.ai WHOIS Lookup: What the Registry Publishes
.ai is the country-code extension of Anguilla, delegated into the root zone on 16 February 1995; IANA's record names the government of Anguilla as the sponsoring organisation. Queries are answered by whois.nic.ai on port 43, and in our measurement on 12 August 2026 the reply carried fifty-four field labels. The extension's RDAP endpoint runs at rdap.identitydigital.services, an address also used by generic extensions, and the zone carries a DS record in the root.
Most of those fifty-four fields sit on the identity side: for the registrant, the administrative and the technical contact there are separate lines for name, organisation, street, city, state, postal code, country, phone, fax and email. In the record we measured, none of these were empty or closed — the name, the organisation, the address and the email could all be read. The reason is that the record belonged to an organisation: the masking settled since 25 May 2018 covers contact data of natural persons and is not mandatory for legal entities.
When data is withheld, it is not withheld silently: the terms of use section in the reply states that unpublished data is marked with its own tag. The same section reports that queries are throttled and that a burst of requests from a single address will be refused for a while. To see how a schema of similar width looks when its values are closed, visit .io WHOIS lookup; for an extension that closes its contact blocks at differing levels, .me WHOIS lookup.
About the .ai extension
- Extension
- .ai
- WHOIS server
- whois.nic.ai
- RDAP endpoint
- https://rdap.identitydigital.services/rdap
- Registry
- The government of Anguilla, per the IANA record
- Delegated
- 16 February 1995
- Measured field count
- 54 field labels (12 August 2026)
- RDAP endpoint
- rdap.identitydigital.services — the address used by generic extensions
- Measured record
- Identity lines open; the record belonged to an organisation (12 August 2026)
WHOIS FAQ
Does an .ai WHOIS lookup show the registrant's name?
It can. In our measurement on 12 August 2026 the registrant block in the reply was populated: the name, organisation, street, city, country and email lines could all be read. Blocks of the same width were present for the administrative and technical contacts. That means the extension does publish identity data, but do not expect the same outcome in every record, because the rule on withholding follows who holds the domain.
Why are contact lines closed in some .ai records?
Because masking is applied according to who holds the record. Contact data belonging to natural persons has been published in closed form since 25 May 2018, while no such obligation covers legal entities. So an address held by a company can show a name and an email while the same lines arrive closed for an address held by a private person. The difference between two replies is not registry inconsistency but the rule itself.
How is withheld data marked in an .ai record?
The terms of use section of the reply states that data which is not published carries its own tag. The practical value of that is simple: a field being closed is not the same as a field being absent from the record, and the tag separates the two. Where you see a marker instead of a value, the data exists and has only been withheld from publication.
Are .ai queries subject to rate limiting?
They are. The terms of use section in the reply states plainly that queries to the service are throttled and that too many requests from a single address within a short window will be refused for a period. The same text notes that bulk collection attempts are detected and limited. A client firing queries back to back can therefore receive empty or failed answers for a while.
Where does the RDAP endpoint for .ai run?
At rdap.identitydigital.services. That endpoint also answers registration data for many generic extensions, and there is nothing unusual about a country extension being served from the same platform. In the 12 August 2026 measurement it listed registrant, administrative and technical roles alongside the registrar role, and it showed a contact name. The events it carried were registration, expiration and last changed.
Is the .ai zone signed with DNSSEC?
The zone is signed: we confirmed a DS record for .ai in the root zone in the measurement of 12 August 2026. Individual addresses are a separate question, and the reply carries its own DNSSEC field for that; in the record we measured, that field read unsigned. A signed zone therefore does not mean that every address inside it is signed.