Domain expiry monitoring for the domains you're responsible for
An expired domain takes everything with it: the website, the email on that domain, and any service that depends on its DNS. Unlike a certificate, a domain doesn't renew itself just because a server is configured well. Someone has to pay for it, from the right registrar account, with a card that still works.
Domainvane watches the registration expiry date of each domain you add, alongside its TLS certificate, and flags it before it lapses.
Start free with 3 domains. No card required.
Why domain renewals still get missed
Auto-renew is meant to solve this, and usually does. It fails quietly in a few familiar ways:
- The card on the registrar account expired or was replaced.
- The domain sits in an account nobody logs into anymore: a client's, a previous agency's, or a freelancer's who moved on.
- Renewal notices go to an old address that nobody reads.
None of those show up on the website until the day it stops resolving. For more on this, see why Let's Encrypt and registrar auto-renew fail quietly and what happens when a domain name expires.
Where the date comes from: RDAP
Domainvane reads domain-registration expiry from RDAP, the Registration Data Access Protocol. RDAP is the structured, HTTPS-based replacement for WHOIS. ICANN made it the definitive source for generic top-level domain (gTLD) registration data on 28 January 2025, when the WHOIS requirement was sunset for most gTLDs.
What that means in practice:
- A date, with its source. When RDAP returns an expiration event, Domainvane stores the date and whether it came from the registry or the registrar. Those two can disagree, and either can differ from the renewal date on your registrar's billing screen, so the source is shown.
- Unknown means unknown. Common gTLDs that publish HTTPS RDAP are in scope. If a TLD has no usable RDAP service, or the record has no usable expiry, the result is unknown. There is no WHOIS fallback and no guessed date.
- Errors are kept separate. A timeout, a rate limit, or a malformed response is stored as an error, not as a date.
How monitoring works
- Add your hostnames. Paste a list separated by newlines, commas, or spaces. See bulk-adding domains.
- Checks run about every 24 hours. Each check looks up the RDAP expiry and reads the TLS certificate on port 443. When something is 7 days or fewer from expiry, or a check is failing, the next check comes sooner, about 6 hours later.
- Alerts at 30, 14, 7, and 1 days before the registration expires, and after 3 consecutive failed checks. Alerts show on the dashboard and go out by email on every plan. Email alerts are delivered to external inboxes, including Gmail; inbox placement is not guaranteed for every provider (Outlook and Yahoo have not been tested).
- Renew at your registrar. Domainvane is a reminder and a status, not a renewal service.
Two dates, one dashboard
A domain registration and a TLS certificate expire on different dates, renew through different companies, and fail differently. Watching only one of them leaves a gap. Domainvane shows both for each hostname on the same dashboard. See domain expiry vs SSL expiry for how they differ.
What it doesn't do
- It doesn't renew or register domains, and it doesn't hold or transfer them.
- It doesn't use WHOIS, so a TLD without usable RDAP shows unknown.
- It doesn't watch domains you don't own for drops or backorders.
- It isn't an uptime monitor.
Plans
| Plan | Price | Domains |
|---|---|---|
| Free | $0 | 3 |
| Solo | $9/mo | 25 |
| Agency | $29/mo | 150 |
| Agency+ | $79/mo | 750 |
Every plan includes the same checks, alert thresholds, and email alerts. See all plans.
Want to look at a certificate first? The free SSL certificate checker checks one hostname on port 443 and doesn't store it. Managing client domains? See monitoring for agencies.
Start free with 3 domains.