No KYC: one verified email, no ID · Paid in crypto: BTC, USDT, USDC, ETH, SOL, LTC · .com $11.99/year
Language: English
Search a domain

Data · 225 extensions · counts of 29 October 2026 · CC BY 4.0

What are the registration rules of each domain extension?

Who may register, whether WHOIS privacy is allowed, and the shortest and longest terms, for 225 extensions: 10 legacy gTLDs, 121 new gTLDs and 94 country codes. Built from IANA, registry and registrar sources; free to reuse under CC BY 4.0.

Last updated: · 13 min read

Quick answer

Which rules apply to each domain extension in 2026?

The DotAlmanac domain extension rules 2026 table covers 225 extensions. As of 29 October 2026, 176 are open to anyone, 23 forbid WHOIS privacy, and only .ai imposes a 2-year minimum. Among the 94 country codes, 52 accept registrants from anywhere; the other 42 set a local, ID or trademark condition, or lack a reliable source.

The table in five numbers

176 of 225

extensions open to anyone, with no residency, presence or eligibility rule (78%)

23

extensions where WHOIS privacy is forbidden or not available

52 of 94

country-code extensions open to registrants from any country

1

extension with a 2-year minimum term: .ai

219 of 225

extensions signed with DNSSEC in the root zone

About this dataset

PublisherDotAlmanac, operated by DomaineGoat LLC
Entries225 extensions: 10 legacy gTLDs, 121 new gTLDs, 94 country-code TLDs (ccTLDs)
FieldsRegistry, type, who can register, WHOIS privacy, minimum and maximum years, DNSSEC, IDN support, sources
Source quality155 entries checked against registry or registrar sources; 70 entries from secondary sources, marked "Secondary" in the tables
DatesSources read in October 2026 (DNSSEC records on 8 October 2026); counts computed on 29 October 2026
Temporal coverageOctober 2026
LicenceCC BY 4.0 (Creative Commons Attribution 4.0 International)

Who can register? The 225 extensions by rule

RuleExtensionsShareExamples
Open to anyone17678%.com, .net, .org, .io, .ai, .co, .de, .uk, most new gTLDs
Local presence (address, company number or local contact)146%.au, .br, .jp, .no, .sg, .berlin
Residency or citizenship63%.eu, .fr, .ca, .it, .hu, .hr
Identity check by the registry42%.cn, .ru, .in, .dk
Nexus (a documented link to the place)21%.us, .nyc
Professional or community eligibility52%.music, .law, .bank, .insurance, .ngo
Trademark10.4%.ua
Not documented178%.tr, .pt, .gr, .il, .vn, .th

Last checked on ; older figures carry their own date

Shares are of the 225 extensions in the table and are rounded. "Not documented" means we found no reliable source; we never guess a rule.

What do the 2026 rules show?

Most extensions are open to anyone, but country codes carry most of the conditions. DotAlmanac is a domain extension guide and registrar: compare every extension, then register it with no KYC and pay in crypto. We publish the rules we check before we list an extension.

  1. Generic extensions are almost all open. Of the 49 extensions with a known or possible condition, 7 are new gTLDs: .music, .law, .bank, .insurance, .ngo, .nyc and .berlin.
  2. Country codes are split. According to DotAlmanac's table of 225 extensions, 52 of the 94 ccTLDs accept anyone, 25 set a condition and 17 are not documented.
  3. Registries hide data themselves in Europe. All 31 extensions where the registry hides personal data on its own are country codes, such as .de, .uk, .nl, .ch and .se.
  4. Privacy bans and access rules often go together. 13 of the 23 extensions that forbid WHOIS privacy also restrict who can register, such as .us, .cn and .au.
  5. Terms are short for a few ccTLDs. Nine extensions allow only 1 year at a time, and .co, .es, .au and .fi stop at 5 years.

Which country codes restrict who can register?

