.cc domain names

What .cc is

.cc is the country-code top-level domain (ccTLD — a two-letter extension assigned to a country or territory under the ISO 3166-1 standard) for the Cocos (Keeling) Islands, an Australian external territory in the Indian Ocean with a population in the low hundreds. IANA classifies it as country-code, not generic. It was delegated on 13 October 1997, originally to eNIC.

It is used almost entirely generically. There is no meaningful connection between .cc registrations and the Cocos Islands, and the market treats .cc as a short, unrestricted global alternative to .com. The two letters get backronymed constantly — creative commons, cricket club, cycling club, church, company, carbon copy — and in Asia .cc is read as an abbreviation of .com.

The registry arrangement is the unusual part. The sponsoring organisation on the IANA record is eNIC Cocos (Keeling) Islands Pty. Ltd., trading as Island Internet Services, and eNIC is a Verisign subsidiary. The technical contact is Registry Customer Service, VeriSign Global Registry Services, of Reston, Virginia, and the administrative contact address is a verisign.com mailbox. That record was last updated on 24 March 2026, and no change of operator was identified for 2025 or 2026. In practical terms .cc is a Verisign-operated country code, run on the same registry infrastructure family as .com and .net.

Who can register .cc

.cc is genuinely open. There is no local presence requirement, no nexus to the Cocos Islands, no citizenship condition, no documentation and no eligibility declaration of any kind. Anyone worldwide may register in real time, and there is nothing that could later be audited or found false.

The corollary is worth stating in the same breath, because buyers get this backwards in both directions: the absence of an eligibility gate does not make .cc a generic extension with ICANN's rulebook behind it. It is a country code with no eligibility rules, which is a different thing entirely.

What .cc costs to own

Verisign prices .cc as a premium-positioned country code: at the wholesale level it sits meaningfully above commodity new generic extensions and generally above .com itself. It is not a bargain extension, whatever a first-year offer suggests.

That first-year offer is the trap. .cc is a perennial favourite for aggressive promotional pricing at retail, and the gap between the promotional first year and the standing renewal is among the widest in the market. That gap is registrar-driven rather than registry policy, so it varies — and the only number worth planning around is the renewal.

• Premium and reserved tiers exist. Short labels and dictionary words sit in elevated registry tiers, with the recurring renewal implications that carries.
• Price changes are not telegraphed the way gTLD changes are. A country-code registry is not bound by ICANN's price-change notice requirements — no guaranteed six months of warning, and no mechanism letting you lock a decade of renewals at the old rate before an increase. No specific .cc price change was identified for the January 2026 round, but the protection generic-extension buyers take for granted is absent here.
• Restoration costs substantially more than renewal. A lapsed .cc that has entered redemption carries a restore fee on top of the renewal.

On the aftermarket, two- and three-character .cc names trade actively, particularly in Asia.

Registration terms, renewals, and transfers

.cc registers for a minimum of one year and a maximum of ten, in whole-year increments.

Verisign runs .cc on transfer mechanics familiar to anyone who has moved a .com. An EPP authorization code is required; the transfer is blocked while clientTransferProhibited is set, so the domain must be unlocked first; there is a 60-day lock after initial registration and after any prior transfer; and a successful transfer adds one year to the term. The lifecycle as documented by registrars runs to a 30-day renewal grace period after expiration, a short add and deletion grace window, and a 30-day redemption and restore period during which only the original registrant can recover the name, on payment of a restore fee.

The caveat matters more here than on most extensions. Because .cc is a country code, none of this rests on ICANN's Transfer Policy or its uniform grace-period rules — it is registry and registrar policy. Day to day the behaviour is indistinguishable from a generic extension; edge cases are where the difference surfaces. Disputed transfers, reversals, change-of-registrant locks and unusual redemption timings may be handled differently, and grace periods vary between registrars. Verify day counts with your registrar.

WHOIS, RDAP, and privacy

.cc runs on a thick registry — Verisign holds the full registration record centrally rather than deferring to the registrar — and Verisign has been an early implementer of RDAP, the Registration Data Access Protocol that returns structured JSON registration data. ICANN's 28 January 2025 WHOIS sunset applies to generic extensions and not to country codes, so .cc is not bound by it; port-43 WHOIS at whois.nic.cc has historically remained available alongside RDAP. Check the live endpoints before hard-coding either into tooling.

Privacy and proxy services are available and widely offered, with many registrars bundling them at no cost. Because ICANN's Registration Data Policy redaction rules do not automatically bind a country code, what appears in a public lookup depends more on your registrar's privacy product than on registry policy — choose the registrar accordingly. ICANN's UDRP is likewise not automatically applicable, though .cc has adopted a UDRP-equivalent process; confirm the current policy text at the registry before relying on it.

