Websites & APIs

Monitor domain expiry: keep registration and TLS deadlines separate

Enable the daily domain check, read the confirmed expiry date beside SSL and understand unknown, failed and stale results before a renewal deadline.

Subscribe via RSS
In this article

A valid TLS certificate does not tell you how long a domain registration will remain active. A website can have a recently renewed certificate while its domain still needs attention at the registrar. Keeping these two deadlines separate helps you notice the right problem early.

MetriBeacon can check the registration expiry of a website's domain and display the latest confirmed result beside its SSL information. This guide explains how to enable that check, read the result and react when the registry does not provide a reliable date.

Separate domain registration from the certificate

A domain registration reserves a name through a registrar. A TLS certificate helps a client verify the identity of a service and establish an encrypted connection. Their expiry dates come from different sources and can change independently.

An HTTP availability check answers another question: did the service return the expected response? A healthy website result is useful evidence about the service now, but it does not confirm the next domain renewal. Use domain, certificate and application observations together without treating one as a replacement for the others.

The certificate monitoring guide covers the TLS side. The domain value described here concerns the registration itself.

Enable the daily domain check deliberately

Open the settings of your HTTP or HTTPS monitor and expand the advanced options. Enable the optional daily domain expiry check, review any alarm settings and save the configuration. New monitors have this additional check disabled until you select it.

Check the website address first. MetriBeacon derives the registration domain from the target hostname. For example, a website under a subdomain generally belongs to the registration of the underlying domain. An IP address is not a domain registration target.

Registry support and the data available for a particular domain determine whether an expiry date can be confirmed. Do not interpret an unsupported lookup as evidence that the registration has expired. The network and certificate guide describes the available check types and target requirements.

Read the current value in the monitor header

Once a date is confirmed, look for the Domain entry in the monitor header. It remains available across the monitor's tabs, independently of whether a chart covers six hours or several days. Click the entry to inspect the domain, expiry date, source and last successful check.

The remaining days are calculated from that confirmed expiry date. They therefore continue to age between registry checks. Opening another tab or shortening a chart period does not require another lookup to keep the displayed remaining time meaningful.

This is particularly useful for a daily check: the last successful lookup may sit outside a six-hour chart window even though its confirmed registration date is still relevant. The domain header does not depend on a point being recorded inside that chart period. It also works for HTTP monitors that do not use TLS.

Understand unknown, failed and stale results

An unknown result means that MetriBeacon does not have a dependable current expiry date. A registry may omit the field, provide conflicting dates or not support the lookup. Those cases should not be converted into a guessed number of days.

A temporary transport failure is different. If a previously confirmed date is still available, the monitor can retain it with a notice about the failed check. Inspect the source and successful-check time before using it to make a renewal decision.

The current freshness limit is 48 hours from the confirmed observation. An older confirmation is marked stale. The date may still help an investigation, but the stale marker tells you that a recent successful registry check is missing. Changing the monitored domain does not transfer the previous domain's confirmation to the new name.

Add an expiry warning that gives you time to act

Choose an alarm threshold that leaves enough time for your own renewal process. A domain handled by a separate finance or customer team may need more lead time than a domain you can renew directly. Verify the notification target and the rule before relying on it.

Domain expiry rules use the current domain result. A missing or conflicting result is not a confirmed recovery, and a domain warning does not turn the website's HTTP availability into an outage. Keep the rule's purpose and the site's current reachability distinct.

A useful operating routine is to review the domain and certificate deadlines together, then check open incidents and the notification delivery history. A correct threshold cannot help if the intended recipient or delivery channel is unavailable.

Check the registrar after a renewal

When an expiry warning appears, confirm the domain and date in the detail panel, then open your registrar account. Check the renewal status and the expiry date recorded there. Automatic renewal is a setting to verify, not proof that a future payment will succeed.

After renewal, allow the registry information to update and review the next successful MetriBeacon check. The display changes when a new confirmed expiry date arrives. Repeatedly opening the monitor does not accelerate the daily registry schedule.

If the values differ, compare the exact domain, data source and observation times. A lookup failure, stale source or disagreement needs investigation; manually treating the monitor as healthy does not update the registry evidence.

Build a small deadline review

Start with one domain you are authorised to manage. Enable its check, inspect the first result and configure a suitable expiry warning. Add a reminder to your operational routine to review stale or unknown results as well as approaching deadlines.

Use the monitor's application checks for reachability and the domain entry for registration timing. Together with certificate monitoring, this gives you three understandable signals without needing a separate domain history chart. You can create a MetriBeacon account and use the website/API template below this article to start with a website you operate.