Domain expiry monitoring for every domain you own

Auto-renew fails more often than teams expect

Renewal depends on a payment method, a contact address and a registrar account that all still work. Expired cards, changed billing owners, unverified registrant email under ICANN rules and transfers left half-finished all break auto-renew quietly. The registrar notice usually goes to a mailbox nobody reads.

• After expiry a domain enters a grace period, then redemption, where recovery carries a significant fee.
• Some ccTLDs delete faster and with fewer notices than gTLDs.
• Losing the domain also means losing DNS, which breaks mail delivery and SSO at the same moment.

RDAP first, WHOIS where needed

RDAP is the modern, structured replacement for WHOIS and returns machine-readable JSON, but coverage varies by registry. ServerInspector queries RDAP where available and falls back to a direct WHOIS query on TCP port 43 for registries that have not migrated, which is how .rs and several other European ccTLDs are supported.

• Structured expiry dates instead of scraped text where RDAP exists.
• Registry-specific WHOIS parsing for ccTLDs with non-standard output.
• Errors are surfaced per domain instead of silently showing no date.

Domains and monitors stay in sync

When you create a monitor, its root domain is tracked automatically, so nothing is forgotten. You can also add domains directly — parked domains, brand defensives, mail-only domains — without creating an uptime monitor for them.

Reminders that reach the person who can pay

Each domain can notify its own address on its own schedule, so billing gets the renewal notice and engineering gets the technical alerts. A weekly digest lists everything sorted by expiry so the next deadline is always visible.