.cloud domain names

What .cloud is

.cloud refers to cloud computing, and is aimed at cloud infrastructure, hosting, SaaS and cloud-adjacent services. IANA classifies it as a generic top-level domain: open and unsponsored, from ICANN's 2012 New gTLD Program.

The registry operator is ARUBA PEC S.p.A. of Ponte San Pietro, Italy, a wholly-owned subsidiary of Aruba S.p.A., one of Europe's largest hosting and cloud providers, with the IANA delegation record last updated in December 2025. Aruba has run .cloud since it won the contention set, with no change of operator identified. That makes .cloud one of very few significant new gTLDs operated by a European hosting company rather than a US portfolio registry or a global technology brand, and the ownership shapes the extension in ways covered below.

Delegation was on 18 June 2015 per the IANA record, which is authoritative for the registration date; Wikipedia gives 26 June. Sunrise ran from 16 November 2015, landrush from 25 January 2016, and general availability opened on 16 February 2016. Back-end registry services were originally provided by ARI Registry Services, later absorbed into Neustar and then GoDaddy Registry; the current provider should be checked against the registry's own documentation rather than inferred from that history.

Technically the extension is unencumbered. It is not on the HSTS preload list, so plain HTTP works and TLS is optional, as with .com. Buyers comparing infrastructure-flavoured extensions frequently assume .app's browser-enforced HTTPS mandate generalises across the category. It does not.

Who can register .cloud

Anyone. The registry imposes no eligibility test. You do not need to operate a cloud service, sell cloud products, or have any technology connection whatsoever. There is no documentation, no verification and no geographic requirement; registration is real time and first-come, first-served. This deserves emphasis because the extension's name implies a category gate that does not exist.

Label syntax follows the standard gTLD pattern: letters, digits and hyphens, with no leading or trailing hyphen and no hyphens in the third and fourth positions, the last rule protecting the reserved prefix used for internationalized domain names. Labels run from one to sixty-three characters, though availability of one- and two-character names is subject to registry reservation policy.

What .cloud costs to own

.cloud is an accessible, volume-oriented new gTLD: its standard registry price sits toward the lower-middle of the range, and it is one of the more aggressively promoted extensions at retail.

The gap between the first year and the renewal is wide, and it is created almost entirely by registrar acquisition promotions rather than by registry pricing. A promotional gap is a one-off saving that reverts on schedule; the standard renewal determines the cost over the name's life, and a batch registered in one promotion reverts on a single anniversary.

Premium tiers exist with elevated recurring renewal pricing on reserved and high-value names, though this is worth verifying: at least one major registrar's documentation does not surface premium tiers for .cloud, and premium tiering has not been confirmed from Aruba's own policies. No .cloud registry increase was identified in the January 2026 round, though absence from one change list is not proof. A lapsed name enters a thirty-day quarantine, restorable only by the original registrant at a fee well above a renewal.

Registration terms, renewals, and transfers

.cloud registers for one to ten years in whole-year increments. Renewal follows the standard gTLD lifecycle, and after deletion a thirty-day quarantine or redemption window applies, with a restore fee, followed by pending delete and release to the available pool.

Transfers use standard ICANN gTLD transfer policy, and registrar documentation sets the conditions out precisely: an authorization code from the losing registrar, no transfer-prohibited status, a domain more than sixty days old, and no transfer within the previous sixty days. A successful transfer automatically renews the domain for one additional year, added to the existing term rather than replacing it.

Registrar-level and registry-level locks are both available, and a registry lock is worth the friction on any .cloud name fronting production infrastructure, since that is exactly where names on this extension tend to sit.

WHOIS, RDAP, and privacy

.cloud is a gTLD, so RDAP, the Registration Data Access Protocol, has been the definitive source of its registration data since ICANN's WHOIS sunset on 28 January 2025. Legacy port-43 WHOIS tools should not be relied on.

