🇳🇺 .nu — Niue

The .nu is a country-code top-level domain (ccTLD) operated by Internetstiftelsen (The Swedish Internet Foundation). This article documents the technical, operational, and contractual requirements for the TLD, along with special considerations for registry, registrar, and domain management.

General Information

Domain Lifecycle

Grace periods

Launch Phases & Availability

Domain Characteristics

Contacts & Roles

Nameservers & DNS

Transfer Policy

WHOIS & RDAP

Dispute Resolution

.nu is the ccTLD for Niue, operated from Sweden by Internetstiftelsen on the same EPP platform as .se and under the same technical rules. There is no local presence requirement.

Contact Attributes

.nu provisions the holder (the registrant) only, and that holder must carry a personal or organization number:

The country code identifies the jurisdiction in which the person or company is registered, which is not necessarily the country in the contact's postal address. A German company operating from Stockholm is [DE], not [SE].

REGISTRY_SE_ORG_NO is immutable once the handle exists at the registry. REGISTRY_SE_VAT_NO can be changed.

[SE] numbers are verified by the registry

For every country code other than [SE], the registry accepts a free-form identifier — the common case for .nu, which has no local presence requirement. [SE] is the exception: it requires a valid Swedish personal or organization number — six digits, a hyphen, then four digits ([SE]NNNNNN-NNNN) — and the registry verifies the number itself, not only its format.

⚠️ A correctly formatted but non-existent number is rejected. [SE]111111-1111 matches the documented format and still fails:

{
  "type": "registry-request",
  "title": "Registry Request Error",
  "status": 400,
  "code": "ERROR_REGISTRY_REQUEST",
  "detail": "2004: Parameter value range error: Value error personal/organization identification number"
}

json

Supply the holder's own personal or organization number, or use a non-Swedish country code when the holder is registered elsewhere.

Internetstiftelsen's EPP specification uses [SE]802405-0190 as its worked example (§7.1.5). That is Internetstiftelsen's own organisationsnummer — a live number, not a test value — so treat it as illustrative and submit the holder's own number instead.

When the holder has no organization name and the country code is [SE], the registry expects a personal number rather than an organization number.

Auth Codes

.nu auth codes are owned by the registry. A registrar cannot choose the value: the registry generates it, returns it in the registration response, and does not expose it in a later domain info request.

Request a fresh code with POST /v1/domains/tld-specific/nu/{domain_reference}/auth_code/request, which returns the code directly and invalidates the previous one. This is how a code consumed by a transfer is replaced.

Transfers

.nu transfers complete immediately: there is no pending window, no approval and no rejection. A transfer request either succeeds outright or fails.

Two consequences are worth planning for:

• the gaining registrar learns the outcome from the transfer response itself, with no notification to wait for;
• the losing registrar is notified after the fact and cannot prevent the transfer.

Transfers do not extend the registration period, and the auth code is consumed in the process.

Contacts on an Inbound Transfer

Transferring a .nu domain in does not move its contact with it. The registry clones the holder under your account as a new handle, and that clone is incomplete: it retains the name, email address, phone number and iis:orgno, but the postal address is returned as empty strings.

A cloned holder is returned in this form:

{
  "id": "76uFie8Nap2SVSfN",
  "roid": "CONTACT_0000129392-TEST",
  "email": "person@example.com",
  "voice": "+46.812345678",
  "postal_infos": [
    {
      "type": "loc",
      "name": "Full Name",
      "org": null,
      "street": [""],
      "city": "",
      "sp": null,
      "pc": null,
      "cc": ""
    }
  ],
  "status": ["ok", "linked"]
}

The street, city, state, postal code and country the holder had at the losing registrar are not carried over, and cannot be recovered from the registry.

Because a contact cannot be stored without an address, the import populates each empty field with OpusDNS's own company address rather than leaving it blank. An imported .nu holder therefore arrives with Franz-Mayer-Str. 1, Regensburg, 93053, DE, even though the holder has no connection to that address. The name, email address, phone number and REGISTRY_SE_ORG_NO are the holder's own.

⚠️ Update the holder after an inbound transfer. The placeholder address is a technical stand-in, not the holder's data. Correct it with PATCH /v1/contacts/{contact_id} once the transfer completes, and the change is propagated to the registry.

Holder Verification

Internetstiftelsen may hold a new registration while it verifies the holder's data. The domain is created, but the registry applies serverHold, serverTransferProhibited and serverRenewProhibited, so it does not resolve and cannot be transferred or renewed while the check is open.

The check clears when the registry accepts the holder data, or when the holder is replaced with one that passes. Either outcome is reported by the registry and reconciled onto the domain automatically, so these statuses are removed without intervention. No action is required beyond correcting the holder data when the registry asks for it.

Registry Lock

Registry lock blocks updates, transfers and deletions, and can be requested when registering or updating a domain. The registry does not support unlocking over EPP, so removal must be arranged directly with Internetstiftelsen.