Domain Expiry Monitoring: Why RDAP Beats WHOIS

Published 22 July 2026 · 5-minute read

Of all the ways a website can go dark, a lapsed domain registration is the scariest — because it's one of the few that can be genuinely unrecoverable. Once a domain drops and someone else registers it, no amount of ops heroics gets it back.

Domain expiry is not the same as SSL expiry

It's easy to conflate the two, but they're different clocks:

• SSL/TLS certificate expiry is about the certificate the server presents. It renews every 90 days (for Let's Encrypt) and a lapse shows a browser warning.
• Domain expiry is about your registration at the registrar. It renews yearly (or multi-year), and a lapse means the domain stops resolving entirely — then enters redemption, then becomes available for anyone to grab.

You need to watch both, but domain expiry has the higher blast radius, because the failure mode is permanent.

How domain-expiry monitoring works

The registration's expiry date is public data published by the registry. A monitor looks it up on a schedule, reads the expiry date, and warns you with enough lead time to renew. The only real question is how it looks that data up — and that's where RDAP and WHOIS differ.

WHOIS: the old way

WHOIS has been around since the 1980s. It works, but it's showing its age:

• Unstructured text. Every registry formats its response differently, so parsing the expiry date reliably across hundreds of TLDs is a constant game of whack-a-mole.
• Rate limiting and redaction. Post-GDPR, many WHOIS responses are heavily redacted or throttled.
• No standard transport. It's a plain-text protocol on port 43 with no real structure or versioning.

RDAP: the modern replacement

RDAP (Registration Data Access Protocol) is the IETF's structured successor to WHOIS, and it's now mandated for gTLDs:

• Structured JSON. The expiry date comes back as a machine-readable field, not buried in free text — so it parses reliably across TLDs.
• Standard HTTP. Predictable, cacheable, versioned, and easy to query securely.
• Consistent across registries. The same client works everywhere RDAP is supported, which is increasingly everywhere.

The practical upshot: RDAP-based monitoring is far less likely to silently break on some obscure TLD, and it doesn't need registrar-specific integrations.

The registrar-agnostic approach

Some monitoring tools ask you to connect each registrar's API individually. That's brittle — every registrar you add is another integration to maintain, and it can't cover a registrar it doesn't support. Querying the registry directly via RDAP (with a WHOIS fallback for TLDs that don't yet support it) works for any domain at any registrar, with nothing to connect.

That's the approach UpWatch Robot takes: point it at a URL and it derives the registrable domain, looks up expiry via RDAP with a WHOIS fallback, and warns you well before the registration lapses — whoever the domain is registered with.

Frequently asked questions

What is the difference between domain expiry and SSL expiry?

SSL expiry is about the TLS certificate the server presents (renews roughly every 90 days; a lapse shows a browser warning). Domain expiry is about your registration at the registrar (renews yearly; a lapse stops the domain resolving entirely and can become permanent once the domain is released). Both need monitoring, but domain expiry has the higher stakes.

Is RDAP better than WHOIS for monitoring domain expiry?

Yes, in most cases. RDAP returns structured JSON over standard HTTP, so the expiry date parses reliably and consistently across TLDs, whereas WHOIS is unstructured free text that's formatted differently by every registry and is increasingly rate-limited and redacted. A good monitor uses RDAP with a WHOIS fallback for TLDs that don't yet support it.

Do I need to connect my registrar to monitor domain expiry?

No. Registrar-specific integrations are brittle and can't cover registrars they don't support. Querying the registry directly via RDAP/WHOIS is registrar-agnostic — it works for any domain at any registrar with nothing to connect.