Domain expiration monitoring: catch renewals before they are due

Track domain renewal deadlines with RDAP and registrar records. Separate registration expiry from DNS and TLS checks, and alert on missing data.

Best practices
Illustration of a monitoring platform with connected services

The website responds, DNS returns the expected records, and the TLS certificate has months left. The registrar still says the domain must be renewed in 14 days. Each check is telling you something different. Domain expiration monitoring tracks the registration deadline and gives its owner time to renew.

Start with the date the owner has to act on

Build the inventory around registered domains. Several applications may use subdomains of the same registration. For each domain, record the registrar, the person responsible for renewal, and the systems that rely on it. Keep an escalation contact that can be reached even if mail on the monitored domain stops working.

For generic top-level domains (gTLDs), RDAP became the definitive source for public registration data in place of sunsetted WHOIS services on January 28, 2025. Use the ICANN Lookup service for manual checks. An automated job can read IANA's RDAP bootstrap registry, find the service for the matching suffix, and append the domain/{name} query to the service's base URL. If there is no usable service or expiry data for a country-code top-level domain (ccTLD), use that registry's documented lookup or the registrar's account records. ICANN's RDAP transition notice · RFC 9224 The WHOIS requirement ended for most gTLDs, with exceptions for .com, .name and .post. ICANN registry guidance

Keep the registry and registrar dates separate

In a gTLD RDAP response, read the top-level domain object's events array. The registry expiry is represented by expiration, and the registrar's registration expiration by registrar expiration. A single response may not contain both. The dates can differ when the registry has automatically extended the registration but the customer has yet to renew with the registrar. Check the registrar's renewal deadline and account confirmation before closing an alert. RDAP response format · ICANN guidance on the two dates

For example, imagine a comparison view that combines two events collected from the relevant sources. The following dates are synthetic.

{
  "events": [
    {"eventAction": "expiration", "eventDate": "2027-12-01T00:00:00Z"},
    {"eventAction": "registrar expiration", "eventDate": "2026-12-01T00:00:00Z"}
  ]
}

At 2026-11-17T00:00:00Z, the registrar event is 14 days away. Taking the later date would hide the immediate renewal risk. Parse the timestamps with their offsets, compare them in UTC, and retain the event type and source so the person investigating can see where the number came from. If a date is missing or ambiguous, mark the observation as unknown and follow up with the registrar.

Page for approaching expiry and missing data separately

A daily check is a reasonable starting point for a deadline measured in days. Set the frequency against the service's limits and use backoff when it returns HTTP 429. A timeout or malformed response leaves the current expiry unknown. Keep the last confirmed date and its observation time, and use a separate freshness rule so an old value cannot silently keep the monitor green.

Time before the confirmed deadline What to do
60 days Open a ticket and confirm the owner and renewal plan
30 days Notify the owner and verify auto-renewal and the payment method
14 days Escalate through the agreed channel and confirm the renewal result

These are example thresholds. Apply the organization's renewal lead time and confirm the date after the transaction completes. Account transfer locks protect against some unauthorized transfers. They do not complete a renewal.

Use live checks to tell which dependency failed

Registration, DNS and TLS need separate signals. A valid registration cannot tell you whether a resolver returns the right records. A healthy DNS result cannot tell you when the site's certificate expires. Keep an independent certificate check and an uptime check for the live service. Guance's SSL synthetic test can track the certificate served by an endpoint, including its remaining validity. The registrar check still owns the domain renewal deadline.

Treat recovery as a separate workflow

An expired domain does not become available for someone else to register at once. Renewal windows, fees and DNS interruption depend on the applicable policy and registrar. Under ICANN's policy, the 30-day Redemption Grace Period for eligible gTLD registrations follows deletion. During that period, DNS resolution is disabled and restoration goes through the registrar. If another party has already registered the name, this recovery process is no longer available. Check the registrar's terms before you need to use them. ICANN Expired Registration Recovery Policy

Get a tailored plan

Contact us

Join the community

Scan with WeChat
to join the community

Try Guance

Start online and pay only for what you use.

Get started

Choose a Guance plan

Code hosting