Many people think of domain, hosting and email as one service, but they are separate. The domain is the address, hosting is the server holding your site's files and database, and email is the service that receives and stores messages. When a domain expires, your files and old emails are not deleted, because hosting is paid for separately. But the address stops working, so nobody can reach those resources by name.
What visitors see
Once the domain stops answering in DNS, browsers cannot turn the site's name into an IP address. Visitors get a "site can't be reached" page, which in Chrome often shows DNS_PROBE_FINISHED_NXDOMAIN. Some registrars point an expired domain to a parking page with ads or an "expired" notice. Either way visitors do not see your site, and many assume the business has closed.
For online shops the damage is greater. Take a flower delivery shop in Tashkent whose domain stopped working just before a holiday. Customers could not open the order page, and the payment system could not send the site notifications for orders already paid, so some orders stayed "unpaid" and had to be reconciled by hand. The files and database were intact, but the business process tied to the domain stopped.
Incoming email is delayed or bounced
A server sending you mail first looks up your domain's MX record. If the domain is down there is no answer. If the error looks temporary, the sending server queues the message and retries for several days. If the domain returns a definite "does not exist", the message is usually bounced straight back. The longer the outage, the more mail is lost and the more senders conclude your address is dead. Your mailbox and old messages stay on the server, but mail apps and webmail usually connect through a name like mail.example.uz, so staff may lose access even to old correspondence.
Outgoing email starts getting rejected
Your server may still be able to send, but recipients may refuse it. Modern mail servers check the sender's domain by looking up SPF, DKIM and DMARC, and many reject or spam-folder mail from a domain that does not exist. Invoices and replies from a company with an expired domain quietly stop arriving.
The chain of SSL, bots and integrations
Other services tied to the domain fail too. Free certificates such as Let's Encrypt renew by proving domain control over DNS or HTTP, which cannot work while the domain is down. A Telegram bot webhook, a mobile app's API, or data exchange with a CRM or accounting system all break if they use the domain name. After recovery, test every integration, not just the home page.
Search rankings
A day or two of downtime rarely hurts rankings much; crawlers simply come back later. If the site is down for weeks, pages gradually drop out of the index and take time to recover. If the domain is deleted and someone else registers it, years of reputation and backlinks pass to the new owner.
What happens stage by stage
In international gTLD zones the lifecycle usually looks like this. National zones, including .uz, may differ, so confirm the details with your registrar.
| Stage | Website and email | Getting the domain back |
|---|---|---|
| Before expiry | Work normally | Normal renewal |
| Grace period | Usually down or parked | Usually renewable at the normal price |
| Redemption | Down | Only with an extra restore fee |
| After deletion | Down | Anyone can register it |
The biggest risk: someone else takes the domain
If the domain is deleted and registered by someone else, a new owner can set their own MX record and start receiving mail sent to your old addresses. If staff used company email to sign up for social networks, banking services or other accounts, password reset emails now go to a stranger. That turns a lost domain from an inconvenience into a security problem, so important domains should never reach deletion.
Checking hosting and domain separately
When something breaks, first find out what. These commands show the expiry date and DNS and mail records; the last one bypasses DNS to check whether the hosting server still serves the site. The IP is a placeholder:
whois example.uz | grep -iE "expir|status"
dig +short A example.uz
dig +short MX example.uz
curl -sI --resolve example.uz:443:203.0.113.10 https://example.uz/If whois shows the date has passed and dig returns nothing, but curl gets a server response, the site and data are safe and you only need to renew. DNS caches may take a few hours to catch up afterwards.
How to prevent it
- Keep the domain's contact email and phone with the person currently responsible.
- Turn on auto-renewal and keep funds on the balance.
- Renew important domains several years ahead.
- Send domain reminders to an address outside that domain too, since its mail stops when the domain does.
In the sayt.uz cabinet domain, hosting and email are managed in one place, so tracking expiry and auto-renewal alongside your hosting is easy.