.int Registration

The .int domain extension was introduced in the year 1988. Organizations formed on the basis of international treaties made between national governments are registered with the .int extension. An organization such as the above, that satisfies all the requirements listed in RFC 1591, is eligible to register a .int domain. Each organization can apply for only one registration. The sponsoring organization for .int registration is the Address Routing and Parametres Area (ARPA) Domain. There are some requirements to be fulfilled before the requested .int domain can be registered. The registrant must produce the relevant international treaty between or among the respective national governments as evidence. The treaty provided alone must establish the credentials of the organization applying for the .int registration. The organization should have an autonomous international legal character and must be answerable to and governed by international law.

If you meet all the required qualifications and want to apply for a domain name under INT then send the IANA a description of your organization. You can get the registration and other details from http://www.iana.org/int-dom/int.htm. The registrant is expected to send a copy of the treaty that established his organization to the .int Domain Registry, at the Internet Assigned Numbers Authority in California.

No fees need to be paid for registering the .int domain name. As per the present IANA policy, the .int gTLD is primarily sanctioned for international treaty organizations, and non-governmental organizations. The .eu.int sub-domain was used by the European Union-affiliated institutions. The .int sub domains are allowed only for international treaty-based organizations.

The University of Southern California/Information Sciences Institute handles the .int extension, ensuring safe and secure management. The .int registration was historically also used for "Internet infrastructure databases". The .int registration is no longer granted for international databases as per RFC 1591.