WCAAN
Authorizes root state
We decide which delegations enter the root, the conditions attached to them, and whether a requested change is legitimate.
Independent naming authority
The authority behind an independent root.
WCAAN is the authority behind the root zone's delegations. We handle the bureaucracy, governance, decisions, and public record that give those delegations legitimacy.
Tan's Network is our contractual technical partner. At our discretion, it builds, signs, and serves the approved zone. Naturally, this does not give it any de jure authority over the root.
What this website is for
Resolvers and operatorsUse and verify the root
Read how the zone is assembled, what it delegates, and which publication facts are presently verifiable.
NICs and affected partiesPrepare a request or noticeIdentify the filing class, required authority, proposed state, fallback state, and evidence.
Partners and the publicInspect the recordRead current delegations, issued instruments, decisions, consultations, notices, corrections, and incidents.
One root, three different responsibilities
ICANN governs the conventional root while Verisign performs much of the work required to publish it. WCAAN and Tan's Network have a comparable division of labour for this root. The comparison explains the boundary. It does not claim the same legal status, public mandate, or scale.
WCAAN is a chartered initiative of Willing International. Our partnerships require a public account of the authority we exercise and the state our partners are expected to implement. Internal governance remains private and membership-based. Our partners are entitled to the information required to understand our intentions and to maintain an amicable, equal relationship grounded in human care.
Filing is not yet open
The filing packet may be downloaded and prepared in advance. At this point, however, sending it anywhere does not create a case. WCAAN has not established an authenticated submission mechanism.
The packet is deliberately exacting because a root-zone change can affect every resolver using this root. This does not justify requesting information merely because an authority may enjoy collecting it. Every required field must correspond to an authorization, validation, publication, or accountability need.