Transferring a domain

SuperSpace can move a domain in from another registrar, out to another registrar, or hand it to another customer on SuperSpace's own registrar with a push transfer (no inter-registrar transfer and no authorization code). All three run through the registrar and are asynchronous — depending on the extension and the other registrar they can finish in minutes or take several days.

Each registered domain has its own pages — open Domains in the sidebar and pick the domain. The tabs are Overview, DNS, Nameservers, Contacts, Lock & Transfer Code, and Settings.

Transferring a domain in

Move a domain you own elsewhere onto SuperSpace.

First, at your current registrar: unlock the domain (remove its transfer lock), make sure the registrant contact can receive email, and copy the domain's authorization code.

Then, in the SuperSpace dashboard:

1. Find the domain. In the sidebar choose Domains, click New Domain, and search for the exact name. A registered domain comes back as Taken; when it's transferable, a transfer price and a Transfer button appear. Click Transfer to add it to your cart. (For the full search-and-cart flow, see Purchasing a domain; you can also transfer a domain in while attaching it to a new site — see Adding a domain to a site.)

2. Enter the authorization code. In the cart, the domain shows an Authorization code (EPP code) field. Paste your code and click Save. Depending on the extension the field is required, optional ("Authorization code is optional for this TLD"), or hidden. The cart also notes that the current registrant will receive an approval email, that the transfer includes a renewal period, and that the registry doesn't refund the fee if a transfer fails — so double-check the code before paying.

   If the cart blocks the transfer

   • Domain locked — the domain is still transfer-locked; unlock it at your current registrar first.
   • Domain too recently registered — ICANN requires domains to be at least 60 days old before they can be transferred.

3. Pay. Continue through checkout and pay, the same as a registration (see Purchasing a domain for the contact and payment steps).

4. Approve at the losing registrar. The registrar emails a transfer-approval request (a Form of Authorization) to the domain's current registrant, who must approve it. This is usually the slowest step — it can take hours to days.

5. Watch it complete. While the transfer is in flight the domain shows a Transfer In Pending badge and an in-progress banner ("Your domain transfer is in progress. This typically takes 5–7 days."). You can set up DNS records right away on the DNS tab — they take effect once the transfer completes. When it finishes, the domain becomes active and SuperSpace turns auto-renew back on (registrars reset auto-renew during a transfer, so SuperSpace re-asserts it).

Transferring in with the API

Transfer-in is a paid order through the same cart/billing flow as a registration — POST /api/orders/domain with action: transfer and the authcode:

curl -X POST \
  -H "Authorization: Bearer $SUPERSPACE_TOKEN" \
  -H "X-Auth-Account: $ACCOUNT_ID" \
  -H "Content-Type: application/json" \
  -d '{"domain":{"name":"example.com","action":"transfer","authcode":"EPP-CODE-HERE"}}' \
  https://control.superspace.nl/api/orders/domain

It returns 202 with the cart envelope; poll the returned order until its status is terminal. This call is OAuth-blocked and needs a user-scoped session or API-key credential, the X-Auth-Account header, and the domain-registration feature flag. See Orders & Carts and Domain registration.

Transferring a domain out

Move a SuperSpace-registered domain to another registrar.

1. Open the domain's Lock & Transfer Code tab. In the sidebar choose Domains, pick the domain, then open Lock & Transfer Code.

2. Unlock the domain. Under Domain Lock, if the status is Locked, click Disable lock. If it shows Registry Locked instead, the registry has imposed a lock (typically for the first 60 days after registration or a previous transfer) — you can't transfer out or retrieve the code until that clears.

3. Get the transfer code. Under Transfer Code (EPP), click View transfer code, confirm your identity if prompted, then Copy the Authorization Code. If the extension doesn't use an auth code, you'll see "This TLD does not use a transfer authorization code" with a pointer to use the Push Transfer option under Settings instead — see Push transfers.

4. Start the transfer at the new registrar. Give the gaining registrar the authorization code and let them run the transfer. When it completes on their side, the domain leaves SuperSpace.

Approving an incoming transfer request. For extensions whose registrar uses transfer approval, when another registrar initiates a transfer you'll see an Outgoing Transfer Pending banner ("Another registrar has initiated a transfer for this domain") with a View Details link. That opens Outgoing Transfer Details with two buttons:

• Approve Transfer — confirms the transfer to the gaining registrar.
• Reject Transfer — cancels it; the domain stays with SuperSpace.

After you approve, the domain can sit at Transfer Out Pending for a while as the gaining registrar finishes — that's normal. (Extensions without an approval step have no buttons; the registry simply processes the transfer.)

Transferring out with the API

Unlock the registration, retrieve the code, and (when a registry-approval request is pending) approve or reject it. :id is the registration's guid:

# Unlock (lift CLIENT_TRANSFER_PROHIBITED)
curl -X PATCH \
  -H "Authorization: Bearer $SUPERSPACE_TOKEN" -H "X-Auth-Account: $ACCOUNT_ID" \
  -H "Content-Type: application/json" -d '{"locked":false}' \
  https://control.superspace.nl/api/domain_registrations/$REGISTRATION_ID/lock

# Retrieve the EPP / auth code (needs the domains:write scope)
curl -H "Authorization: Bearer $SUPERSPACE_TOKEN" -H "X-Auth-Account: $ACCOUNT_ID" \
  https://control.superspace.nl/api/domain_registrations/$REGISTRATION_ID/epp_code

# Resolve a pending outbound transfer
curl -X POST \
  -H "Authorization: Bearer $SUPERSPACE_TOKEN" -H "X-Auth-Account: $ACCOUNT_ID" \
  -H "Content-Type: application/json" -d '{"decision":"approve"}' \
  https://control.superspace.nl/api/domain_registrations/$REGISTRATION_ID/transfer_out

See Domain registration for the full request and response shapes, including the registry-lock and hidden-authcode error cases.

Push transfers

A push transfer moves a domain to another customer on SuperSpace's registrar — without a full inter-registrar transfer and without an authorization code. It's the right path when an extension doesn't expose an auth code, or when you're handing a domain to another account on the same registrar. It's only available for extensions that support it.

1. Start the transfer on the receiving side first. The receiving registrar or customer gives you their Receiving Registrar TAG — a registrar identifier. SuperSpace reminds you: "Please initiate the transfer at your new registrar before using this option. They will provide you with the correct value to enter here."

2. Open the domain's Settings tab. In the sidebar choose Domains, pick the domain, and open Settings. In the Transfer Out card ("Transfer this domain to another provider via push transfer. This action cannot be undone."), click Transfer to another provider.

3. Enter the TAG and confirm. On the Push Transfer form, paste the Receiving Registrar TAG, then click Initiate Push Transfer.

4. Wait for the other side to accept. The domain shows Push Transfer In Progress and is removed from your workspace once the receiving provider accepts it. On completion SuperSpace cancels the domain's subscription — the same cleanup as a transfer out.

Push transfers with the API

POST /api/domain_registrations/:id/push_transfer with the destination registrar handle as recipient:

curl -X POST \
  -H "Authorization: Bearer $SUPERSPACE_TOKEN" -H "X-Auth-Account: $ACCOUNT_ID" \
  -H "Content-Type: application/json" -d '{"recipient":"REG-IDS"}' \
  https://control.superspace.nl/api/domain_registrations/$REGISTRATION_ID/push_transfer

Returns 200 or 202. Extensions that don't support it return 422 push_transfer_unsupported. See Domain registration.

Next steps

• Purchase a domain if you'd rather register a new one
• Connect a domain to a site
• Manage DNS records once the domain is on SuperSpace
• Automate transfers with the Domain registration API