AWS Route53 documentation change
Summary
Added detailed section about common transfer error messages including resolution steps, improved troubleshooting structure, and added cross-references
Security assessment
The changes document security-adjacent features like authorization codes, transfer locks, and ICANN transfer rules, but there's no evidence of addressing a specific vulnerability. The content explains existing security mechanisms (EPP codes, domain locks) rather than patching a security issue.
Diff
diff --git a/Route53/latest/DeveloperGuide/troubleshooting-domain-transfer-failed.md b/Route53/latest/DeveloperGuide/troubleshooting-domain-transfer-failed.md index 9b54d86a6..2264b7dbb 100644 --- a//Route53/latest/DeveloperGuide/troubleshooting-domain-transfer-failed.md +++ b//Route53/latest/DeveloperGuide/troubleshooting-domain-transfer-failed.md @@ -5 +5 @@ -You didn't click the link in the authorization email The authorization code that you got from the current registrar is not valid "Parameters in request are not valid" error when trying to transfer a .es domain to Amazon Route 53Is the internationalized domain name you're transferring to Amazon Route 53 listed in punycode? +You didn't click the link in the authorization email The authorization code that you got from the current registrar is not valid "Parameters in request are not valid" error when trying to transfer a .es domain to Amazon Route 53Is the internationalized domain name you're transferring to Amazon Route 53 listed in punycode?Common transfer error messages @@ -9 +9,5 @@ You didn't click the link in the authorization email The authorization code that -Here are some common reasons that transferring a domain to Amazon Route 53 fails. +If your domain transfer has already failed or been rejected, use this section to diagnose and resolve the failure. + +###### Note + +For preventing issues during active transfers, see [Preventing common Route 53 transfer issues](./domain-transfer-troubleshooting.html). @@ -20,0 +25,2 @@ Here are some common reasons that transferring a domain to Amazon Route 53 fails + * Common transfer error messages + @@ -54,0 +61,85 @@ If you get an error while transferring an IDNs to Route 53, use punycode to repr +## Common transfer error messages + +When a domain transfer fails, you'll typically receive an error message either in the Route 53 console or via email. Here are the most common error messages and how to resolve them: + +### "Transfer was rejected by the registry" + +This error occurs when the domain registry blocks the transfer for one of several reasons. The most common causes are: + + * The domain doesn't meet the 60-day ICANN rule. ICANN requires that transfers be blocked within 60 days of initial registration or a registrant contact change. + + * The domain has transfer lock enabled at your current registrar. + + * The domain is in a status that prevents transfers, such as `clientTransferProhibited`, `serverTransferProhibited`, `pendingDelete`, `pendingTransfer`, or `redemptionPeriod`. + + + + +To resolve this issue, check the following with your current registrar: + + * Verify that the domain is more than 60 days old from the date of registration. If you recently changed the registrant contact information, you might need to wait 60 days from that change. Some registrars allow you to opt out of this restriction, so ask your current registrar if this option is available. + + * Unlock the domain by disabling any transfer locks or domain locks. + + * Check that your domain status allows transfers. You can verify the domain status using a WHOIS lookup or by contacting your current registrar. + + + + +### "Invalid authorization code" or "Auth code is incorrect" + +This error means that the authorization code (also called an EPP code or transfer code) that you entered is not valid. This can happen if the code has expired, was entered incorrectly, or wasn't obtained from your current registrar. + +To resolve this issue: + + * Contact your current registrar to request a new authorization code. Make sure to ask how long the code will remain active so you can complete the transfer before it expires. + + * When you receive the new code, verify that it's different from the previous code. If it's the same, ask your registrar to refresh or regenerate the authorization code. + + * Double-check that you're entering the code exactly as provided, including any uppercase or lowercase letters, numbers, and special characters. + + + + +### "Transfer authorization email not received" or "Authorization timeout" + +This error occurs when you don't click the authorization link in the transfer confirmation email within the required timeframe (typically 5 days). ICANN requires this authorization step for all domain transfers. + +If you didn't receive the authorization email or missed the deadline, check the following: + + * Check your spam or junk mail folder. Transfer authorization emails are sometimes filtered by email providers. + + * Verify that your mailbox isn't full and doesn't have storage limitations that might prevent email delivery. + + * Check if your email provider has policies that filter incoming mail from unknown senders. + + * Confirm that you can access the registrant email account and that the email address is still active. + + + + +If necessary, update your contact information with your current registrar before requesting another transfer. For information about resending the authorization email, see [Resending authorization and confirmation emails](./domain-click-email-link.html). + +### "Domain is locked" or "Transfer prohibited" + +This error indicates that your domain has a lock enabled that prevents transfers. Most registrars enable domain locks by default as a security measure to prevent unauthorized transfers. + +To resolve this issue, log into your account with your current registrar and disable the domain lock or transfer lock settings. The exact steps vary by registrar, but you'll typically find these settings in your domain management or security settings. If you need help finding these settings, contact your current registrar for assistance. + +### "Contact information verification required" + +This error occurs when you've recently changed your domain's contact information. ICANN rules require a 60-day waiting period after contact changes before a domain can be transferred to prevent fraudulent transfers. + +To resolve this issue, you have two options: + + * Wait 60 days from the date of the contact change before attempting the transfer again. + + * Contact your current registrar to verify your current contact information. Some registrars may allow you to opt out of the 60-day restriction if you can verify your identity. + + + + +###### Note + +If you receive an error message that isn't listed here, contact AWS Support and include the exact error text. Our support team can help you diagnose and resolve transfer issues specific to your situation. + @@ -61 +152 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -My domain is suspended (status is ClientHold) +My domain operation failed