DNSSEC is supported: the zone is signed and registrars support DS record management. Internationalised domain names are supported across multiple scripts, a differentiator against newer generic extensions that remain ASCII-only. .cc is not on the HSTS preload list, so plain HTTP works and encryption is optional in the same way it is for .com.

Who .cc suits, and who should avoid it

The framing to hold onto is that .cc is the country code of the Cocos (Keeling) Islands, governed as a sovereign delegation rather than under ICANN's generic-extension contracts, and operated commercially by a Verisign subsidiary. The marketing has positioned it as a global .com alternative since the late 1990s — commercially accurate, legally incomplete.

.cc suits anyone wanting a genuinely short, memorable, unrestricted global extension where the .com is gone. It suits the natural CC constituencies — cricket and cycling clubs, community and church organisations, Creative Commons-adjacent projects, and companies whose initials are CC. It suits link shorteners, where two characters are two characters, and open-source projects, where arduino.cc is the canonical example. And it suits businesses with meaningful exposure to Asian markets, where .cc carries real recognition rather than needing explanation.

Avoid .cc if you need the trust profile of a .com for a mainstream Western consumer or financial audience. Avoid it if you are sensitive to legacy spam-filter heuristics, some of which still reflect .cc's history. Avoid it if you want ICANN consensus-policy protections — the uniform Transfer Policy, uniform redemption rules, guaranteed UDRP, mandated price-change notice — as enforceable contract rather than registry practice. And avoid it if your budget assumed commodity renewal pricing.

Common mistakes with .cc

Confusing a co.cc or com.cc address with a real .cc registration. These third levels are sold as pseudo-namespaces by third parties. What you get is a subdomain from a reseller, not a registered domain: you do not own it, cannot transfer it independently, and have no registry-level recourse. The co.cc collapse is the cautionary tale — the operation handed out free and bulk subdomains at enormous scale, became a spam vector, and Google delisted more than 11 million co.cc sites in July 2011.

Registering on a first-year promotion without checking the renewal. .cc is a premium-priced Verisign country code, and the gap between the promotional first year and the standard renewal is one of the widest in the market. Multiply the renewal by your holding period before you buy.

Getting the country-code status backwards, in either direction. There is no Cocos Islands presence requirement, for anyone. But there is also no automatic ICANN consensus-policy protection, so the transfer, redemption and dispute guarantees that are contractual entitlements on .com are registry practice here. Buyers routinely assume one of these wrongly, and sometimes both.

A few hundred islanders, and a registry built for .com

The Cocos (Keeling) Islands are an Australian external territory with a population in the low hundreds. Their country code is one of the most widely used generic-purpose ccTLDs in the world, and Verisign's subsidiary marketed it explicitly as the next .com.

The delegation structure is what makes .cc genuinely unusual rather than merely small. The sponsoring organisation of record is a locally named company, eNIC Cocos (Keeling) Islands Pty. Ltd., trading as Island Internet Services. Every operational contact on the same IANA record points to VeriSign Global Registry Services in Reston, Virginia, and eNIC is a Verisign subsidiary. A territory of a few hundred people has its namespace run by the company that operates .com and .net, on the same registry infrastructure family.

For reliability, this is close to the best arrangement available to a small territory. Registrars encounter EPP behaviour, transfer mechanics and lifecycle handling that resemble .com because they substantially are .com's. The zone is DNSSEC-signed, and Verisign was among the earliest registry operators to implement RDAP. For a country code, the operational floor under .cc is unusually high.

For policy, the arrangement cuts the other way, and this is the most under-appreciated structural fact about the extension. ICANN's contractual apparatus attaches to generic-extension registry agreements: the Registration Data Policy governing redaction, the uniform Transfer Policy, the RDAP mandate, uniform grace and redemption periods, guaranteed UDRP applicability, notice requirements around price increases. A country code has no such agreement. Verisign runs .cc on gTLD-like commercial terms and most registrars treat it the same way, so nothing feels different from the outside — but those guarantees are registry practice rather than obligations an accreditation body can enforce on your behalf. When something goes wrong at the edges, that is the whole difference.

One historical footnote deserves care rather than repetition. In 2016 .cc was recorded among a group of four extensions accounting for roughly 75% of all malicious domain registrations, with .cc responsible for about a quarter of that group. That is a decade-old datapoint; .cc's profile has improved considerably under Verisign and it should not be read as a current characterisation. What persists is the reputational tail — some spam-filter heuristics were tuned in that era and never retuned.