How to Setup Domain Monitoring?

Domain monitoring automatically tracks your domain name's expiration date via WHOIS lookups and alerts you well before it lapses — preventing website outages, broken email, and the risk of permanently losing a domain you've built your brand on. This step-by-step guide shows you exactly how to set up domain monitoring in MonitoringDaddy in just a few minutes.

What Is Domain Name Monitoring?

Domain name monitoring is an automated service that periodically queries the WHOIS registry for your domain and records its expiration date. When the expiry date falls within your configured alert window — say, 30 days from now — MonitoringDaddy fires an alert so you have enough time to log in to your registrar and renew before anything breaks.

Unlike website uptime monitoring, which checks whether your server is responding at this moment, domain monitoring focuses entirely on the registration lifecycle of the domain itself. The two work as a complementary pair: uptime monitoring catches server-level failures; domain monitoring catches registration-level failures.

Why Domain Expiry Matters More Than You Think

A forgotten domain renewal is surprisingly common — and the consequences are severe:

• Website goes offline. DNS records stop resolving the moment a domain enters the grace or redemption period.
• Email stops working. MX records depend on a live domain; expired domains break every email address on that domain instantly.
• SEO damage. Search engines de-index unreachable sites quickly, and recovering lost rankings can take months.
• Brand hijacking risk. Domain drop-catchers monitor expiring domains 24/7 and can snap up your domain within hours of it lapsing.
• Redemption fees are expensive. Most registrars charge $80–$200 or more to recover a domain in the redemption grace period — if recovery is even possible.

How Domain Monitoring Works

MonitoringDaddy uses WHOIS protocol queries to fetch authoritative registration data for your domain at the interval you choose. Here is what happens under the hood:

1. At each check interval, the platform sends a WHOIS query to the authoritative registry for your domain's TLD (e.g., Verisign for .com, Nominet for .co.uk).
2. The response is parsed for the Registry Expiry Date (or Expiration Date field, depending on the registry format).
3. The expiry date is compared against the current date to calculate days remaining.
4. If days remaining falls at or below your configured threshold (e.g., 30 days), an alert is sent to all configured alert channels.
5. Alerts continue on each check until the domain is renewed and the new expiry date is reflected in WHOIS.

Because domain registrations change slowly, a 15-minute check interval is more than sufficient — there is no need for 1-minute polling as you might use for uptime checks.

Domain Monitoring vs. SSL Certificate Monitoring

These two monitors are often confused but track completely different assets. If you want full coverage, you should run both:

• Domain monitoring — tracks the WHOIS expiry date of the domain registration itself.
• SSL certificate monitoring — tracks the TLS certificate expiry date served over HTTPS on port 443.

A domain can be fully registered and live while its SSL certificate has expired (causing browser security warnings), and vice versa. Enable both for end-to-end protection.

Before You Begin