Public output is redacted under ICANN's Registration Data Policy: registrant contact details are masked, while domain status, dates, name servers and sponsoring registrar remain visible. Privacy and proxy services are permitted and widely offered by registrars. UDRP and URS apply as ICANN consensus policies.

DNSSEC is supported, with a signed zone and DS record management offered by registrars as standard. Internationalized domain names are not supported: the permitted character set is the letters a to z, the digits 0 to 9, and hyphens. IDN tables are sometimes added after launch, so confirm the current position with the registry.

Who .cloud suits, and who should avoid it

.cloud suits IaaS and PaaS providers, hosting companies, SaaS businesses, managed service providers, DevOps and cloud-consulting firms, backup services and enterprise IT vendors: anyone for whom cloud is the literal product category rather than a decoration. It is also a strong choice for a dedicated cloud product line belonging to a company whose main brand sits on a .com, where a separate property at product.cloud reads as deliberate rather than second-best.

Avoid it if your business has nothing to do with cloud computing, because a mismatch reads as keyword-grabbing to exactly the technical audience the extension appeals to. Avoid it if you need non-Latin characters, or if procurement in your market treats .com as the default for enterprise vendors. And take the length point seriously: .cloud is a seven-character extension, and paired with an already long brand it produces a domain that is tiring to type and awkward in an email address.

Common mistakes with .cloud

The recurring .cloud mistakes divide into one about policy, one about money and one purely practical.

• Assuming there is an eligibility check, and therefore that the extension signals a verified cloud provider. There is none. Anyone can register a .cloud name for anything, so the extension confers category association but no credibility gate. Buyers who assume otherwise over-value the name; buyers who assume they would be rejected for lacking credentials never apply at all.
• Not budgeting the renewal after a deep first-year promotion. .cloud is among the most heavily discounted extensions at retail, and the standard renewal is a different order of magnitude from a promotional first year, with the reversion landing on a whole portfolio at once.
• Underestimating the total string length. Test the full address aloud and in an email signature first; this, rather than any pricing surprise, is the most common regret specific to .cloud.

When the registry is also an infrastructure company

The .cloud contention set was one of the strongest fields of the 2012 round on paper: Amazon, Google, Symantec, Donuts, Top Level Domain Holdings, CloudNames and Aruba. It resolved at a private auction in November 2014, and Aruba won. Three of the largest technology companies in the world lost the most on-brand string for their own core business to a comparatively small Italian hosting provider. No price was disclosed and none should be reported; any figure circulating is unverified. Because this was a private auction rather than an ICANN auction of last resort, the proceeds went to the losing applicants rather than to ICANN, so Amazon and Google were paid out of the string they lost.

What makes .cloud genuinely unusual is not how it was won but who owns it. Nearly every significant new gTLD is run by a portfolio registry whose business is selling names, or by a brand protecting its trademark. ARUBA PEC is neither: it is the registry arm of a hosting and cloud provider with over two million customers, selling exactly the services .cloud describes, to exactly the customers who would register .cloud names.

That alignment produces incentives a portfolio registry does not have. The operator is also a large-scale end user of the namespace it sells, so it has a direct commercial interest in .cloud being deployed on working infrastructure rather than merely registered and parked. A pure-play registry earns the same renewal on a parked name as on a production one; a hosting company that owns the extension does not, because its wider business depends on the category being credible. The pre-launch Pioneer programme is the visible expression of that: seeding the zone with more than thirty infrastructure companies, Canonical and OVH among them, contrasts sharply with the launch-and-discount approach most 2012-round registries took. Aruba has also obtained licensing to sell .cloud in China, a hard approval for a Western new gTLD to secure, though its date and current status are unverified.

The same structure carries risks worth weighing honestly. A registry that is a subsidiary of a hosting company has a strategy subordinate to that hosting business, and registrants depend on the commitment of a parent whose primary revenue lies elsewhere. There is also commercial tension in an operator that competes with some of the hosting companies selling names in its own extension. Neither has produced a visible problem since delegation, but they are the trade-off you accept for a registry that actually uses its own namespace.