You arrive at work and find the website will not load and client emails have stopped coming in. It turns out the domain expired yesterday and the reminders went to a mailbox nobody reads. There is no need to panic: in the first days after expiry the domain is usually still yours and can be renewed normally. What matters is acting quickly and in the right order.
First confirm the domain is the problem
A site can fail because of hosting, DNS records or an SSL certificate, not only the domain. WHOIS shows the expiry date and status flags, and a DNS query shows whether the domain resolves right now. If the expiry date has passed or the NS query returns nothing, the domain is almost certainly the cause.
whois example.uz | grep -iE "expir|status"
dig +short NS example.uz
dig +short A example.uz @8.8.8.8It also helps to check the hosting directly by bypassing DNS and sending the request straight to the server IP. Take the IP from your hosting details; the one below is only a placeholder:
curl -sI --resolve example.uz:443:203.0.113.10 https://example.uz/If the response contains HTTP/1.1 200 or HTTP/2 200, your files and server are fine and only the name is broken. Nothing needs restoring; the only job is renewing the domain.
The first hours: pay for renewal straight away
Shortly after expiry a domain can usually be recovered at the normal renewal price. How long that window lasts depends on the zone and registrar, so do not count on it. Log in to your cabinet, top up the balance and renew for at least a year. If the payment fails or the domain is missing from the cabinet, contact support immediately with the exact domain name.
Do not try to transfer the domain now. Transferring an expired domain often fails or drags on, raising the risk of sliding into the expensive redemption stage. Leave changes to the owner details until the domain is active again.
Why the site does not come back instantly
The payment went through and the cabinet shows the domain as active, yet the site still does not open. This is DNS caching. While the domain was down, ISP resolvers and public DNS servers remembered a "no such domain" answer for a set time, and some users keep getting it until that cache expires. This usually takes minutes to a few hours, occasionally longer. Compare several resolvers; if one returns the right IP and another does not yet, it will sort itself out:
dig +short A example.uz @8.8.8.8
dig +short A example.uz @1.1.1.1
dig +short NS example.uzTo clear the cache on your own Windows machine, run ipconfig /flushdns and restart the browser. Also note that some registrars point an expired domain's NS to a parking page; after renewal make sure the NS records point to your own servers again.
What happened to email during the outage
Servers that tried to mail you while the domain was down behave in one of two ways. If the error looked temporary, the message stays in the sender's queue for several days of retries and usually arrives once the domain is back. If the domain returned a definite "does not exist", many servers bounce the message immediately, so some mail from those days may be lost. After recovery, check your records and send yourself a test from another address:
dig +short MX example.uz
dig +short TXT example.uzThe MX record should point to your mail server and the TXT records should include SPF. Ask key partners, suppliers and your bank to resend anything they sent during the outage.
Telling clients and partners
Take a private school in Tashkent. During admissions the domain expired, parents could not open the application page and their emails to the admissions office bounced. The domain was renewed on day two, but parents had no way of knowing. The school posted a short notice on its Telegram channel and sent an SMS: the site had been down for a day for technical reasons, it was back, and applications sent in that period should be resubmitted. Being open like this keeps trust and recovers lost requests.
Check the SSL certificate too
While the domain was down, automatic renewal of a free certificate could not validate the domain. If the certificate was due in those days, browsers may now show a warning. Check the expiry date with:
echo | openssl s_client -connect example.uz:443 -servername example.uz 2>/dev/null | openssl x509 -noout -enddateAutomatic renewal usually succeeds on its next attempt. If it has not within a day, ask support to reissue the certificate.
Making sure it does not happen again
- Replace the contact email and phone on the domain with those of the person responsible today.
- Turn on auto-renewal and top up the balance ahead of time.
- Renew important domains for several years at once.
- Add the expiry date to a shared calendar with a reminder a month ahead.
In the sayt.uz cabinet the expiry date and the auto-renew setting sit on the same page, so checking them takes a couple of minutes.