In auction domaining, delivery of a purchased registration and a later move between registrars are separate events. The auction may fulfil the name into a specified account first, with conditions that affect further transfer.
Confirm the exact route, authority and restrictions before accepting a sale or scheduling a provider change. Keep registrar migration separate from website and email migration.
Confirm the auction’s fulfilment process
Read the listing’s receiving registrar, payment conditions and expected delivery. GoDaddy’s buyer guidance describes relevant auction conditions, including possible original-registrant renewal.
A winning result is not proof that the domain already appears in your account. Verify delivery through the service and receiving registrar before attempting a separate transfer.
The auction-check workflow helps document the acquisition.
Identify the kind of change
| Change | Process to check |
|---|---|
| Move between accounts at one registrar | The provider’s account-transfer rules. |
| Change the registration holder | Applicable holder-change requirements. |
| Move to another registrar | Receiving provider and registry transfer conditions. |
| Move website or email services | Separate hosting, data and DNS requirements. |
ICANN’s current Transfer Policy addresses covered registrar and holder changes. Country-code registries and particular providers need their own rules checked.
Check eligibility and access first
Confirm registrar control, current contact routes, expiry and any restriction from registration, a recent transfer, holder change or auction fulfilment. Read the reason for a restriction rather than assuming every lock can be removed immediately.
ICANN’s status-code guide provides administrative definitions. A status observation is a starting point for provider clarification, not permission to bypass a restriction.
Save the existing DNS configuration and identify email or recovery dependencies before changes.
Follow the receiving registrar’s documented steps
ICANN’s transfer FAQs explain the role of transfer authorisation and relevant conditions. Where required, obtain the code through the current registrar and keep it confidential.
Initiate the move through the receiving provider’s official process, with the exact domain and appropriate holder authorisation. Follow verification instructions through the providers themselves rather than assuming every case uses an identical email link.
Do not disable privacy, publish credentials or unlock the registration solely because an unexpected message requests it. Confirm the actual requirement with the provider.
Plan service continuity and timing
A registration move does not constitute a complete website or mailbox transfer. The hosting guide helps identify those separate responsibilities.
Allow for documented restrictions and processing rather than promising a universal completion time. If a sale depends on moving the name, agree realistic delivery conditions before settlement.
Verify completion and update the record
Confirm the exact registration in the receiving account, contacts, expiry, DNS and intended services. Save transfer and payment records, then secure account access and renewal settings.
The registration record should preserve the acquisition, transfer and next deadline. Keep provider instructions with it so later sales do not depend on an outdated generic transfer checklist.