AWS Route53 documentation change
Summary
Added 'Transfer process overview' section with key steps and common failure points, updated section titles, and clarified domain ownership change process
Security assessment
Changes focus on improving transfer process documentation and troubleshooting guidance. While authorization codes and email verification are security-adjacent, these are standard domain transfer requirements rather than addressing a specific vulnerability. The 60-day ICANN rule clarification is a compliance note, not a security fix.
Diff
diff --git a/Route53/latest/DeveloperGuide/domain-transfer-to-route-53.md b/Route53/latest/DeveloperGuide/domain-transfer-to-route-53.md index 92b4cfda1..9f1f0b694 100644 --- a//Route53/latest/DeveloperGuide/domain-transfer-to-route-53.md +++ b//Route53/latest/DeveloperGuide/domain-transfer-to-route-53.md @@ -5 +5 @@ -Transfer requirements for top-level domainsStep 1: Confirm that Amazon Route 53 supports the top-level domainStep 2 (Optional): Transfer your DNS service to Amazon Route 53 or another DNS service providerStep 3: Change settings with the current registrarStep 4: Get the names of your name serversStep 5: Request the transferStep 6: Click the link in the confirmation and authorization emailsStep 7: Update the domain configuration +Transfer process overviewTransfer requirements for top-level domainsStep 1: Confirm that Amazon Route 53 supports the top-level domainStep 2 (Optional): Transfer your DNS service to Amazon Route 53 or another DNS service providerStep 3: Change settings with the current registrarStep 4: Get the names of your name serversStep 5: Request the transferStep 6: Click the link in the confirmation and authorization emailsStep 7: Update the domain configuration @@ -14,0 +15,38 @@ To transfer the registration for a domain to Amazon Route 53, follow the procedu +## Transfer process overview + +Domain transfer involves these key steps: + + 1. **Complete pre-transfer checklist** + +Verify prerequisites to avoid transfer failures. See [Pre-transfer checklist for domain transfers](./domain-transfer-checklist.html). + + 2. **Request transfer in Route 53 console** + +Enter domain name and authorization code. See Step 5: Request the transfer. + + 3. **Authorize via email** (_Customer action required)_ + +Click authorization link sent to registrant email within 5 days. See Step 6: Click the link in the confirmation and authorization emails. + + 4. **Wait for completion** + +Transfer completes automatically unless rejected by current registrar. Monitor status in console. + + + + +###### Most common failure points + +The following are solutions for common issues: + + * **Email not received** : Verify registrant email is accessible and check spam folder + + * **Domain locked** : Unlock at current registrar before starting transfer + + * **Invalid auth code** : Request new authorization code from current registrar + + * **60-day rule violation** : 60-day ICANN rule (eligibility window). Transfers are blocked within 60 days of initial registration or a registrant contact change. Some registrars allow an opt-out before the change—ask your current registrar if applicable. + + + + @@ -552 +590 @@ If you changed the following values, we send you a separate email that asks for -If you change the owner of the domain, as described in [Who is the owner of a domain?](./domain-update-contacts.html#domain-update-contacts-who-is-domain-owner), we send email to the registrant contact for the domain. +If you change the owner of the domain, as described in [What triggers a domain ownership change?](./domain-update-contacts.html#domain-update-contacts-who-is-domain-owner), we send email to the registrant contact for the domain. @@ -631 +669 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Transferring domains +Pre-transfer checklist @@ -633 +671 @@ Transferring domains -Viewing the status of a domain transfer +Common transfer issues