AWS Route 53 Domains Self-Service Restore (November 2026): What Startups Need to Know
Our recommendation: use self-service restore for an eligible expired or recently deleted Route 53 domain after confirming the registry's restoration window and reviewing the restoration price.
Affected: This applies to expired or recently deleted domains in Amazon Route 53 Domains.
What did the vendor release?
On 12 November 2026, AWS announced self-service restore for Amazon Route 53 Domains.
You can restore an expired or recently deleted domain through the Amazon Route 53 console, AWS CLI or AWS SDKs. Previously, restoring a domain required a request to AWS Support.
To restore a domain, enter its name, review the restoration price, accept the charge and submit the request. Route 53 works with the TLD registry to reactivate the registration and return the domain to your AWS account.
Which startups are affected?
The release covers recovery after a missed renewal, an expired payment method or an accidental deletion. AWS says you can restore the website, email and applications that depend on the domain.
Our recommendation: add this recovery path to your runbook if your startup registers domains through Route 53 Domains. Name the person responsible for checking restoration eligibility and the person who can approve the charge.
Our recommendation: list the websites, email services and applications you would check after a domain is returned to your account. Use that list as your recovery checklist.
Adopt it or keep the existing approach?
Our recommendation: use the self-service process for an eligible expired or recently deleted domain after confirming the registry window and reviewing the price. Update any recovery instructions that begin by requesting restoration from AWS Support.
Restoring a domain typically costs more than registering or renewing one.
Our recommendation: keep renewal and payment checks in your operating routine. Treat restoration as a recovery option and review the quoted charge before committing to a request.
Our recommendation: choose the console, CLI or SDK route your team is prepared to operate. Assign an owner for the request and record which domain is being restored, who approved the charge and what was submitted.
Our recommendation: do not promise a recovery time based on this announcement. Confirm the available restoration path before giving colleagues or customers a recovery estimate.
What to check before enabling it?
Most TLD registries support restoration, and each registry sets how long after expiration or deletion a domain can still be restored.
Our recommendation: confirm your TLD is on the supported list before you rely on restore in a runbook.
- Our recommendation: check the relevant registry's restoration window before submitting a request. Record the applicable deadline in the recovery notes.
- Our recommendation: verify the exact domain name before accepting a charge. Have the request owner compare it with the domain recorded in your runbook.
- Our recommendation: review the displayed restoration price and agree who can approve it. Keep that approval with the recovery record.
- Our recommendation: document which console, CLI or SDK workflow your team will use. Have another team member review the written steps before submitting the request.
- Our recommendation: after the registration returns to your account, check each dependent website, email service and application. Record the result before marking the incident resolved.
Our recommendation: review why the domain was lost after recovery. Consider adding a renewal reminder, a payment-method review or a clearer deletion approval step to your runbook.
Sources
- Amazon Route 53 Domains now supports self-service restore for expired and deleted domains (Amazon Web Services, 12 Nov 2026). Primary source.