HomeGuidesCommunity gTLDs and Specification 12
Registry & policy

Community gTLDs & Specification 12

How community commitments appear in registry agreements, where Specification 12 fits, and why the actual commitments must be read TLD by TLD.

On this page
TL;DR

Community status is a contractual dimension, not an IANA root-zone type. Specification 12 records community registration policies and commitments for applicable registry agreements; the actual rules vary by TLD.

Community is a separate dimension

Do not collapse “community” into the IANA TLD type. IANA may classify a TLD as generic while the ICANN registry agreement separately contains community commitments.

What Specification 12 is for

For applicable community-based registry agreements, Specification 12 contains community registration policies and related commitments. Those terms are specific enough that a reference site should link to the actual agreement rather than paraphrasing from the TLD string.

How to model it safely

FieldSourceMeaning
iana_typeIANARoot-zone classification
spec_12_communityICANN agreementCommunity contractual attribute
Registration eligibilityAgreement / registry policyTLD-specific rules; never infer

Avoid universal policy summaries

Community does not mean one universal rule

Eligibility and naming policies can differ. The correct detail page should cite the TLD's own authoritative agreement or policy source.

Primary sources

These are the primary references this guide is designed around. When implementation data disagrees with editorial copy, the primary source wins.