The 25 country-code extensions with a known condition. The 52 open ones are listed on can you register a country domain without living there. The 17 undocumented ones are .tr, .pt, .tw, .gr, .sk, .il, .id, .vn, .th, .lu, .ke, .pk, .kz, .eg, .bz, .sc and .ms.

ccTLDCountryRuleConditionSource
.euEuropean UnionResidencyEU/EEA citizens wherever they live, or residents and organisations established in the EU/EEAChecked
.frFranceResidencyIndividuals resident in the EU/EEA or organisations established there; AFNIC eligibility and reachability checksChecked
.caCanadaResidencyCanadian Presence Requirements: citizens, permanent residents, Canadian entities, trademark holdersChecked
.itItalyResidencyCitizens, residents or organisations of the EEA, UK, Switzerland, San Marino or Vatican; tax or ID numberChecked
.huHungaryResidencyPersons and companies in Hungary or the EUSecondary
.hrCroatiaResidencyCroatian citizens, residents and organisationsSecondary
.cnChinaID checkReal-name check by CNNIC; foreigners show a passport, firms a company certificateChecked
.ruRussiaID checkIdentity check through the Gosuslugi portal since 1 September 2026; Russian registrars onlyChecked
.inIndiaID checke-KYC within 7 days of registration or renewal; non-residents need a business link with IndiaChecked
.dkDenmarkID checkOpen to foreigners, but photo ID, proof of address or a selfie can be required on a risk basisChecked
.usUnited StatesNexusUS citizens or residents, US organisations, or foreign entities with a bona fide US presenceChecked
.uaUkraineTrademarkDirect .ua needs a matching Ukrainian trademark; .com.ua is openSecondary
.auAustraliaLocal presenceCitizen or resident, an ABN/ACN entity, or an exact-match Australian trademarkChecked
.brBrazilLocal presenceBrazilian CPF or CNPJ number; foreign companies need a local attorneyChecked
.jpJapanLocal presenceJapanese postal address; registrar local-presence services existSecondary
.krSouth KoreaLocal presenceKorean address; foreigners use a registrar trustee serviceSecondary
.sgSingaporeLocal presenceSingapore-based admin contact verified through SingPassChecked
.noNorwayLocal presenceNorwegian organisation number or national ID plus addressChecked
.ieIrelandLocal presenceA documented real and substantive connection with IrelandChecked
.arArgentinaLocal presenceA contact with an Argentine address; the registrant may be foreignSecondary
.myMalaysiaLocal presenceMalaysian presenceSecondary
.bgBulgariaLocal presenceRegistrant in Bulgaria or a local representativeSecondary
.aeUnited Arab EmiratesLocal presenceLocal presence or documents for co.ae, net.ae and similarSecondary
.saSaudi ArabiaLocal presenceSaudi presence, a local representative or a Saudi trademarkSecondary
.maMoroccoLocal presenceBased in Morocco or a legal representativeSecondary

Last checked on ; older figures carry their own date

"Checked" = the entry was checked against registry or registrar sources. "Secondary" = it rests on a secondary source such as Wikipedia. DotAlmanac sells none of these 25 extensions.

Which extensions forbid WHOIS privacy?

WHOIS privacy hides the owner's contact data behind a service. In DotAlmanac's table of 225 extensions, 135 allow it, 31 have data hidden by the registry itself, 23 forbid it or offer no way to use it, and 36 are unknown. These are the 23.

