The purpose of this document is to describe the rules
for the allocation of names within the .IO domain and its
sub-domains. NIC.IO is responsible for the day-to-day running
of the NIC.
2. PROCESS DETAIL
2.1 The rules given here apply to all requests for names
in the .IO domain and all sub-domains of .IO except where
differing rules exist for a sub-domain. The rules for a
sub-domain shall incorporate all the rules in this document
along with such additional rules that are required. Agreement
of the Management of NIC.IO shall be required if the rules
of a sub-domain are to exclude any of the rules of this
document. Their agreement shall not unreasonably be withheld.
2.2 Where a dispute over the interpretation of the rules
exists, the Management of NIC.IO shall rule on the interpretation.
2.3 All NEW second and third level domain requests will
conform to RFCs 1034,
and any subsequent replacements. For designated zones the
requests may be handled by the automated Registration
System. This Registration System will apply the appropriate RFCs,
the rules and a check against the list of existing domain names. It
may also check that operating nameservers exist for the
2.4 If the rules are changed in the future, some names
approved under one set of rules might be rejected under
the revised rules. No rule change will ever affect the status
of a name which has been approved before the change unless
sound technical reasons require this.
3. MANDATORY RULES FOR SECOND LEVEL DOMAINS.
3.1 An applicant may reside in any legal jurisdiction.
3.2 Certain single letter, two or more letters or number domain
names are available for registration in a controlled and equitable
3.3 There shall be at least two nameservers for the domain (with addresses
specified in the request) operating at the time the request is submitted. There
is no requirement for the nameserver to be physically located in the British Indian
Ocean Territory. There is no restriction on the IP address of these nameservers.
4. MANDATORY RULES FOR THIRD LEVEL DOMAINS
4.1 An applicant must be resident in the British Indian Ocean Territory.
4.2 Two character names within an Third LD are allowed.
4.3 All second level names used by NIC.IO are banned from
being used as third level names. e.g. com.com.IO would be
banned as it is a second level name.
4.5 All top level domains are banned from being used as
third level names. e.g. net.org.IO and org.com.IO are not
4.6 All One Letter domains (i.e.[a-z].xxx.IO) are reserved
to cater for possible future sub-domain usage. The owner
shall still maintain it unless they volunteer to relinquish
4.7 There shall be at least two nameservers for the domain (with addresses
specified in the request) operating at the time the request is submitted. At least
one nameserver must be physically located in the British Indian Ocean Territory.
There is no restriction on the IP address of these nameservers.
Once an application has been approved a record will be
created in NIC.IO's database where management of the zone
is delegated to NIC.IO from which Web or NS records will
be generated and loaded into NIC.IO's Register of Domain
Names for the zone.
6. APPROPRIATE USE
No .IO domain may be used, directly or indirectly, for
any purpose that is sexual or pornographic or that is against
the statutory laws of any Nation. In the event of NIC.IO
being advised by any party that a specific site breaches
this condition then NIC.IO reserves the right to immediately
deactivate the offending registration. The applicant may
seek the reinstatement of any suspended domain name by seeking
a determination by an Arbitrator appointed by the World
Intellectual Property organisation.
7. UNSOLICITED COMMERCIAL E-MAIL (SPAM) MAIL POLICY
In the event that any .IO domain is used either directly or indirectly for
the purpose of directing unsolicited electronic mail ("spam mail") either
as the originator of the spam mail or as the address to which readers of spam
mail are referred, then NIC.IO reserves the right to send a cease and desist letter
to the registered Administrative Contact of the specified .IO domain name. Should
the Administrative Contact of the .IO domain name fail to adhere to the conditions
contained in the warning letter, then NIC.IO reserves the right to suspend the
operation of the offending .IO domain name until the necessary assurances are
obtained from the Administrative Contact.
8. WHOIS DISCLOSURE OBLIGATIONS
To promote stability of the .IO namespace it is beneficial that
members of the Internet community holding a domain name in the .IO
space make their contact information publicly available. NIC.IO
does this by allowing members of the public or organisations to
search the .IO Domain Name Register (via WHOIS) to ascertain the
contact information of associated with a specific domain name. The
default setting is that all contact information is available but
should the Domain Owner or Administrative Contact so elect, it is
possible to withhold the publication of certain personal data using
the appropriate on-line form or their Registrar to prevent
disclosure of certain contact information via publicly accessible
WHOIS services. Should the privacy settings be activated to prevent
disclosure of contact information where a domain name is used in an
inappropriate manner, NIC.TM reserves to the right to summarily
suspend the Domain Name from active use and publish the contact
information of all parties associated with the domain name.
9. CONTACT DATA ACCURACY
As per the Terms and Conditions, all contacts assocaited with a
domain name must supply accurate and verifiable contact
information; specifically the full name of the legal entity or
individual listed as the Domain Owner as well as the Administrative
Contact and a physical street address for service of official
notices along with a valid email address managed by each