Domain Expiration Monitoring in Zabbix, Nagios and PRTG or a Hosted Monitor
November 2026 · UptimeHub
Checked from regions with auto-retry. No single-location false alarms.
All systems operational. Steady pulse across every region.
api.example.com returned no response from all 2 regions. Auto-retry confirmed the outage, then we alerted your team.
api.example.com is back up. The incident is logged to your status page history automatically.
90-day uptime · branded · your domain
Live demo · drive it, no signup needed
Zabbix, Nagios and PRTG can all warn you about an expiring domain, but none of them does it out of the box in the way they handle a ping or an HTTP check. You add a script or plugin that asks a whois or RDAP server, schedule it, parse the date and write the alert rule yourself. That is fine for a handful of domains you own. It gets expensive in attention once the list grows, the registry rate limits you or the person who wrote the script leaves. A hosted domain expiry monitor does the same job with no code to maintain.
This is a buyer's comparison for a team that already runs one of these tools and is deciding whether to extend it or hand the job to a hosted service. We are not claiming the self-run tools are bad. They are excellent at what they were built for, and many teams should keep them.
How domain expiry monitoring works in a self-run tool
All three tools follow the same pattern, because a domain expiry date is not a network measurement. It is a record held by a registry, so the tool has to look it up.
- A lookup. A script or plugin queries the registry for the domain, through the older whois protocol or through RDAP, the JSON based replacement that ICANN describes on its RDAP page.
- A parse. The script pulls the expiration date out of the response and turns it into a number of days remaining.
- A threshold. The monitoring tool compares that number with a warning and a critical value and raises an alert.
- A schedule. The check runs once or twice a day, not every minute, because the date changes once a year.
In Nagios and its relatives this is a plugin. In Zabbix it is usually an external check, a user parameter or a script item feeding a trigger. In PRTG it is a custom script sensor, a mechanism the vendor documents in its custom sensor manual. We did not find a built-in sensor or template for registration expiry in these products at the time of writing, so check the current documentation for your version before you plan around that.
Where the self-run route gets expensive
Each piece is small. Together they are a part time job.
| Concern | Self-run script in Zabbix, Nagios or PRTG | Hosted domain expiry monitor |
|---|---|---|
| Extensions that do not return a clean date | You write and test the parser for each registry format | Handled by the service, with a clear message when a registry publishes no date |
| Rate limits on lookups | Many domains checked in a burst can get your server address throttled | Lookups are spread out and cached for you |
| Who is told | Whoever receives your normal alerts, once you map the trigger | The same Slack, email, SMS or webhook channels as your uptime alerts |
| Domain that was deleted | Your script has to treat a not found answer as an alert | An unregistered domain raises an alert |
| Ownership | The script lives in someone's repo and breaks when they leave | A monitor in a dashboard anyone on the team can see |
| Cost | Your time, plus the server the monitoring tool runs on | A monitor slot in the plan |
A worked example with 25 domains
Suppose a platform team runs Zabbix and holds 25 domains: 8 production, 12 redirects and brand variants, and 5 legacy domains from old projects. Writing the first script and trigger takes an afternoon. Adding each domain afterwards takes a few minutes, so call it two hours for the lot. Then three things happen over the following year. Two registries change their response format and the parser starts returning empty. A server migration drops the script from the path. One engineer who knew how it worked moves on.
The failure that matters is the quiet one. A script that returns nothing usually does not alert, so the monitor looks healthy while it checks nothing. That is the same trap as a cron job that stops running: absence of a signal is read as good news. A hosted monitor reports the same problem as an explicit message on the monitor, so a registry that cannot be read does not masquerade as a domain that is fine.
When you should keep the self-run tool
- You monitor internal or private zones that are not in public registries. A hosted external service cannot see those.
- You have a small, stable list of domains and an engineer who owns the script.
- Your compliance rules say monitoring data must stay inside your network.
In those cases, run the script, put the threshold at 30 days or more, and add a second, independent monitor on at least the production domains so a broken script is never your only warning.
When a hosted monitor is the better buy
- The domain list is growing, owned by several people, or includes client domains.
- You want domain expiry in the same place as uptime, so one alert channel and one list of monitors covers it.
- Nobody wants to own a parser.
UptimeHub reads the expiry date from the registry over RDAP, refreshes it at least every 12 hours and alerts when a domain is within 14 days of expiring, already expired or no longer registered. The full description is on the domain expiration monitoring page. Domain checks sit on the Pro plan and above, listed on the pricing page, and they run alongside SSL certificate monitoring and DNS monitoring.
What to do this week
Whichever route you choose, export your domain list from every registrar account today. Compare it with what your monitoring actually watches. In most teams the gap is the domains nobody remembers buying, and those are the ones that lapse. If you currently price tools by what they bundle, the breakdown in our SSL certificate monitoring tools comparison shows how vendors cap certificate checks separately from uptime checks, and the same question is worth asking about domain checks before you sign anything.
Know your site is down before your customers do
Start monitoring your sites, APIs and services from two regions, with alerts by Slack, email, SMS and webhook and a branded status page. Transparent, flat pricing per monitor.