ExtensionTypeWho can registerPrivacy noteSource
.cnccTLD (China)ID checkPrivacy services not offered by major registrarsChecked
.brccTLD (Brazil)Local presencePrivacy protection not supportedChecked
.auccTLD (Australia)Local presenceRegistrant name stays public; no privacy serviceChecked
.inccTLD (India)ID checkRegistry does not support proxy privacyChecked
.usccTLD (United States)NexususTLD policy bans privacy and proxy registrationsChecked
.esccTLD (Spain)Open to anyone, ID or company number requiredPrivacy services not supportedChecked
.jpccTLD (Japan)Local presenceNot offered by international registrarsSecondary
.dkccTLD (Denmark)ID checkPublic under Danish law; name and address protection only for Danish residentsChecked
.zaccTLD (South Africa)Open to anyone under .co.za.co.za privacy not availableSecondary
.sgccTLD (Singapore)Local presencePrivacy protection not supportedChecked
.hkccTLD (Hong Kong)Open to anyone at second levelPrivacy service not availableSecondary
.twccTLD (Taiwan)Not documentedPrivacy service not availableSecondary
.arccTLD (Argentina)Local presence.com.ar privacy not supportedSecondary
.clccTLD (Chile)Open to anyonePrivacy protection not supportedChecked
.phccTLD (Philippines)Open to anyonePrivacy service not availableSecondary
.siccTLD (Slovenia)Open to anyonePrivacy service not availableSecondary
.liccTLD (Liechtenstein)Open to anyonePrivacy service not availableSecondary
.ngccTLD (Nigeria)Open to anyone under .com.ngPrivacy service not availableSecondary
.imccTLD (Isle of Man)Open to anyonePrivacy not supportedChecked
.musicNew gTLDMusic-community members onlyPrivacy service not availableChecked
.nycNew gTLDNew York City nexusPrivacy and proxy registrations not allowedChecked
.berlinNew gTLDBerlin address requiredPrivacy not supportedChecked
.ngoNew gTLDProof of non-profit statusPrivacy service not availableChecked

Last checked on ; older figures carry their own date

At DotAlmanac, WHOIS privacy costs nothing on every extension whose registry permits it, and each registry decides what remains visible. Verisign's .com and .net are thin registries: they receive no registrant contact data at all.

What are the minimum and maximum registration terms?

Most extensions can be registered for 1 to 10 years. These 15 depart from that rule.

ExtensionMinimumMaximumWhat it means
.ai2 years10 yearsEvery registration and every renewal covers at least 2 years
.co1 year5 yearsYou can prepay up to 5 years, not 10
.es1 year5 yearsYou can prepay up to 5 years
.au1 year5 yearsYou can prepay up to 5 years
.fi1 year5 yearsYou can prepay up to 5 years
.im1 year2 yearsYou can prepay up to 2 years
.de, .nl, .ch, .be, .gg, .jp, .it, .ac, .ru1 year1 yearRenewed one year at a time; no multi-year registration
The other 210 extensions1 year10 yearsStandard range; 82 of these 210 use the default value and are not confirmed

Last checked on ; older figures carry their own date

Terms come from Amazon Route 53's page for each extension, which exists for 143 of the 225. Route 53 describes one registrar's rules, which can be stricter than the registry's. Planning a long registration? Read should you register a domain for 10 years.

What else does the table record?

Each entry also records security and script support, which matter for some projects.

  • DNSSEC: 219 of the 225 extensions have a DS record in the root zone, read on 8 October 2026. The six without one are .so, .to, .im, .ae, .pk and .eg.
  • IDN: 164 of the 225 accept domain names in non-ASCII characters, such as accented letters or Cyrillic.
  • HTTPS required: .app, .dev and .page are on the browser HSTS preload list, so a site on them works only over HTTPS.
  • Risk notes: .io works normally in 2026. The open question is who will hold the Chagos Islands; the UK–Mauritius treaty was shelved in 2026.

The same data feeds our extension guides and the restrictions column of our price list.

How was the table built?

