Need help escalating a Case - domain renewal

Hi there,

I understand you need help with a domain renewal issue before the domain expires on June 16. To prevent any confusion or further delays, refrain from creating additional support cases. I've reached out to our Support team regarding your urgent request. Continue to monitor our Support Center for an update: http://go.aws/support-center.

- Kita B.

Sorry to hear about the stress with the June 16 expiration.

The detail you mentioned — "a system-generated notification requesting additional information to keep the domain active" is the key, and the good news is you can almost certainly fix this yourself right now without waiting for the case to be assigned.

That notification is the ICANN registrant-contact verification email. For domain registrations, ICANN requires the registrar to confirm the registrant contact's email address is valid. You have 3–15 days to click the link in that email; if it's missed, ICANN requires the domain to be suspended, and it can also block the renewal from completing. That lines up exactly with what you're seeing.

Resolve it directly in the Route 53 console:

1. Check/correct the registrant contact email first. Route 53 console → Registered domains → select your domain → confirm the registrant contact email is one you can actually receive mail at. Update it if needed.
2. Resend the verification email. On the same domain detail page, look for the warning box titled "Your domain might be suspended" and choose Send email again. (If that box isn't there, the email was already confirmed.)
3. Click the link in the email. It comes from one of: noreply@registrar.amazon, noreply@domainnameverification.net, or noreply@emailverification.info. Check your spam folder — these are easy to miss. The link may point to www.registrar.amazon, which is safe.

Two more things to check so the renewal actually goes through:

• Valid payment method. Renewal fees cannot be paid with AWS credits. Billing console → Payment preferences → make sure a valid (non-expired) card is on file. A failed payment is the other common reason auto-renew fails.
• Don't wait on auto-renew given the June 16 date. You can proactively extend now: Route 53 console → Registered domains → select the domain → Renew/Extend the registration period. This locks in the renewal immediately rather than relying on the auto-renew cycle. Also confirm automatic renewal is enabled on the domain.

If June 16 slips past: don't panic — for most generic TLDs there's a late-renewal window after expiration (commonly up to ~44 days, varies by TLD) during which you can still renew at the standard price, plus a registry restoration period after that. So the domain is recoverable even if it briefly lapses. You can check by trying the Renew/Extend flow — if the domain is still listed, it's within the late-renewal window.

Reference docs:

• Resending the verification/confirmation email: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-click-email-link.html
• Renewing a domain: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-renew.html
• Extending the registration period: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-extend.html

Note: domain-registration support is free for all customers regardless of support plan, but the steps above will most likely resolve it faster than waiting on case assignment.

Hope this saves your domain!

Thank you 'AWS Support - Kita' - the case has been assigned now and they are looking into it. Thanks also to Steven and Florian Turnwald for taking the time to reply, it is much appreciated.

Best Regards,