All resources
Domain Monitoring

Domain and Hosting Renewal Checklist for Agencies

A domain and hosting renewal checklist for agencies covering registrar ownership, billing contacts, auto-renew, DNS dependencies, email dependencies, and escalation.

Updated 5 May 2026

See exactly where your client domains stand.

Run a free audit on up to 10 domains — SSL expiry, domain expiry, and DNS health in one report. No signup needed.

Domains and hosting are the two most operationally critical assets a web agency manages for clients. When either lapses, the result is usually immediate — the site goes down, email stops working, or DNS stops resolving. Despite this, missed renewals remain one of the most common preventable incidents in agency operations.

This checklist covers what to verify before a domain or hosting renewal, during the transition, and after renewal is confirmed. It is designed for agency account managers and operations leads who manage renewals across multiple clients.

Before You Begin: What a Domain and Hosting Renewal Checklist Covers

A domain renewal and a hosting renewal are separate events, often with separate owners, separate billing contacts, and separate consequences if missed.

  • Domain renewal is managed at the registrar. A lapsed domain becomes available for third-party registration, potentially losing email, website access, and brand identity simultaneously.
  • Hosting renewal is managed at the hosting provider. A lapsed hosting account may suspend the site, delete files depending on the provider's grace period policy, or disrupt services that depend on the hosting environment.

Treat them as separate checklists even when a client holds both through the same provider.


Domain Renewal Checklist

1. Confirm registrar and account ownership

  • [ ] Identify the registrar (Namecheap, GoDaddy, Google Domains / Squarespace, Cloudflare Registrar, etc.)
  • [ ] Confirm which account holds the domain — agency account or client account
  • [ ] If agency account: confirm the billing contact is active and monitored
  • [ ] If client account: confirm the client has received renewal reminders and can action them

2. Verify the renewal date

  • [ ] Log in to the registrar or query RDAP/WHOIS for the confirmed expiry date
  • [ ] Cross-check against your renewal tracking record — dates drift when transfers occur
  • [ ] Note whether the domain is within a 60-day, 30-day, or 14-day warning threshold

Use CertPilot's free 10-domain audit to check domain expiry dates across multiple client domains in one run without logging in to each registrar. The single domain health check is useful for a quick per-domain check.

Related reading: Domain Expiry Monitoring for Agencies

3. Check auto-renew status

  • [ ] Log in to the registrar and confirm auto-renew is enabled
  • [ ] Confirm the payment method attached to auto-renew is current (unexpired card, active account)
  • [ ] If auto-renew is disabled: set a manual renewal task with a 14-day lead time
  • [ ] Note any registrar-specific grace period or redemption period in case of accidental lapse

4. Verify the registrant and administrative contact emails

  • [ ] WHOIS or registrar panel shows the registrant email — confirm it is a monitored inbox
  • [ ] Check that the admin contact email routes to someone who can action renewal reminders
  • [ ] If the registrant email is a former employee address or personal email, update it now

This is one of the most common causes of missed domain renewals. Renewal emails go to an address no one monitors, auto-renew fails on an expired card, and the domain lapses with no one aware.

5. Identify DNS dependencies

  • [ ] List all DNS records that would break if the domain expired: A records, MX records, CNAME records for CDN or email
  • [ ] Note whether email is routed through this domain (MX records pointing to Google Workspace, Microsoft 365, etc.)
  • [ ] Note whether any subdomains support active services

Related reading: DNS Drift Agency Guide

6. Check for domain transfer locks

  • [ ] Confirm the domain has a transfer lock enabled (prevents unauthorised transfers)
  • [ ] Note the unlock procedure in case the client ever needs to move registrars

7. Notify the client if relevant

  • [ ] If the domain is client-owned and billed to the client: send a renewal reminder at least 30 days before expiry
  • [ ] Include: domain name, current expiry date, registrar, action required, and who to contact with questions
  • [ ] Document the notification in your care plan or CRM

Hosting Renewal Checklist

1. Confirm hosting provider and account

  • [ ] Identify the hosting provider (WP Engine, Kinsta, SiteGround, Cloudways, Flywheel, etc.)
  • [ ] Confirm account ownership — agency account or client account
  • [ ] Note the billing contact and payment method on file

2. Verify the renewal date and billing cycle

  • [ ] Log in to the hosting panel or billing section for the confirmed renewal date
  • [ ] Note whether billing is monthly, annual, or biennial
  • [ ] Annual and biennial renewals require more lead time — ensure a 60-day review is scheduled

