> ## Documentation Index
> Fetch the complete documentation index at: https://help.noxity.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Transfer a domain to Noxity

> Move an existing domain registration from another registrar to Noxity. Prerequisites, the auth code flow, the typical 5-7 day wait, and what to do when something stalls.

Moving a domain to Noxity preserves the existing expiry date and adds one year on top. Most TLDs charge the same as a registration; a few ccTLDs (`.at`, `.si`, `.uk`, `.co.uk`) waive the transfer fee entirely. See the [TLD overview](/domains/registrations/tlds/overview) for the per-TLD rate.

## Before you begin

Run through the list before you start the transfer at our end. Each item is something the losing registrar controls; if you skip one, the registry will reject the transfer and you'll need to start over.

* **Domain must be older than 60 days.** ICANN locks every gTLD for the first 60 days after a fresh registration or a recent transfer. Inside that window, the domain physically can't move. Check the registration date at the current registrar.
* **Domain must not be expired or in redemption.** A domain past expiry can't be transferred until it's renewed back to active state. Move it out of redemption first, or wait until the new registrar's flow lets you renew on transfer.
* **Transfer lock must be off.** Most registrars enable a "registrar lock" or "transfer prohibited" status by default. Toggle it off in the losing registrar's panel before you continue.
* **WHOIS privacy must not block emails.** If the privacy service forwards email to a junk folder or rejects unknown senders, the registry's confirmation message won't reach you. Either disable privacy temporarily, or confirm the forwarder is delivering messages from the registry.
* **The registrant email must be valid and reachable.** The auth code is sent there. So is the eventual transfer-confirmation email if your TLD requires it.
* **You have an auth code.** Different registries call it different things: EPP code (most gTLDs), AuthInfo (`.de`, `.it`), domain password (older registrars), or IPS tag (`.uk`, `.co.uk`). The losing registrar issues it on demand from their panel; some still require a support request.

<Note>
  `.uk` and `.co.uk` don't use an auth code. Nominet uses an IPS-tag model: the losing registrar pushes the domain to our IPS tag (`NOXITY` ‒ {/* TODO: confirm exact IPS tag once Nominet allocation is finalised */}) instead. The flow below explains how this differs.
</Note>

## Start the transfer