• Confirm your domain is currently active and registered (check your registrar's dashboard).
• Have the root domain name ready — use the bare domain without any protocol or path (e.g., example.com, not https://example.com/).
• Decide your alert lead time — how many days before expiry you want to start receiving warnings.
• Have at least one alert channel configured (an email address or a webhook URL for Slack, Discord, or similar).
• Note your domain's current expiry date so you can verify the monitor picks it up correctly after setup.

How to Set Up Domain Monitoring — Step by Step

Step 1: Monitor Name

Give your monitor a clear, descriptive label so you can identify it instantly on your dashboard or in alert messages.

Good naming conventions include the domain name itself and a hint at what it covers, such as example.com — Domain Expiry. This is especially helpful when you manage multiple domains across different clients or projects.

Step 2: Domain Name

Enter the root domain name without any protocol (http:// or https://), without a trailing slash, and without any subdomain or path.

Correct inputs: mybusiness.com, store.co.uk, startup.io
Incorrect inputs: https://mybusiness.com, www.mybusiness.com/home

Step 3: Monitoring Interval

Choose how often MonitoringDaddy queries WHOIS for your domain's expiry date. Because registrar records update at most once per day, a high-frequency interval is unnecessary:

• 15 minutes — default and recommended for all domain monitors
• 30 minutes or 1 hour — perfectly fine, reduces WHOIS query volume
• 1 minute — not recommended; no benefit for domain expiry tracking

Step 4: SSL Certificate Monitoring

While setting up domain monitoring, you will see the option to also enable SSL certificate monitoring:

• ON — recommended if you also want alerts before your SSL certificate expires (covered in detail in the SSL certificate monitoring guide)
• OFF — if you already have a separate SSL monitor for this domain or don't need SSL alerts

Step 5: Enable Domain Name Monitoring

This is the core toggle for this guide. Set Domain Name Monitoring to ON. This activates WHOIS-based expiry tracking for the domain you entered.

If this toggle is OFF, the monitor will only perform uptime checks (if configured) and no domain expiry alerts will fire regardless of other settings.

Step 6: Set Expiry Alert Days (Lead Time)

Choose how many days before domain expiration you want to start receiving alerts. This is your lead-time warning window:

• 60 days — recommended for business-critical domains, e-commerce sites, or domains with manual renewal processes
• 30 days — recommended for most domains; this is a widely used industry default
• 15 days — minimum safe option; leaves less buffer for slow registrar processing or team availability issues
• 7 days — use only if you have automated renewal and just want a last-chance safety net

Step 7: Alert Condition

Set the alert condition to trigger domain expiry notifications. The recommended setting is:

You can also enable this alongside the domain expiry alert so you get notified if the domain lapses and the URL stops resolving entirely — giving you a second layer of protection.

Step 8: Alert Channels

Add at least one alert channel so notifications are delivered reliably when a domain is approaching expiry:

• Email alerts — recommended for everyone; use a shared team inbox rather than an individual address so alerts are not siloed
• Webhook alerts — post notifications directly to Slack, Discord, Microsoft Teams, PagerDuty, or any custom endpoint that accepts a POST request

Consider adding two channels (e.g., email plus Slack) for critical domains so the alert is impossible to miss.

Step 9: Optional Website Availability Check

You can optionally keep the URL becomes unavailable condition enabled alongside domain monitoring. This means the same monitor will both track domain expiry in advance and alert you immediately if the domain stops resolving entirely — useful as a last-resort safety net if the domain somehow lapses before your earlier warnings were acted on.

Recommended Domain Monitoring Configuration

Best Practices for Domain Expiry Management

Enable Auto-Renew at Your Registrar

Domain monitoring is your safety net — but auto-renew at your registrar is your first line of defense. Log in to your registrar and confirm that auto-renew is enabled and that a valid, up-to-date payment method is attached. Even with auto-renew on, monitoring provides a backup alert in case the payment fails silently.

Set the Renewal Lead Time to Match Your Workflow

If your renewal process involves procurement approvals, finance sign-offs, or client coordination, set your alert window to 60 or even 90 days. Registrar grace periods are not a safety buffer — they are an emergency lane, and relying on them risks data loss and downtime.

Enable Registrar Lock (Transfer Lock)

Most registrars offer a transfer lock (also called a registrar lock or EPP lock) that prevents unauthorized domain transfers. Keeping this enabled alongside monitoring means even if an alert is missed, an attacker cannot hijack the domain through a fraudulent transfer before you act.

Use a Shared Team Email for Alerts

Avoid routing domain expiry alerts to a single person's inbox. Use a team alias like devops@yourcompany.com or a shared Slack channel so the alert is visible to whoever is available, regardless of holidays or staff changes.

Monitor All Domains, Not Just the Primary One

Typo-squatting protection domains, country-code TLDs, and brand-variant domains are just as vulnerable to expiry-related loss. Set up separate monitors for every domain in your portfolio. See the free domain monitoring tool for a quick way to check any domain's status.

Verify the WHOIS Record After Setup

After saving your monitor, check the MonitoringDaddy dashboard to confirm it has successfully fetched the WHOIS expiry date. If the expiry date shown does not match what your registrar reports, it may indicate a WHOIS privacy/proxy service that blocks automated lookups — in which case, contact your registrar to whitelist monitoring queries or use a non-proxied registrar record.

Troubleshooting Domain Monitoring

WHOIS Expiry Date Not Detected

Some registrars use WHOIS privacy protection services that mask the actual registrant and expiry date. If MonitoringDaddy cannot retrieve the expiry date, try the following:

• Temporarily disable WHOIS privacy at your registrar to confirm the raw WHOIS record is publicly accessible.
• Verify the domain name was entered without http://, www., or any trailing characters.
• Test the domain manually using a public WHOIS lookup tool to confirm the expiry date is visible.

Alerts Not Being Received

• Check that at least one alert channel is configured and saved correctly in your MonitoringDaddy notification settings.
• For email alerts, check spam/junk folders and whitelist alerts@monitoringdaddy.com.
• For webhook alerts, confirm the webhook URL is valid and the endpoint is accepting POST requests.

Domain Shows as Expired but Site Is Still Live

This can happen when a domain is in the grace period (typically 0–30 days post-expiry) and the registrar has not yet suspended DNS. Treat any expiry alert as urgent even if the site appears live — DNS can be cut at any moment during the grace period.

Next Steps

With domain monitoring active, your domain portfolio is protected against the most common and damaging registration failure. To complete your monitoring stack, also enable SSL certificate monitoring so you're alerted before TLS certificates expire, and website uptime monitoring to catch server-level outages in real time. For a full overview of available plans and domain monitor limits, visit the pricing page.

Frequently Asked Questions