On this page
Identify the domain and actual registration agreement
The Internet Corporation for Assigned Names and Numbers (ICANN) registrant framework describes access to the registrar agreement, prices, support and management instructions. Check the actual generic top-level domain (gTLD), such as .com, and registrar/proxy arrangement; country-code domains can follow different rules.
ICANN’s updated Transfer Policy, required by August 2025, recognises the Registered Name Holder’s transfer authority. Registrar transfer and a change of registered holder are separate from the domain’s routing settings (the Domain Name System, or DNS) and website hosting. Do not assume public contact details or the agency’s dashboard alone decide every contractual ownership issue.
Changing holder details can affect the transfer timetable
The policy requires a 60-day inter-registrar lock after a Change of Registrant unless the registrar offered, and the holder chose, an opt-out beforehand. A separate clause covers the transfer code (AuthInfo) and specified client transfer lock where the registrar does not provide self-service: it uses five calendar days after the holder’s initial request. Other valid restrictions still apply.
Fictional example: management wants to change the agency-held registration into the company’s name and move registrar the next day. Check the actual eligibility, authorisations and order of changes with the registrar before promising that timetable.
Test the authorised responsibility, not a shared password
Use a company-authorised process to confirm these records. Keep authorisation codes, identity documents and credentials in the approved registrar/security process, never in ELN.
| Handover record | Question to resolve |
|---|---|
| Holder/registrar/TLD | Which registration and agreement are involved? |
| Authorised access | Can the right company people use recovery and support routes? |
| Renewal | Where do notices go, when is expiry and who checks payment? |
| Transfer | Which actual lock, holder-change and authorisation steps apply? |
| Website/DNS hosting | Who operates these separate services during the transition? |
Keep renewal working while the transfer is resolved
The current gTLD expiry policy calls for notices about one month and one week before expiry under its conditions. Confirm that they reach the responsible company contact, with a supported backup and current payment details if auto-renew is selected. Do not treat reminders as extra registration time.
Get the actual renewal, expired-renewal and restoration terms from the registrar. An agency handover plan should preserve the renewal job even if a registrar move needs a different date. This exercise supplies no domain title or recovery guarantee.
Scope
- Selected current ICANN gTLD framework only. No particular domain ownership, proxy entitlement, transfer eligibility, country-code rule, account recovery or uninterrupted service is determined.
Next step
Use Management dependence to assign registration authority, renewal, account recovery and the separate website/DNS jobs, including a backup person.
Sources & review notes
Internet Corporation for Assigned Names and Numbers
Passage, dates and research notes
organisation-policy-guidance · Registrant rights: registration agreement, registrar/provider identity, pricing, support and management/renewal/transfer instructions
Relevant rights and account/payment responsibilities read. Old public-WHOIS wording is not adopted; current Registration Data Policy and actual privacy/proxy arrangement must be checked.
Internet Corporation for Assigned Names and Numbers
Passage, dates and research notes
domain-registration-policy · Updated-policy implementation note; I.A.1.1, 3.7–3.9, 5.1–5.7; II.A–C and lock footnote
Actual selected current-policy text read, required by 21 August 2025. Uses Registered Name Holder authority, not superseded Administrative Contact wording. Other valid locks/disputes and TLD/contract scope remain separate.
Internet Corporation for Assigned Names and Numbers
Passage, dates and research notes
domain-registration-policy · Updated implementation note; sections 1–4 and notes on expiry notices/fees and backup contacts
Actual policy body read. gTLD notice/recovery scope and exceptions are not converted into guaranteed uninterrupted service or a universal country-code rule.
Detailed rule records (2)
The updated Transfer Policy recognises Registered Name Holder authority. Its non-self-service AuthInfo/unlock provision uses 5 calendar days after the holder’s initial request, subject to applicable requirements. Change of Registrant triggers a 60-day inter-registrar lock unless an available prior opt-out was chosen.
Transfer Policy, updated 21 February 2024 Registrants’ Benefits and ResponsibilitiesThe policy calls for pre-expiry notices approximately one month and one week before expiry, and specified post-expiry notice/renewal conditions. Published fee and notification-method information must be available under its conditions.
Expired Registration Recovery Policy, updated 21 February 2024 Registrants’ Benefits and ResponsibilitiesBookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.