<Steps>
  <Step title="Place the order in the Members Area">
    Sign into the [Members Area](https://members.noxity.io), open **Domains** → **Transfer**, and enter the domain you want to move. The form pulls the current TLD's transfer price (and tells you if it's free for that TLD).

    Pay the order. Nothing pings the losing registrar yet — payment just queues the transfer order in our system.
  </Step>

  <Step title="Submit the auth code">
    Once the order is paid, paste the auth code into the field on the order summary page. We send it to the registry, which contacts the losing registrar and asks them to release the domain.

    For `.uk` / `.co.uk`, this step is replaced by asking the losing registrar to change the IPS tag on your domain to ours. We confirm the tag value in the order summary.
  </Step>

  <Step title="Approve the registry confirmation email (some TLDs)">
    Most gTLDs send a confirmation message to the registrant email asking you to approve the transfer. Click the approve link.

    A handful of TLDs skip this step. ccTLDs in particular often complete on the auth code alone.
  </Step>

  <Step title="Wait for completion">
    Typical timeline:

    * **gTLDs (`.com`, `.net`, `.org`, …)**: 5 to 7 days. ICANN policy lets the losing registrar hold the domain for up to 5 days; if they don't approve sooner, it auto-completes on day 5.
    * **`.eu`**: 1 to 2 days. EURid auto-approves the transfer once the registry accepts the auth code.
    * **`.si`, `.at`**: typically same-day. Free transfers, fast registries.
    * **`.uk`, `.co.uk`**: minutes. Once the IPS tag flips to ours, the domain is in our account immediately.
    * **`.de`**: typically 1 to 3 days. DENIC requires the gaining registrar to confirm DNS authority.
    * **`.it`**: 5 to 7 days. NIC.it runs an explicit approval process.

    You'll get a "transfer completed" email when it lands. The domain appears under **Domains** in the Members Area, and the [domain panel](/domains/management/panel) lets you manage it.
  </Step>
</Steps>

## What we keep, what we don't

A transfer moves the **registration** between registrars. It doesn't move anything that lives outside the registry record.

| Stays                                                       | Doesn't move                                                                  |
| ----------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Domain name and TLD                                         | DNS records, unless we manage DNS for it                                      |
| Existing expiry date (we add one year on top)               | Email forwarding set up at the losing registrar                               |
| Registrant contact data (we copy it in)                     | Subscriptions tied to the losing registrar (privacy proxy, premium DNS, etc.) |
| DS records / DNSSEC chain (where the registry preserves it) | Any one-off services bundled with the domain at the losing registrar          |

If you used the losing registrar's nameservers, plan to either point the domain at our [in-house NS](/domains/management/ns/inhouse) or your own external DNS before the transfer completes. The DNS doesn't break the moment the transfer lands, but the losing registrar will eventually shut down their NS for accounts that have moved away.

## Common issues

<AccordionGroup>
  <Accordion title="Auth code rejected">
    The most common cause is a copy-paste with a stray space or a misread `0`/`O`. Go back to the losing registrar, copy the code straight from their panel, paste into our field. Some auth codes are case-sensitive.

    If the code is genuinely fresh and still gets rejected, the losing registrar may have invalidated it (some rotate the code after it's been viewed once). Ask them to issue a new one and try again.
  </Accordion>

  <Accordion title="Transfer is stuck and the 5-day timer has passed">
    The losing registrar can drag a transfer to the very last minute. ICANN policy lets it auto-complete once the timer runs out, but only if their system actually releases the domain. If a transfer is past day 6 with no movement, open a ticket and we'll escalate to the registry.
  </Accordion>

  <Accordion title="Registry says the domain is locked">
    Two flavours of lock. Registrar lock (the losing registrar can toggle this in their panel) and registry lock (some high-value names use this; only the registry can lift it via the losing registrar). Unlock at the losing registrar before the auth code goes in.
  </Accordion>

  <Accordion title="Confirmation email never arrived">
    Check whether WHOIS privacy is intercepting it. Some privacy services hide the registrant email and forward only specific senders. Disable privacy for the duration of the transfer, or whitelist the registry's domain. The exact registry sender is in the per-TLD page.
  </Accordion>

  <Accordion title="`.uk` IPS tag isn't flipping">
    Nominet processes IPS tag changes quickly, but the losing registrar has to actually push it. Some UK registrars require a support ticket to change the tag (especially the bigger ones). If it's been more than a few hours, follow up with the losing registrar; we can't pull the tag from our side.
  </Accordion>

  <Accordion title="`.de` rejected because nameservers don't respond">
    DENIC checks the new nameservers respond authoritatively for the domain *before* completing the transfer. If the registrar that's losing the domain is also providing the DNS, the transfer fails because the new NS aren't set up yet. Set up DNS at the gaining configuration first, then start the transfer.
  </Accordion>

  <Accordion title="Domain transferred but DNS broke">
    DNS doesn't move with the registration. If the losing registrar was your DNS host, the records vanish when they shut down their NS for the domain. Add the records under [in-house NS](/domains/management/ns/inhouse) or your external DNS provider, then update the NS records at the registry.
  </Accordion>
</AccordionGroup>

## Next

<CardGroup cols={2}>
  <Card title="Transfer out" icon="truck-arrow-right" href="/domains/transfers/outbound">Move a domain away from Noxity.</Card>
  <Card title="Domain panel" icon="bars-progress" href="/domains/management/panel">Manage a domain after the transfer lands.</Card>
</CardGroup>

## Need a hand?

<CardGroup cols={2}>
  <Card title="Open a ticket" icon="life-ring" href="https://members.noxity.io/submitticket.php">
    Best for anything that needs an account check or a config change on our end.
  </Card>

  <Card title="Live chat" icon="messages" href="https://noxity.io/contact">
    Faster for quick questions during business hours.
  </Card>
</CardGroup>

<div className="mt-8">
  <Accordion title="Sources" icon="book-bookmark">
    * [Transfer out](/domains/transfers/outbound)
    * [TLD overview](/domains/registrations/tlds/overview)
    * [Verification emails](/domains/registrations/contact-details/verification-emails/overview)
    * [ICANN inter-registrar transfer policy ↗](https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en)
    * [Nominet IPS tag procedure ↗](https://www.nominet.uk/domain-support/transferring-a-domain/)
  </Accordion>
</div>