We combined automatic reads of public registries with targeted research, and wrote "unknown" wherever no source was solid.

  1. Registry name: from the IANA root zone database, one page per extension.
  2. DNSSEC: a lookup of the DS record of each extension in the root, over DNS-over-HTTPS, on 8 October 2026.
  3. IDN: the IDN tables filed at IANA, or "IDN supported" on the Route 53 page, with manual fixes for a few ccTLDs.
  4. Terms: Amazon Route 53's page for each extension, available for 143 of them; the rest use 1 to 10 years by default.
  5. Who can register and WHOIS privacy: registry policies and registrar help pages for about 40 extensions, registrar lists of extensions without privacy, and a Wikipedia cross-check.
  6. Counts: computed from the finished table on 29 October 2026. Every entry keeps its source URLs.

What are the limits of this table?

The table is reliable for the popular extensions and weaker for small ccTLDs. Know its limits before you rely on one row.

  • 70 of the 225 entries rest on secondary sources. They are marked "Secondary" in the tables above. Check them with the registry before you buy.
  • Route 53 describes a registrar, not always the registry. It is stricter than DENIC for .de, for example, where it asks for a German contact up front.
  • Regulated new gTLDs may need a licence. Some finance, legal or health extensions can require one in their registry terms. We did not check those.
  • European rules are tightening. The NIS2 directive led AFNIC, Punktum and other registries to verify registrant data more strictly in 2025 and 2026.
  • Two points stay open: the minimum term of .to (2 years in one source) and the eligibility of .so (older texts mention a link with Somalia).

Found an error? Write to us through the contact page with a source, and we correct the row.

Domain extension rules: FAQ

Which domain extensions do not allow WHOIS privacy?

23 of the 225 extensions in our table, as of 29 October 2026. They include .us, .es, .cn, .in, .au, .br and .dk among country codes, and .music, .nyc, .berlin and .ngo among new gTLDs. At DotAlmanac, WHOIS privacy is free wherever the registry allows it.

Which country domains can anyone register?

52 of the 94 country codes in the table, including .io, .ai, .co, .me, .tv, .gg, .de, .uk, .nl and .ch. The full list, with what to check for each one, is on can you register a country domain without living there.

Which extension has a minimum registration of 2 years?

.ai is the only one in the 225-extension table. Every .ai registration and renewal covers at least 2 years. At DotAlmanac, .ai costs $84.49/year, billed 2 years at a time.

Can every domain be registered for 10 years?

No. In our table, 211 of the 225 extensions allow 10 years, 82 of them by default value. .co, .es, .au and .fi stop at 5 years, .im at 2, and nine ccTLDs, including .de, .nl and .ch, accept only 1 year at a time.

How reliable is this table?

155 of the 225 entries were checked against registry or registrar sources; 70 rest on secondary sources and are marked as such. Where no source was solid, the table says "unknown" rather than guessing.

Sources (12)
  1. Root Zone Database — IANA (checked 2026-10-08)
  2. IDN tables repository — IANA (checked 2026-10-08)
  3. Domains that support privacy protection — Amazon Route 53 (checked 2026-10-08)
  4. Domains where privacy is not allowed dynadot.com/help/question/domain-privacy-not-allowed — Dynadot (checked 2026-10-08)
  5. Rules for .eu domains — EURid (checked 2026-10-08)
  6. usTLD privacy services policy — about.us (usTLD registry) (checked 2026-10-08)
  7. .ru ready to crash as draconian new rules come in — Domain Incite (checked 2026-10-08)
  8. Domain name news, June 2026 (.in e-KYC) — Hogan Lovells (checked 2026-10-08)
  9. Data and ID verification of registrants — Punktum dk (checked 2026-10-08)
  10. Domain Name Eligibility and Allocation Policy Rules — auDA (July 2024, checked 2026-10-08)
  11. .io safe for now as Trump puts Chagos deal on ice — Domain Incite (checked 2026-10-08)
  12. HSTS preload and Google Registry kb.porkbun.com/article/96-hsts-preload-and-google-registry — Porkbun (checked 2026-10-08)

Pick an extension with known rules

Every extension we sell shows its registry rules next to its price. No ID; pay in crypto.

.com $11.99/year · no KYC · crypto

Search a domain