Domain Expiration Monitoring

A domain that expires does not fail loudly at first. The website may keep working for a while, then the name stops resolving and the site, the email, and every link that depends on it go quiet. The cause is often small: a card that expired, or a reminder sent to a mailbox nobody reads.

This page describes what to do with an independent warning, and what that warning can and cannot do. For how the date is read and where it comes from, see How to Check When a Domain Expires. For what happens after a missed renewal, see What Happens When a Domain Expires?.

Why a separate warning helps

Registrars send reminders, but they depend on one contact address. If that address belongs to a former employee, a web agency, or a mailbox that is full, the reminders reach no one. A warning from a monitor does not replace the registrar's, but it comes from a second source and goes to the people you chose.

An ordinary availability check also cannot warn you in advance. It reports a problem after the domain has already stopped working. A domain check exists so that you never reach that point.

The workflow

1. Add the website

For every website you add, UptimeWire takes the domain from the website address and checks its registration date. You do not add the domain separately. The check is included on every plan, the Free plan too.

2. Choose the warning period

You choose how many days ahead you want to be warned, separately for each website. The default is 30 days. A longer period gives more room when renewal needs approval or the person who pays is away. A shorter one suits a domain that renews automatically and that you only want to hear about when renewal has failed.

3. Receive the warning

The registration date is checked once a day. When it comes within your chosen period, UptimeWire sends one warning by email and by Telegram. It does not repeat the warning every day. Webhook, Discord, Slack, and Microsoft Teams do not carry domain warnings, so keep email or Telegram on for this.

A domain warning is not an incident. It does not open one and it does not appear as downtime.

4. Confirm the date with the registrar

Open the registrar account for the domain and read the expiry date there. The registrar is the authoritative place. If its date differs from what you expected, find out why before you do anything else.

5. Renew

Renewal happens at the registrar and is up to whoever manages the domain. UptimeWire has no part in it. Check that automatic renewal is on and that the payment method on file is valid.

6. Check the new date

After renewing, check that the registrar shows the new expiry date. The next daily check updates what UptimeWire shows.

A worked example

This is an invented example, not a customer case. A freelancer looks after a small shop website for a client. The domain is registered under the client's account, and the registrar's reminders go to the client's old email address. The freelancer sets a 30-day warning for https://shop.example/.

Thirty days before the date, a warning arrives by email. The freelancer asks the client to renew. The client finds that the card on file expired months ago, updates it, and renews. Without the warning, the first sign would have been the shop going offline.

When no date is shown

Some registries do not publish an expiration date. UptimeWire then shows the domain as unknown and sends no warning. An unknown date does not mean the domain is safe. For such a domain, keep your own reminder in a calendar, and ask the registrar where the date is shown.

What this does not do

• It does not renew or restore domains. Renewal is yours.
• It does not cover every domain you own. It checks the domain behind each website address you monitor. Other domains need their own entries or another tool.
• It does not give an exact-moment alert. The date is checked once a day.
• It does not check who holds the domain or whether payment will succeed. It reads the expiry date, nothing else.

When this fits

This workflow suits anyone whose business depends on a domain they do not renew every day: owners who delegated renewal, freelancers and agencies looking after client domains, and teams where the person who registered the domain has moved on. The more of the process is automatic, the more the warning acts as a safety net for the day the automation fails.