How to Check When a Route 53 Domain Expires

Domains registered through AWS live in the Route 53 console, slightly apart from the DNS hosted zones people usually associate with the service. Here's how to see when one expires, plus a few Route 53 behaviours that differ from a typical registrar.

Method 1: In the Route 53 console

1. Sign in to the AWS Management Console and open Route 53 at console.aws.amazon.com/route53/.
2. In the navigation pane, choose Registered domains.
3. Choose the name of the domain to open its detail page.

The list of registered domains includes each domain's expiry, and the Route 53 dashboard separately surfaces a list of domains approaching their expiration date — useful as a quick portfolio glance.

To change the registration period, go to the domain's Details section, open the Actions dropdown and choose Renew domain registration. The Renewal period dropdown shows the options available for that TLD, with the resulting expiry date listed under each duration.

Method 2: A public lookup (no AWS login)

Registration expiry is public data, so you don't need console access. Enter the domain into our free domain expiry checker to see the expiry date and the registrar of record — handy for verifying quickly, or checking a domain in an AWS account you don't have access to.

This is also the most reliable cross-check, because it reads the registry's own date rather than any dashboard's interpretation of it. For the full method see how to check when a domain expires.

How Route 53 auto-renewal behaves

Auto-renew is toggled from the domain's Details section → Actions → Turn on auto-renew / Turn off auto-renew.

Several behaviours are specific to Route 53 and worth knowing:

• It's on by default. Domains registered with or transferred into Route 53 have auto-renew enabled unless you turn it off.
• It renews 35 days early for most domains — and 30 days early for .com.ar and .com.br, a registry restriction.
• AWS emails the registrant 45 days before expiry, stating whether auto-renew is on or off. If it's off, ICANN-mandated reminders follow at 30 days and 7 days.
• Your AWS credits can't pay for it. Domain registration, renewal, extension and restoration must be paid by the account's payment method — credits don't apply. This surprises people running otherwise credit-funded accounts.

The bit that isn't obvious: Route 53 isn't one registrar

Route 53 is a reseller front end over two registrars, and which one applies depends on the TLD. Some TLDs are registered through Amazon Registrar, Inc.; others go through Gandi acting as AWS's registrar associate. AWS publishes the per-TLD breakdown in its documentation.

This matters in two practical ways:

• The registrar in a WHOIS lookup won't say "Amazon" for every domain. If you look up one of your own Route 53 domains and see Gandi, nothing is wrong.
• Recovery is slower for the Gandi-backed TLDs. AWS forwards restoration requests to Gandi, which processes them during Paris business hours — AWS's own documentation warns this can take a week or more.

There's also a useful diagnostic in the AWS docs: if you're unsure whether an expired domain is still recoverable, start the extend-registration flow. If the domain still appears in the list, it's within the late-renewal period.

One caution on deadlines: the specific late-renewal, deletion and restoration windows are per-TLD, published in AWS's registrar TLD list, not a single universal rule. And a restored domain gets a new expiry calculated from the old expiry date, not the restore date.

Don't rely on a single console

If every domain you own is in one AWS account, the Registered domains page covers you — provided someone looks at it. In practice domains scatter: a client's domain at their host, an old project at a different registrar, a marketing domain someone bought on a company card. No single dashboard shows all of them, and the one that lapses is always the one nobody owns.

The dependable approach is monitoring expiry independently of the registrar — one place that tracks every domain wherever it lives and emails you weeks ahead, so a failed payment or an email nobody read still reaches you in time. That's what DomainChest does. See also why auto-renew fails and why registrar renewal reminders aren't enough.