CINXE.COM
.INT Policy & Procedures
<!doctype html> <html> <head> <title>.INT Policy & Procedures</title> <meta charset="utf-8" /> <meta http-equiv="Content-type" content="text/html; charset=utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> <link rel="stylesheet" href="/_css/2022/iana_website.css"/> <link rel="shortcut icon" type="image/ico" href="/_img/bookmark_icon.ico"/> <script type="text/javascript" src="/_js/jquery.js"></script> <script type="text/javascript" src="/_js/iana.js"></script> </head> <body> <header> <div id="header"> <div id="logo"> <a href="/"><img src="/_img/2022/iana-logo-header.svg" alt="Homepage"/></a> </div> <div class="navigation"> <ul> <li><a href="/domains">Domains</a></li> <li><a href="/protocols">Protocols</a></li> <li><a href="/numbers">Numbers</a></li> <!-- <li><a href="/news">News</a></li>--> <li><a href="/about">About</a></li> </ul> </div> </div> </header> <div id="body"> <article class="hemmed sidenav"> <main> <h1>.INT Policy & Procedures</h1> <h2>Eligibility for a .INT domain</h2> <p>To register in the .int domain, the applicant must be an intergovernmental organization that meets the requirements found in RFC 1591. In brief, the .int domain is used for registering organizations established by international treaties between or among national governments. Only one registration is allowed for each organization. There is no fee for registering an .int domain name.</p> <p>Please consider the following three elements before applying for an .int domain name. These qualifications must be met before an .int domain name can be granted.</p> <ol> <li>An <strong>international treaty</strong> between or among national governments must be provided. We should be able to look up the international treaty in the UN online database of treaties, or you should provide us a true certified copy of the treaty. Please be sure what you provide is a treaty, not the constitution or bylaws of the organization. We recognize as organizations qualified for domain names under the .int top-level domain the <a href="https://www.un.org/about-us/specialized-agencies">specialized agencies</a> of the UN, and the organizations having <a href="https://www.un.org/about-us/intergovernmental-and-other-organizations">observer status</a> at the UN General Assembly.</li><br/> <li>The treaty submitted must establish the organization applying for the .int domain name. The organization must be <strong>established by the treaty itself</strong>, not by a council decision or similar.</li><br/> <li>The organization that is established must be widely considered to have <strong>independent international legal personality</strong> and must be the subject of and governed by international law. The declaration or the treaty must have created the organization. If the organization created is a secretariat, it must have a legal personality. For example, it must be able to enter into contracts and be party to legal proceedings.</li> </ol> <p>Please also review the following information to help determine if you should submit an application for an .int domain name:</p> <ul> <li><strong>If the organization is a program/function of a treaty organization, we suggest you contact that organization. </strong><ul>The program/function is eligible, with consent of the treaty organization, to receive a third-level domain within the second level .int domain operated by that organization (e.g., example.un.int). For example, if your organization is a program of the UN, you should contact the administrator for un.int for a third level domain. If you wish to pursue this, you should contact the appropriate officials of the organization, who can set up the third-level domain without involvement of the IANA. See the IANA Whois service for information about the administrative and technical contacts of the various .int domains.</ul></li> <li><strong>The IANA no longer grants .int domain names for international databases as per RFC 1591.</strong><ul> In the past, the .int top-level domain was used both for international treaty-based organizations and for Internet-infrastructure purposes. Because of the need for secure and stable management of the infrastructure aspects of the .int domain, from the time of its inception in 1988 the .int domain was administered by personnel at the University of Southern California/Information Sciences Institute. This activity was assumed by ICANN as part of the transition of the IANA functions from USC/ISI to ICANN at the time of ICANN's establishment. In 2000 the Internet Architecture Board recommended that any new infrastructure subdomains be established within .arpa and that consideration be given to migrating existing infrastructure subdomains in .int to .arpa. See also <a href="/go/rfc3172">RFC 3172</a>, Appendix A (28 April 2000 letter from Karen Rose to Louis Touton designating administration of .arpa as an additional IANA function). Accordingly, subdomains are now established in .int only for international treaty-based organizations.</ul> </ul> </main> <nav id="sidenav"> <div class="navigation_box"> <h2>Domain Names</h2> <ul> <li id="nav_dom_top"><a href="/domains">Overview</a></li> <li id="nav_dom_root"><a href="/domains/root">Root Zone Management</a></li> <ul id="nav_dom_root_sub"> <li id="nav_dom_root_top"><a href="/domains/root">Overview</a></li> <li id="nav_dom_root_db"><a href="/domains/root/db">Root Database</a></li> <li id="nav_dom_root_files"><a href="/domains/root/files">Hint and Zone Files</a></li> <li id="nav_dom_root_manage"><a href="/domains/root/manage">Change Requests</a></li> <li id="nav_dom_root_procedures"><a href="/domains/root/help">Instructions & Guides</a></li> <li id="nav_dom_root_servers"><a href="/domains/root/servers">Root Servers</a></li> </ul> <li id="nav_dom_int"><a href="/domains/int">.INT Registry</a></li> <ul id="nav_dom_int_sub"> <li id="nav_dom_int_top"><a href="/domains/int">Overview</a></li> <li id="nav_dom_int_manage"><a href="/domains/int/manage">Register/modify an .INT domain</a></li> <li id="nav_dom_int_policy"><a href="/domains/int/policy">Eligibility</a></li> </ul> <li id="nav_dom_arpa"><a href="/domains/arpa">.ARPA Registry</a></li> <li id="nav_dom_idn"><a href="/domains/idn-tables">IDN Practices Repository</a></li> <ul id="nav_dom_idn_sub"> <li id="nav_dom_idn_top"><a href="/domains/idn-tables">Overview</a></li> <!-- <li id="nav_dom_idn_tables"><a href="/domains/idn-tables/db">Tables</a></li> --> <li id="nav_dom_idn_submit"><a href="/procedures/idn-repository.html">Submit a table</a></li> </ul> <li id="nav_dom_dnssec"><a href="/dnssec">Root Key Signing Key (DNSSEC)</a></li> <ul id="nav_dom_dnssec_sub"> <li id="nav_dom_dnssec_top"><a href="/dnssec">Overview</a></li> <li id="nav_dom_dnssec_ksk"><a href="/dnssec/files">Trust Anchors and Rollovers</a></li> <li id="nav_dom_dnssec_ceremonies"><a href="/dnssec/ceremonies">Key Signing Ceremonies</a></li> <li id="nav_dom_dnssec_dps"><a href="/dnssec/procedures">Policies & Procedures</a></li> <li id="nav_dom_dnssec_tcrs"><a href="/dnssec/tcrs">Community Representatives</a></li> <li id="nav_dom_dnssec_archive"><a href="/dnssec/archive">Project Archive</a></li> </ul> <li id="nav_dom_special"><a href="/domains/reserved">Reserved Domains</a></li> </ul> </div> </nav> </article> </div> <footer> <div id="footer"> <table class="navigation"> <tr> <td class="section"><a href="/domains">Domain Names</a></td> <td class="subsection"> <ul> <li><a href="/domains/root">Root Zone Registry</a></li> <li><a href="/domains/int">.INT Registry</a></li> <li><a href="/domains/arpa">.ARPA Registry</a></li> <li><a href="/domains/idn-tables">IDN Repository</a></li> </ul> </td> </tr> <tr> <td class="section"><a href="/numbers">Number Resources</a></td> <td class="subsection"> <ul> <li><a href="/abuse">Abuse Information</a></li> </ul> </td> </tr> <tr> <td class="section"><a href="/protocols">Protocols</a></td> <td class="subsection"> <ul> <li><a href="/protocols">Protocol Registries</a></li> <li><a href="/time-zones">Time Zone Database</a></li> </ul> </td> </tr> <tr> <td class="section"><a href="/about">About Us</a></td> <td class="subsection"> <ul> <li><a href="/performance">Performance</a></li> <li><a href="/reports">Reports</a></li> <li><a href="/reviews">Reviews</a></li> <li><a href="/about/excellence">Excellence</a></li> <!-- <li><a href="/news">News</a></li>--> <li><a href="/contact">Contact Us</a></li> </ul> </td> </tr> </table> <div id="custodian"> <p>The IANA functions coordinate the Internet鈥檚 globally unique identifiers, and are provided by <a href="http://pti.icann.org">Public Technical Identifiers</a>, an affiliate of <a href="http://www.icann.org/">ICANN</a>.</p> </div> <div id="legalnotice"> <ul> <li><a href="https://www.icann.org/privacy/policy">Privacy Policy</a></li> <li><a href="https://www.icann.org/privacy/tos">Terms of Service</a></li> </ul> </div> </div> </footer> <script> $(document).ready(function() { $("#nav_dom_int").addClass("selected") $("#nav_dom_int_policy").addClass("selected") $("#nav_dom_root_sub").hide() $("#nav_dom_idn_sub").hide() $("#nav_dom_dnssec_sub").hide() $("#nav_dom_tools_sub").hide() }); </script> </body> </html>