Global internet infrastructure visualization
Global Internet Infrastructure Since the 1970s

Without coordination,
the Internet breaks.

IANA ensures that every domain name resolves correctly, every IP address routes to the right place, and every protocol speaks a common language — keeping the global Internet stable for 8 billion users.

1,500+
TLDs coordinated
5 RIRs
Regional registries served
2,000+
Protocol registries maintained
50+ yrs
Of trusted coordination

What happens when internet coordination fails?

Without a trusted, neutral authority managing the Internet's core identifiers, the consequences are immediate and global.

DNS routing collisions

Without a single root, duplicate TLDs would fragment the web — users on different networks would reach different sites at the same address.

IP address exhaustion chaos

Uncoordinated IP allocation would create overlapping address blocks — breaking routing tables and siloing networks from each other globally.

Protocol incompatibility

Without canonical protocol registries, software implementations would conflict — breaking email, web, and every other internet service at the interoperability layer.

Core Services

The four pillars that keep the Internet from falling apart

Every connected device on Earth depends on at least one of these IANA-managed functions — every second of every day.

Domain Names
Domain Names

DNS Root Zone Management

IANA manages the DNS Root Zone — the authoritative top of the naming hierarchy. Without this, entering a URL would fail to resolve. We coordinate all ccTLDs, gTLDs, .int and .arpa zones, so your domain queries never go unanswered.

  • Root Zone Database — publicly accessible, real-time
  • TLD delegation and modification processing
  • .INT domain registration for treaty organizations
Number Resources
Number Resources

IP & AS Number Coordination

Every device that connects to the Internet needs a unique IP address. IANA coordinates the global pools of IPv4, IPv6, and Autonomous System numbers — allocating to 5 Regional Internet Registries so address space never collides.

  • Global IPv4 and IPv6 address space allocation
  • Autonomous System (AS) number coordination
  • Special-purpose registry management
Protocol Assignments
Protocol Assignments

Protocol Name & Number Registries

From port numbers to media types, IANA maintains the central registries that allow internet protocols to interoperate. Without canonical assignments, every HTTP request, email, and API call would risk misinterpretation.

  • 2,000+ protocol parameter registries
  • Port numbers, media types, character sets
  • IETF RFC-based expert review process
DNSSEC
DNSSEC / Security

Root Key Signing (DNSSEC KSK)

IANA manages the Root Zone Key Signing Key — the cryptographic anchor for DNSSEC. Through transparent, multi-party Key Signing Ceremonies, we ensure attackers cannot forge DNS responses and redirect users to malicious sites.

  • Publicly audited KSK signing ceremonies
  • Trust anchor for the entire DNSSEC hierarchy
  • Hardware security module (HSM) protected keys
About IANA

We understand the complexity of global internet governance.

Managing global internet identifiers means serving millions of stakeholders with conflicting interests — all demanding stability, fairness, and zero downtime. We've navigated that complexity since the early 1970s.

IANA functions are performed by Public Technical Identifiers (PTI), a purpose-built subsidiary of ICANN. This structure ensures operational independence, accountability, and a clear policy framework — so the coordination function remains trusted, neutral, and technically excellent regardless of geopolitics.

50+
Years of operations
Global
Stakeholder community
Open
Policy development

Understanding the IANA structure

ICANN
ICANN Policy & Accountability

Sets policy for IANA functions, provides accountability structure, and convenes the multistakeholder community.

PTI
PTI (Public Technical Identifiers) Legal Entity

The ICANN subsidiary that legally performs IANA functions. Operationally independent with direct service contracts.

IANA
IANA Functions Operational

The technical operations: DNS Root Zone, IP coordination, protocol registries, and DNSSEC key management.

How to Work with IANA

Three steps to get what you need from IANA

Whether you're applying for a protocol assignment, updating delegation details, or accessing the Root Zone Database — the process is transparent and documented.

01

Identify your need

Determine which IANA function applies to your situation — domain name, IP/AS assignment, protocol registry, or DNSSEC. Each has a dedicated portal and documented requirements.

DNS Delegation Protocol Request IP Allocation
02

Submit your request

Use the appropriate IANA online form or contact us directly. Requests are reviewed by our technical staff for completeness, eligibility, and policy compliance — with clear acknowledgement timelines.

Online Portal Direct Email
03

Review & confirmation

IANA processes your request, communicates any questions, and issues a formal decision. Approved changes are reflected in the Root Zone Database or relevant registry, often within days.

Transparent tracking Public record
Resources & Access

Everything publicly accessible — because openness is non-negotiable

All IANA databases and registries are freely accessible. No login required to look up data that underpins the entire Internet.

Why the Internet Trusts IANA