3. Confirm what is hosted in this account

  • [ ] List all sites or subdomains hosted in this account
  • [ ] Note any staging environments, email accounts, or databases that depend on this hosting
  • [ ] Identify whether SSL certificates are provisioned through this host (and what happens to them on non-renewal)

4. Verify auto-renewal and payment method

  • [ ] Confirm auto-renew is enabled in the hosting panel
  • [ ] Verify the payment method is current
  • [ ] Some providers send renewal invoices rather than auto-charging — confirm which applies

5. Check server and plan health

  • [ ] Confirm the hosting plan is appropriate for current site size and traffic (relevant if the client has grown significantly)
  • [ ] Note any pending plan changes, resource upgrades, or migrations that would affect the renewal

6. Confirm DNS is not dependent on this host

  • [ ] If the domain's DNS is hosted by the same provider as the website, a hosting lapse could affect DNS resolution as well
  • [ ] Note whether DNS is managed separately (Cloudflare, Route 53, registrar) or through the hosting panel

7. Check for recent hosting issues

  • [ ] Review any support tickets, downtime events, or performance issues in the past quarter
  • [ ] If the hosting relationship is problematic, note this before auto-renewing — a renewal is a decision point, not just an automatic event

After Renewal: Verification Checklist

Once a domain or hosting renewal has processed:

  • [ ] Confirm the new expiry date is visible in the registrar or hosting panel
  • [ ] Update your renewal tracking record with the new expiry date
  • [ ] Verify that SSL certificates are still valid and cover the correct domains — some renewal or migration events affect certificate provisioning

Run a quick check using CertPilot's single domain health check or the free 10-domain audit after a domain or hosting renewal to confirm SSL, DNS, and registration status all look correct.


Annual Domain and Hosting Audit Checklist

In addition to per-renewal checks, agencies should run a full audit of all client domain and hosting assets at least once per year.

| Check | Frequency | Tool | |---|---|---| | Domain expiry dates across all clients | Annual + monthly monitoring | Free audit | | SSL certificate validity and expiry | Monthly monitoring | Domain health check | | DNS record snapshot for drift detection | Continuous | CertPilot monitoring | | Registrant email addresses | Annual | Registrar panel | | Auto-renew and payment method status | Annual | Registrar/hosting panel | | Hosting plan suitability review | Annual | Hosting panel |

Related reading: Domain Renewal Checklist for Agencies | Client Domain About to Expire


Common Causes of Missed Domain and Hosting Renewals

Understanding why renewals are missed helps prevent them:

| Root cause | Prevention | |---|---| | Renewal email sent to unmonitored address | Update registrant/admin email at onboarding and annually | | Payment card expired | Audit payment methods on file 60 days before renewal | | Auto-renew disabled after a transfer | Verify auto-renew status after every domain transfer | | Domain transferred to new registrar, expiry date reset | Re-verify expiry date in new registrar immediately after transfer | | Shared hosting account deleted after client offboarding | Migrate DNS and SSL before removing hosting access | | No one knew who owned the billing account | Document account ownership at onboarding |


Frequently Asked Questions

How far in advance should agencies check domain and hosting renewals?

Start reviewing at 60 days before expiry. This gives time to verify payment methods, update contact emails, handle any transfer issues, and notify the client without rushing. A 14-day review is the last practical point for most registrars; by then, options may be limited.

What happens if a client domain expires?

After expiry, most registrars enter a grace period (typically 0–30 days) during which the domain can be renewed at the standard price. After the grace period, the domain enters a redemption period (typically 30–60 days) where recovery costs significantly more. After redemption, the domain becomes available for anyone to register. The specific timelines vary by registrar and domain TLD.

Does auto-renew protect against domain expiry?

Auto-renew reduces the risk but does not eliminate it. Common failure modes: the payment method on file expires; the billing email receives a failed-payment notice that no one monitors; or auto-renew was disabled when the domain was transferred without being re-enabled.

Should the agency or the client own the domain registrar account?

Both models exist. Agency-owned accounts give the agency more control over renewal timing, but create an operational dependency that complicates client offboarding. Client-owned accounts reduce this risk but require the agency to have access to renewal notifications, either through a shared inbox or a secondary contact address.

How does hosting renewal differ from domain renewal?

Domain renewal is managed at the registrar and affects DNS resolution and ownership. Hosting renewal is managed at the hosting provider and affects the server environment where the site runs. A domain renewal failure takes the domain name offline. A hosting renewal failure takes the site's files, database, and services offline. Both are critical but require separate tracking.

Monitor every client domain from one dashboard.

CertPilot checks SSL expiry, DNS records, and domain registration daily — then sends one alert when action is needed. 14-day free trial, no card required.