# Domain expiration monitoring: a practical renewal checklist By Track.Name Canonical URL: https://staging.track.name/blog/domain-expiration-monitoring Domain expiration monitoring follows published registration dates and status changes so you can review an approaching renewal. For a domain you own, pair those observations with the registrar account, a named renewal owner and a verified payment method. Complete the renewal through the registrar and confirm its result; a reminder is not proof of payment. ## Create one renewal record for each domain Start with the domains your organisation depends on, including names used for email, customer accounts and redirects. A domain that has no public homepage can still belong in the renewal inventory. Ask each team which names their services use, then compare the answers with the registrar accounts you control. For each domain, record the registrar, account owner, renewal decision-maker, observed expiration date, internal review date and business purpose. Link to the approved location of account access details; do not put passwords or recovery codes into a shared spreadsheet. Include a backup person who can act when the primary owner is away. Make the record useful to someone outside the technical team. 'Customer sign-in and password-reset email' explains why a name matters more clearly than 'production domain'. An old campaign redirect may deserve a different review than a primary email domain. Keep intentional non-renewals in the inventory until the responsible person confirms the decision and dependent services have been reviewed. Removing a name from a list should not accidentally become permission to let it lapse. ## Check the registrar as well as the public expiry date A public registration lookup is a useful independent observation. The registrar account is where you confirm your own renewal settings and account-specific instructions. Put the two sources side by side when you investigate a discrepancy, and record which date each one labels as expiration or renewal. ICANN recommends tracking the expiration date, keeping payment and contact information current, and checking the registrar's renewal terms. Its [renewal and expiration FAQ](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en) also explains that renewal options and fees vary by registrar. Avoid combining registration expiry, certificate expiry and a hosting invoice into one 'website renewal' date. They are separate things to verify, with separate records and people who may be responsible for them. The [certificate monitoring guide](/blog/ssl-certificate-monitoring) explains the HTTPS side of that distinction. When two sources disagree, retain both observations and ask the registrar to explain the account's current state. Do not silently replace the earlier value or assume the later date proves that your payment succeeded. ## Turn renewal reminders into assigned work A reminder needs an owner, a decision and enough time to resolve an account problem. Choose internal review dates that allow for your purchasing process, approval requirements and staff availability. Make your review earlier if access depends on a former contractor or an account you have not used recently. For generic top-level domains, ICANN's [Expired Registration Recovery Policy](https://www.icann.org/en/contracted-parties/consensus-policies/expired-registration-recovery-policy/expired-registration-recovery-policy-21-02-2024-en) sets minimum registrar renewal-notice requirements before expiry. Treat those notices as one input to your process. Your internal ownership and approval workflow still needs to function when an email is missed or reaches the wrong person. A practical reminder should include: - The exact domain and what depends on it. - The source and time of the observed expiry date. - The person responsible for confirming renewal. - The internal due date and next escalation contact. - A place to record the result and supporting evidence. Keep the status precise: awaiting review, approved, renewal requested or renewal confirmed. 'Email sent' describes a notification, not a completed renewal. ## Review auto-renew and account access before they are needed Use auto-renew where it fits your registrar setup, then verify the surrounding details. ICANN's [renewal guidance](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en) specifically recommends keeping payment information current when using auto-renew. Your review should also establish who can resolve a failed payment or an access problem. Run this checklist from the registrar account through your usual trusted access route: 1. Confirm that the correct domain appears in the correct account. 2. Review its auto-renew setting and the registrar's displayed timing. 3. Check the authorised payment method and billing contact. 4. Confirm that the responsible people can sign in and use the required authentication method. 5. Review who receives renewal and account-security messages. 6. Record the review date and any unresolved action. Do not change a setting merely to make the checklist look complete. For a domain deliberately scheduled to expire, preserve the written decision and verify the dependencies first. For a domain that must stay registered, an unresolved access issue deserves escalation while there is still time to fix it. ## Confirm the renewal and keep the evidence After requesting a renewal, check the registrar's result rather than closing the task at the payment screen. Save the confirmation or transaction reference and the new date shown in the account. Repeat the public registration lookup later and note the observation time. If the public record has not changed, retain that uncertainty and follow up with the registrar. A useful completion note is specific: who checked the account, what the registrar confirmed, which date is now shown and whether the external observation agrees. Avoid a single untimestamped 'done' label that nobody can investigate next year. Review the linked services separately if the domain had already stopped working. A successful account transaction should not be used as the sole evidence that the website, email and DNS are all behaving as intended. Check each service you listed in the inventory, and route unresolved technical symptoms to its owner. Finally, set the next internal review. Keep the earlier record so a future change in ownership, registrar or renewal date has a clear history. ## If a domain has expired, establish its current state For your own domain, contact the registrar promptly through a verified channel. Gather the domain, account identifier, visible status, payment history and previous renewal messages. Ask what action is available for that registration now, what it costs and how you will know it has completed. Do not calculate a universal recovery deadline from a blog post. Under ICANN's policy, covered gTLD registrations can have a redemption process after deletion; that is not the same event as the original expiration date. Check the applicable registrar and registry rules, especially for country-code domains. The [policy's scope and redemption provisions](https://www.icann.org/en/contracted-parties/consensus-policies/expired-registration-recovery-policy/expired-registration-recovery-policy-21-02-2024-en) matter more than a generic countdown. If you are observing somebody else's domain, keep that workflow separate. You cannot complete its owner's renewal review, and the public expiry date does not tell you when you can register it. Follow the [taken-domain monitoring workflow](/blog/taken-domain-monitoring) to record changes without assuming an outcome. ## Example: a startup changes its renewal owner Imagine a startup whose domain reminders still go to the person who originally built its website. The finance team has a payment card on file, but nobody has confirmed who can access the registrar account. This is a hypothetical handover problem, not a reported customer incident. During a scheduled review, the team assigns a current owner and backup, confirms access, checks the billing contact and records the registrar's renewal settings. It lists the website and company email as dependencies, then sets a separate date for confirming the renewal result. The improvement is measurable without inventing an outage avoided: the team now has an accountable person, accessible account and documented verification step. Use that as the completion standard for a portfolio review. Every domain should have either a confirmed renewal process or an explicit decision to retire it. ## Frequently asked questions ### Is auto-renew enough to protect a domain? Auto-renew is useful, but review payment details, account access and renewal messages as well. Assign someone to confirm the completed renewal rather than treating an enabled setting as proof that it will succeed. ### Where should I check my domain expiration date? Check your registrar account and compare it with a current registration lookup. Record the source, date label and observation time. Ask the registrar to explain any discrepancy affecting a domain you own. ### Does monitoring renew my domain for me? Monitoring records information and can support reminders; renewal is a separate registrar action. Confirm the renewal in the account responsible for the registration and keep evidence of the result. ## Sources - [ICANN domain renewal and expiration FAQ](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en) - [ICANN Expired Registration Recovery Policy](https://www.icann.org/en/contracted-parties/consensus-policies/expired-registration-recovery-policy/expired-registration-recovery-policy-21-02-2024-en)