Trusted by every registry, operator, and developer — globally

"IANA's protocol assignment process is transparent and efficient. Our RFC review was acknowledged within 48 hours and the registry update was completed well ahead of our deployment schedule."
MR
Marcus R.
Protocol Engineer, IETF Working Group
"We updated our ccTLD delegation details through IANA's online portal. The process was clearly documented, the request tracker gave real-time status, and changes were live in the root zone within the week."
ST
Sofía T.
Technical Director, National ccTLD Registry
"As a network operator in Southeast Asia, I had concerns about geographic bias. IANA's public reports and independent accountability mechanisms gave me confidence that address space is allocated fairly, regardless of region."
AK
Arjun K.
Network Operations, Regional ISP
EFQM Committed to Excellence
EFQM Committed to Excellence
ICANN
Accountability Framework
IETF
Protocol Standards Partner
5 RIRs
Global Registry Partners
Frequently Asked Questions

Questions about IANA's role, services, and processes

Real answers to real questions from registries, protocol developers, network operators, and policy participants.

What is the difference between IANA, PTI, and ICANN?
IANA is the set of operational functions (DNS Root Zone, IP coordination, protocol registries). PTI (Public Technical Identifiers) is the ICANN subsidiary that legally performs those functions. ICANN sets the policies that govern how IANA functions are carried out and provides the accountability framework. Think of IANA as the work, PTI as the entity that does the work, and ICANN as the structure that ensures the work is done correctly and accountably.
Why should I trust IANA as the authority for internet coordination?
IANA's authority derives from decades of demonstrated technical excellence and community trust, not from any government or commercial interest. All decisions follow publicly documented policies developed through open multistakeholder processes. Annual performance reports, customer satisfaction surveys, and independent accountability reviews are published openly. The ICANN accountability framework includes formal escalation paths, including an independent review process, if any stakeholder believes IANA has acted improperly.
How do I apply for a protocol assignment?
Protocol assignments follow IETF procedures defined in each registry's governing RFC. Typically: (1) Identify the correct registry at iana.org/protocols, (2) Review the registration requirements in the referenced RFC, (3) Submit your request via the online form or by emailing iana@iana.org with your specification, (4) An IANA expert reviewer may contact you for clarification, (5) Once approved, the registry is updated — typically within days for expert review requests.
Is IANA accessible to organizations outside the United States?
Absolutely. IANA serves the entire global Internet community regardless of geography. All online services, databases, and request portals are available worldwide. IANA staff communicate in English as the primary working language, but the organization works with regional partners and within the global multistakeholder community to ensure geographic representation. Physical address is in Los Angeles, California, but operations and service are entirely global.
What is DNSSEC and why should my organization care?
DNSSEC (DNS Security Extensions) adds cryptographic signatures to DNS responses. Without it, attackers can forge DNS data through cache poisoning attacks, redirecting users from your legitimate site to a malicious one — without any visible warning. IANA manages the Root Zone Key Signing Key (KSK), the cryptographic trust anchor at the top of the entire DNSSEC hierarchy. If your TLD and domain support DNSSEC, your users benefit from verified, unforgeable name resolution.
How does IANA handle disputes between stakeholders?
IANA follows published policies for all decisions. If you disagree with a decision, formal escalation paths exist: (1) Contact IANA directly to request reconsideration with supporting evidence, (2) File a complaint through the ICANN accountability mechanisms, (3) Request an Independent Review Process (IRP) through ICANN's bylaws for significant disputes. For ccTLD delegation disputes involving competing claims from governments or communities, IANA follows RFC 1591 and related guidelines developed through community consensus.
How do I access or update the Root Zone Database?
The Root Zone Database is publicly accessible at iana.org/domains/root/db — no login required. To update your delegation details (nameservers, contacts, DNSSEC records), TLD operators submit a change request through the IANA online portal or by contacting iana@iana.org. Requests are reviewed for technical correctness and policy compliance. IANA processes most straightforward delegation changes within a few business days.
How can I participate in IANA policy development?
IANA policy is developed through the ICANN multistakeholder model, which is genuinely open. You can participate by: joining relevant ICANN Supporting Organizations or Advisory Committees, attending ICANN public meetings (held three times per year on different continents), submitting comments during public consultation periods posted on icann.org, and engaging with the IETF for protocol-related policies. There is no membership fee to participate in policy development.
Contact IANA

Don't let an unanswered question stall your deployment.

Whether you're applying for a protocol assignment, updating delegation details, or trying to understand which IANA function applies to your work — our team responds to every inquiry.

Address
12025 Waterfront Drive, Suite 300
Los Angeles CA 90094, USA

Send us a message

We respond to all inquiries within 2 business days.