Buy .nr Domain Name

No. Nothing in the registry's texts asks for establishment in Nauru, a local contact, a tax number or a commercial capacity, and the country list in the registration form covers the whole world. Holders visible today include people and organisations based in France, Japan, Saudi Arabia, Vanuatu, Austria and the United States. Private individuals may register too: the only personal condition in the agreement is that you are of legal age to enter into it. The one restriction sits in the sub-zones — edu.nr and gov.nr are reserved for educational and government entities in Nauru.

The registry publishes no minimum length at all; none of its public texts defines a lower character bound. Measurement shows single-character names actually registered: a.nr belongs to a Saudi company, is delegated to Cloudflare name servers and resolves to a working address, while d.nr has been held by a Vanuatu company for years. Two-letter names are far more common still. If a short name is refused at checkout, the cause is our own length setting rather than a registry rule, and you can write to us from the contact page.

You do not choose the term when you register. The registry's own form has no period or year field of any kind; the registry sets the term and puts it on the invoice. The agreement says a registration ends at the close of the year in which it was made and is renewable in perpetuity thereafter, yet real records show anniversary-dated expiries and periods running from one year up to nine. So .nr has no fixed registration range, and the term you see at checkout is the term we apply. Note your renewal date in your own calendar as well.

Both sit with the same registry under the same registration agreement; the difference is the level and the habit of use. .nr is registered directly at the second level and, being short, invites domain hacks and two-letter abbreviations. .com.nr sits at the third level and behaves like a classic corporate namespace: Nauru's own institutions and the defensive registrations of global brands are concentrated there. Because the rules treat the levels as independent, the holder of a .nr name cannot stop the same label going to someone else under .com.nr.

Yes, and in full. The registration agreement expressly grants the registry the right to publish the following in a publicly accessible database: your name and postal address, the names, addresses, email addresses and telephone numbers of the administrative and technical contacts, the name servers, and the creation and expiry dates. Every record examined showed those fields unmasked, and no privacy service is offered for purchase. That is why a business address is the sensible choice for .nr. You can see how your record looks on the whois search page.

Two, and they must be different people. The registry asks for one administrative and one technical contact record per domain name, and its help text states that for redundancy these persons cannot be the same. Each contact gets its own handle and password; every later change to the name is made with that handle and password, so losing the password means losing control of the name. You also have to enter at least two working name servers before the name goes live, and the registry does not host them for you.

There is no change of registrar here as you know it from generic extensions, because .nr has neither an accredited registrar system nor an authorisation code; registry and registrar are the same organisation. What can change is ownership: the agreement states that you may transfer your registration to a third party of your choice and that the procedure follows the conditions the registry publishes. The transfer works as a record update driven by the name's handle and password. While a dispute is on file you may not alter the record without approval. Start on the domain transfer page.

No. Measurement shows no DS record for .nr in the root zone, and none for the com.nr sub-zone either. Not one page of the registry mentions DNSSEC, DS records or key submission, and the registration form has no field in which a key could be entered. The practical consequence is that you cannot sign your .nr name with DNSSEC, because the chain that would validate the signature is not established in the parent zone. Security has to come from your name server side and from a strong contact password.