Skip to main content
You’re free to move any domain registered with us to another registrar. We don’t charge an outbound fee, we don’t hold domains, and we don’t make you ask. The flow is the mirror of transferring in: the gaining registrar pulls the domain after you give them an auth code. Most of what gates the transfer is set by ICANN or by the registry of the TLD, not by us.

​
Before you begin

  • Domain must be older than 60 days. Same ICANN rule that applies to transfers in. A domain that you registered or transferred to us less than 60 days ago can’t move yet.
  • Domain must not be expired. Renew first if it’s past expiry, then transfer.
  • Transfer lock must be off. We enable it by default after a registration to defend against unauthorised transfers. Toggle it off in the domain panel before you generate the auth code.
  • Registrant email must be reachable. The transfer-out confirmation goes there. If it bounces, we can’t approve.
  • WHOIS privacy must not block emails. Same as inbound — privacy filters can swallow the confirmation email.

​
Get the auth code

1

Open the domain in the panel

From the Members Area, open Domains, click the domain, then Manage.
2

Disable the transfer lock

Find the Transfer lock toggle and switch it off. The change applies immediately at the registry; no waiting period for most TLDs.
.de doesn’t use a registrar lock toggle in the same way. The auth code (AuthInfo) is generated on demand and is what gates the transfer instead.
3

Generate the auth code

Click Get auth code (sometimes labelled EPP code or AuthInfo depending on the TLD). The code displays once on the page and gets emailed to the registrant address.For .uk and .co.uk, there’s no auth code to generate. Instead, we change the IPS tag on the domain to whatever the gaining registrar specifies. Pass the gaining registrar’s tag to support and we’ll set it.
4

Hand the code to the gaining registrar

Start the transfer at the receiving registrar’s site. They’ll ask for the auth code; paste it in. From this point, the gaining registrar drives the timeline.

​
Approve the transfer

When the gaining registrar submits to the registry, ICANN policy lets us notify you before we approve. The email goes to the registrant email on file.
1

Read the transfer-out confirmation email

Subject pattern: “<domain> is being transferred out of Noxity”. Body lists who’s gaining the domain and includes approve and cancel links.For details on the email itself, see Verification emails → Transfer-out confirmation.
2

Click approve

Once approved, the registry releases the domain to the gaining registrar within minutes for most ccTLDs and within a day for gTLDs.
3

Or wait for auto-approval

If you don’t act, the transfer auto-completes after the gaining registrar’s clock runs out (typically 5 days for gTLDs). This is ICANN policy; the assumption is that whoever has the auth code is authorised to move the domain. If that’s wrong, click cancel in the confirmation email instead.

​
What you keep when you leave

  • The remaining time on your registration. A transfer adds one year to the existing expiry; you don’t lose any time you’ve already paid for.
  • The DNS records, if you want them. Export from the domain panel before the transfer completes. Once the domain leaves, our DNS for it shuts down within a few days.
  • The historical record. We keep the registration history for our own audit trail; the new registrar will see the existing WHOIS record and pick up from there.

​
Common issues

Check the registrant email’s spam folder, then check whether WHOIS privacy is forwarding messages somewhere unexpected. The auth code also displays once in the panel at generation time; you can copy it from there.If neither worked, generate a fresh code; the previous one is invalidated when a new one issues.
Most likely a stray space on copy-paste. Some auth codes are case-sensitive. Generate a fresh code from the panel and try again.
ICANN’s 60-day lock applies to brand-new registrations and to domains that recently transferred in. There’s no override; the lock is registry-side. Wait it out.
The new registrant on the receiving side may not meet the TLD’s eligibility rules. .eu requires EU/EEA residency or citizenship; .it requires the same plus San Marino, Vatican City, or Switzerland. Confirm with the receiving registrar before you start.
Privacy proxy or spam filter is the usual cause. Whitelist noreply@noxity.io and domain-notifications@noxity.io on the registrant inbox. If the email is genuinely missing, open a ticket — we can re-send.
Our DNS for the domain stops responding shortly after the registration moves. Either set up DNS at the gaining registrar before the transfer completes, or use an external DNS provider and update the NS at the registry from the gaining side.

​
Next

Transfer in

Move a domain to Noxity.

Domain panel

Generate the auth code from here.

​
Need a hand?

Open a ticket

Best for anything that needs an account check or a config change on our end.

Live chat

Faster for quick questions during business hours.