The domain wasn't renewed — and the site vanished: how to watch the registration date

July 2, 2026 · 7 min read

There's a failure that sounds almost comical — until it happens to your client: "The domain expired." Not an attack, not a data-center outage, not a bug in the code. The domain registration simply ran out — and the site vanished along with email, ads, and leads. The most maddening part is that it looks dumb, and that's exactly why the client is angrier. Let's break down why domains don't get renewed, how to check in time when one expires, and how to put the date under watch.

The domain often belongs to "nobody"

Formally, a domain has an owner. In reality there's fog around it. The site was built long ago by the first agency, the domain was registered by the founder, then access was handed to a marketer, the marketer quit, renewal notices go to an old inbox, accounting pays for hosting but not the domain. The new contractor thinks the client owns the domain. The client thinks the contractor owns everything.

For years this bothers no one — until the registration runs out. Then the hunt begins: who has access, which registrar, which email it's all tied to, who was supposed to pay, why nobody warned. But the client isn't interested in the archaeology of logins. Their site is down, and they'll be sorting it out by way of a complaint to you.

Why a domain is more than an address

People treat a domain like a signboard. For a business it's a piece of infrastructure holding up far more than "a page on the internet":

• the site itself and every familiar link to it;
• often the company email on that same domain;
• ad campaigns pointing at a live address;
• SEO history and links in decks, social profiles, maps, newsletters.

If the domain drops, the flow of leads stops, email quits working, sales reps can't send a proposal from a proper address. And all of it — over one date that got forgotten.

Checking a domain's expiry is boring — which is why it gets forgotten

Nobody wakes up thinking "I should check when the client's domain expires." It's a dull admin task, which means it can't live in your head — it will inevitably fall out. Looking up the date once is easy: a domain's registration is stored in the registry and available over the RDAP and WHOIS protocols, shown by public services and your registrar's panel. But a one-off check guarantees nothing.

If an agency supports a site, the domain's expiry should be in a monitoring system. Not in a spreadsheet someone will open "someday." Not in a two-year-old email thread. In a system — with warnings ahead of time and a clear owner: who renews, who pays, who has access.

Who should be responsible for the domain

An agency isn't always obligated to pay for a client's domain. But if you sell support, you're obligated to clarify the boundaries — otherwise you'll be the one left holding the bag when the site disappears. A reasonable minimum worth pinning down at the very start:

• where the domain is registered and who owns it;
• who has access to the registrar's panel;
• which email gets the renewal notices;
• who pays for the domain renewal;
• how many days ahead the alarm goes off;
• what we do if the client doesn't respond.

This isn't bureaucracy — it's a way to avoid being blamed for someone else's forgetfulness. Otherwise the conversation is short: "Why didn't you warn us?" And the line "that wasn't in our scope" is legally correct but commercially useless — the client still leaves angry.

How far ahead to warn the client

A single last-minute notice is bad practice: the client may lack the money, access, or time on that exact day. Stages are smarter — say, 30, 14, 7, and 3 days before expiry. That leaves room to approve a budget, track down registrar access, and pay, even if the client is slow to react. The key is that the first signal arrives weeks ahead, not days: renewing a domain is a calm procedure right up until two days are left.

How to show this work to the client

Domain oversight is nearly invisible: if it's renewed, nothing happens. So it needs to be shown. In a client report it reads convincingly: "The domain client.com is under watch, 82 days to expiry." Or, when it kicks in: "There were 9 days to expiry, we warned the client, renewal is done, no downtime."

Boring prevention turns into visible work — and into an argument for why a retainer is worth its price.

The domain is one date in the bigger picture

Pingvera checks domain expiry alongside the other things that get an agency unpleasant phone calls: availability, SSL, forms, signs of a hack, WordPress, and server metrics. For an agency this is convenient: the whole fleet of client sites in one dashboard, instead of domains in one spreadsheet, SSL in another, availability in a third.

A domain is a small date. But sometimes it's exactly the one that decides whether the client sees your support as peace of mind or expensive air.

Frequently asked questions

How do I check when a domain expires?

A domain's registration date is stored in the registry and available over the RDAP and WHOIS protocols — that's where the expiry date lives. You can look it up once through a WHOIS service or your registrar's panel. But a one-off check guarantees nothing: what matters is putting the date under continuous watch. Pingvera checks domain expiry via RDAP and WHOIS and warns you well ahead — weeks, not days, before it lapses.

Who's responsible for renewing a client's domain?

There's no single rule: the domain might be paid for by the client, or by the agency under a support contract. The problem is that this is usually never spelled out, and at expiry the person left holding the bag is whoever's closest. If an agency sells support, it's worth pinning down: where the domain is registered, who owns it, who has access, which email gets the notices, who pays for renewal, and how many days ahead the alarm goes off. It's protection against the "why didn't you warn us" conversation.

How far ahead should you warn about a domain expiring?

The sensible practice for an agency isn't one last-minute notice, but stages: for example, at 30, 14, 7, and 3 days. That leaves room to approve a budget, track down registrar access, and pay, even if the client is slow to respond. Pingvera warns you about an approaching expiry ahead of time — weeks, not days — so you have time to renew calmly instead of fighting a fire.

Read also: SSL certificate expired: how not to miss the date · Site not working: how to check availability.