Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- On November 12, AWS announced that customers can submit restoration requests through the Route 53 console, CLI, or SDKs without first opening an AWS Support case.
- The request must come from the same AWS account to which the domain was originally registered, and the TLD registry must still allow restoration. Disappearing from the console alone does not prove recovery is no longer possible.
- The .com expiry timeline is specific to that TLD; other TLDs have their own rules. Generic TLDs deleted within the first five days after registration are a separate exception and do not receive the standard 30-day redemption period.
- Restoration usually costs more than renewal or registration and can cost much more. Premium domain prices are set individually and may change. AWS credits cannot pay the restoration fee.
- Restoration is asynchronous: HTTP 200 and an OperationId mean the request was accepted, not completed. Track its status, then verify the domain and the DNS configuration used by its website or email.
What changed in the November 12 announcement
On November 12, 2026, AWS announced that Amazon Route 53 Domains now lets customers restore expired or recently deleted domains through the Route 53 console, AWS CLI, or AWS SDKs. Previously, customers had to contact AWS Support. AWS lists a missed renewal, an expired payment method, and accidental deletion as common reasons for restoration.
Route 53 works with the top-level domain (TLD) registry to reactivate the registration and return the domain to its AWS account. Self-service changes how you submit a request; it does not extend the registry deadline or mean every TLD supports restoration.
Check the original account and registry window first
The request must come from the AWS account to which the domain was originally registered. Find the domain’s TLD in Route 53’s TLD list and check whether that registry supports restoration and how long its window lasts after expiry or deletion. The window varies by TLD.
A domain may disappear from the Route 53 console after the late-renewal period ends or after it is deleted. That alone does not prove the registry has released it permanently. Check the relevant TLD rule before deciding whether restoration is still possible. Route 53’s registration list is also different from the scope of its DNS service.
The .com timeline is an example, not a universal 30-day clock
Route 53 lists this timeline for .com: late renewal through Route 53 is possible until 44 days after expiry; on day 45, the domain is deleted from Route 53; registry restoration is possible between 45 and 75 days after expiry; and the registry deletes the domain on day 75. Check the expiry date and current official TLD rule for the specific domain rather than applying these dates to other extensions. The page gives day counts, not a domain-specific cutoff time or time zone; do not treat day 75 as a guaranteed full day to act.
A separate case applies when a generic TLD domain is deleted within the first five days after registration: the standard 30-day redemption period does not apply, and someone else may register it immediately. This exception concerns early deletion after registration, not the post-expiry .com timeline. It does not mean every deleted domain has 30 days to recover.
Review the restoration quote and price cap before submitting
Restoration typically costs more than registration or renewal, sometimes much more. Review the price shown in the console before submitting. You can also use GetDomainPrices to retrieve DomainPrice.RestorationPrice for an individual domain, including Currency and Price. A registry prices each premium domain individually, and that price can vary by domain and change over time; do not substitute a standard TLD list price for the actual quote.
AWS credits cannot pay the restoration fee. RestoreDomain accepts a Consent object with Currency and MaxPrice: it is required for premium domains and optional at a standard TLD price. The request fails if the restoration price exceeds MaxPrice. No quote was retrieved for a specific domain here; use the price shown in your account before submitting to confirm the amount and currency.
Submit the request and track its asynchronous operation
After confirming the domain, eligibility, and price, submit the request through the console, CLI, or an SDK. The RestoreDomain API requires the domain to have been registered to the AWS account making the request. An HTTP 200 response with an OperationId does not prove that restoration has completed; use GetOperationDetail to check that operation’s status. The returned ID is not proof of success.
After a successful operation, the domain reappears in the console and in ListDomains. A DuplicateRequest response means a request for that domain is already in progress; check the original operation instead of blindly submitting another request.
After registration is restored, verify DNS and dependent services
Domain registration and DNS configuration are separate. Route 53 can provide DNS for a domain with any TLD and any registrar; its TLD registration list only covers domains that can be registered or transferred to Route 53. If DNS is hosted in Route 53 but registration is held elsewhere, RestoreDomain is not a cross-registrar restoration or transfer tool.
Restoring a registration does not guarantee that a website, email, or application will immediately return to its previous state. After success, check the registration status, name servers, and DNS records separately, then verify the site or mail service that depends on them. If another registrar holds the registration, follow that registrar’s published recovery process. No AWS account was accessed or restoration requested for a real domain here; actual eligibility, pricing and completion time remain unverified.
Sources
- AWS announcement: Route 53 Domains now supports self-service restore for expired or deleted domains
- Route 53 Developer Guide: Restoring an expired or deleted domain
- Route 53 API Reference: RestoreDomain
- Route 53 API Reference: GetDomainPrices
- Route 53 Developer Guide: .com domain deadlines
- Route 53 Developer Guide: Domains you can register and TLD list
Frequently Asked Questions
Will a restored domain keep its original expiration date?
Not necessarily. AWS’s restoration guide says the new expiration date may differ from the old one. After restoration succeeds, read the domain details, confirm the new date and adjust renewal reminders.
Am I charged a restoration fee if the domain can no longer be restored?
AWS’s guide says that when a domain cannot be restored, the request fails and you are not charged. This statement covers a request for an unrestorable domain; it does not establish billing treatment for other services or every failure scenario.