.cloud WHOIS Lookup
.cloud is a generic extension operated by the Italian company ARUBA PEC. Look up a .cloud address and see what the record contains.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.cloud WHOIS Lookup: Two Channels, One Record
.cloud is a generic extension that entered the root zone on 18 June 2015, operated by ARUBA PEC S.p.A. of Italy. Port 43 queries are answered by whois.nic.cloud, which returned fourteen fields in our measurement on 12 August 2026, and an RDAP endpoint runs at rdap.registry.cloud. The zone holds a DS record in the root.
This extension is one of the cases where both channels remain open on the generic side. Under many newer extensions the WHOIS service has been retired and RDAP is the only address; here the two run together. In our measurement both returned the same record: creation, update and expiry dates, the registrar's name and IANA number, an abuse contact, name servers and status codes. The difference is not scope but form — one replies in plain text, the other in structured data.
No field for a registrant exists at registry level, which is the shared trait of the newer generic extensions. Identity data sits with the registrar that sold the name, and the reply states that registrar's name, number and reporting channel plainly. To compare an extension whose WHOIS service has closed see the .shop WHOIS lookup, and for another sharing the same narrow schema, the .online WHOIS lookup page.
About the .cloud extension
- Extension
- .cloud
- WHOIS server
- whois.nic.cloud
- RDAP endpoint
- https://rdap.registry.cloud/rdap
- Registry
- ARUBA PEC S.p.A., Italy
- Delegated
- 18 June 2015
- Fields measured
- 14 fields (12 August 2026)
- Channels
- Port 43 and the RDAP endpoint run together and carry the same record
- Withheld
- Registrant fields are not opened at registry level
WHOIS FAQ
Is the WHOIS service still running for .cloud?
It is. In the 12 August 2026 measurement whois.nic.cloud answered on port 43 and returned a record of fourteen fields. That is no longer true of every extension on the generic side: under many newer ones WHOIS has been retired and RDAP is the only address. .cloud is one of the cases keeping both channels open.
Is there a difference between RDAP and WHOIS under .cloud?
Not in scope, but in form. In our measurement both channels returned the same record: the dates, the registrar, the name servers and the status codes. WHOIS replies in plain text and suits reading by eye; RDAP delivers the same information structured, lowering the risk of mismatched fields in automated systems. Which to choose depends on who will read the result.
Does a .cloud WHOIS lookup show the domain holder?
It does not. No field for a registrant exists at registry level, which is the shared trait of the newer generic extensions. What the reply does carry plainly is the name of the registrar that sold the domain, its IANA number and an email address and phone number for abuse reports. Where identity is needed, that registrar's own channel is the step that works.
Does a .cloud record show creation and expiry dates?
It does. The reply gives the creation date, the last modification and the expiry date in UTC, and the same three values arrive as events on the RDAP side. Our result screen derives the domain's age and its remaining term from them. As the term runs short we turn the indicator to a warning colour, so the renewal window is hard to miss.
Who sets the status codes in a .cloud record?
The codes come from ICANN's shared EPP vocabulary and the prefix tells you who set them. Codes beginning with client are set by the registrar managing the name and lifted by it on request; codes beginning with server are set by the registry and the registrar cannot lift them. Our result screen prints what each code blocks, so you can read why a name cannot be transferred without memorising codes.
How does an available .cloud name appear in a lookup?
Query a name nobody holds and the registry reports that no match was found, with none of the fourteen fields present. That means the name looks free to register. We keep such a result for five minutes only and registered ones for six hours, the short window being there because a name that looks free can be taken quickly.