---
title: "Whois & domain expiry check — Lemwatch Help"
description: "Uses RDAP to track domain expiry, auto-renew status, and registrar lock — alerts you 90, 30, 14, and 3 days before expiry."
canonical: "https://lemwatch.com/help/whois-and-domain-expiry-check"
source: "https://lemwatch.com"
---

# Whois & domain expiry check

> Uses RDAP to track domain expiry, auto-renew status, and registrar lock — alerts you 90, 30, 14, and 3 days before expiry.

## Quick answer

 Daily RDAP lookups fetch the expiry date, registrar, and status flags. Lemwatch fires reminders at 90, 30, 14, and 3 days out.

## What it checks

- Expiry timestamp from RDAP

- Registrar of record

- Status flags (clientTransferProhibited, redemptionPeriod, pendingDelete)

- Auto-renew inference from status codes

## Where to find it in Lemwatch

 **Renewals hub** shows every monitored domain with an expiry countdown.

## How to respond

- Confirm auto-renew is enabled at your registrar.

- If expiry is <14 days and status is unknown, renew manually.

- Enable registrar lock to block unauthorised transfers.

- Acknowledge to silence the 90/30/14/3 reminders.

## FAQ

### Why RDAP instead of Whois?

 RDAP is structured JSON, rate-limit-friendly, and returns consistent timestamps.

### What if my TLD doesn't publish expiry?

 Country-code TLDs sometimes hide expiry — Lemwatch marks these "unknown" and skips the countdown.

## Related

- Renewals & SSL management

- DNS NS record check

- SSL monitoring


## Related

- [Help centre](https://lemwatch.com/help)
- [SSL & Domain Renewals](https://lemwatch.com/help/renewals-ssl-management)
- [DNS NS record check](https://lemwatch.com/help/dns-ns-record-check)
- [SSL Certificate Monitoring](https://lemwatch.com/help/ssl-monitoring)
- [SPF record check](https://lemwatch.com/help/spf-record-check)
- [DKIM record check](https://lemwatch.com/help/dkim-record-check)
- [Lemwatch pricing](https://lemwatch.com/pricing)
- [Why am I getting false alerts?](https://lemwatch.com/help/why-am-i-getting-false-alerts)