The Domain for Inteligencia Artificial

Search .IA + Compare Popular TLDs

Type an idea (e.g., robotica). We’ll simulate .IA availability and live‑check basic DNS signals for .com, .net, .org, .io, .co, .ai, .xyz. Demo only — not a registrar result.

.AI momentum → A case for .IA

A sample of teams using .ai today (tap to visit). Imagine the multilingual mirror under .ia.

Why .IA?

“IA” is the natural acronym for Artificial Intelligence across Spanish, Portuguese, French, and Italian — a community of ≈1.2B speakers. .IA provides a clear, neutral home for people and agents in these languages.

• Multilingual by default: Serving Romance‑language speakers worldwide
• Bridges Web2 DNS + Web3 identity: Wallets, agent credentials, decentralized resolution
• Community governance: International non‑profit model with transparent decision‑making
• Public interest focus: Ethical, open, and prioritizing accessibility over profit

Architecture Goals

Pair Web2 DNS with on‑chain identifiers for autonomous agents, creating verifiable digital identity across traditional and decentralized systems.

Community Registry Model

Unlike generic or corporate TLDs, .IA is being developed as a community‑based registry serving a clearly delineated global community.

Our Community

• ≈1.2 billion Romance‑language speakers (Spanish, Portuguese, French, Italian)
• AI researchers, developers, and autonomous agents worldwide
• Multilingual open‑source teams building AI tools and infrastructure
• Governments and academic institutions advancing AI policy and research

Community Governance (In Development)

• ✓ Established: IA XYZ Benefit LLC (October 30, 2025)
• ✓ ICANN Status: Applicant Support Program (Org ID: IAXL2597)
• ⏳ Seeking: Board members from each Romance‑language region
• ⏳ Charter: Community voting on registry policies and major decisions

Public Interest Commitments (PIC)

• Equitable access for researchers, students, and startups
• Revenue sharing with community development (90% reinvestment target)
• Open governance with transparent, accountable decision‑making
• Affordable pricing versus traditional corporate registries
• Standards development for AI agent identity and Web3 integration

Roadmap: From Vision to Reality

Ambitious but clear milestones to de‑risk execution through a phased, community‑driven approach.

Q4 2025 ✓ Community Foundation

• ✓ Form IA XYZ Benefit LLC (Wyoming) — Oct 30, 2025
• ✓ ASP organization record (IAXL2597) — Oct 30, 2025
• ⏳ Community Charter draft (Nov 2025)
• ⏳ Organizational endorsements (Nov–Dec 2025)
• ⏳ Public awareness campaign

2026 🚀 Government & ICANN Phase

• Petition ICANN as Community TLD applicant (Feb–Mar 2026)
• Secure government support letters from Spain, France, Brazil, Portugal, Italy
• Form international governance board with Romance‑language representation
• Establish technical standards for AI agent identity
• Apply in gTLD Round 2 (April–August 2026) (expected)
• ICANN evaluation (estimated) 2026–2027

2027 🔗 Web3 Pilot Phase

• Conditional approval (if granted) — targeting 2027
• Pilot: NFT‑style .IA registration on L2 (Arbitrum/Base)
• Agent identity standards work
• Community governance voting system live

2028 🌍 Global Launch

• Unified Web2 + Web3 registration
• Full ICANN‑approved .IA launch (if approved)
• Access for ≈1.2B Romance‑language speakers
• International governance consortium operational

Technical Architecture

Standards & Technical Implementation

Core Technologies

• Web2 DNS: Traditional ICANN‑compliant domain registration
• Web3 Integration: On‑chain resolution via ENS, Unstoppable Domains compatibility
• Agent Identity: Verifiable credentials for autonomous AI agents
• Security: DNSSEC, blockchain verification, multi‑signature governance

Smart Contract Preview (Demo)

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.21;

contract IADomainRegistry {
  mapping(string => address) public domains;
  event DomainMinted(string name, address owner);

  function mint(string memory name) public payable {
    require(domains[name] == address(0), "Already taken");
    require(msg.value >= 0.01 ether, "Insufficient payment");
    domains[name] = msg.sender;
    emit DomainMinted(name, msg.sender);
  }
}

Non‑binding demo. Real implementation will add pricing, expirations, royalty routing, and on‑chain resolution. Full specs will be published during the Web3 pilot phase (2027).

Get Involved — Evidence Our Community

Community evidence strengthens our case as a Community TLD applicant. Your participation helps demonstrate public interest to ICANN.

1) Individual Community Members

2) Organizations & Institutions

We’re seeking endorsements to include in our application materials:

Community Leaders Support .IA

Want to add your voice? Share your support

Frequently Asked Questions