Keep the route familiar
Watch A, AAAA, CNAME, MX, NS and TXT records. Check that records exist, include your expected values or match the complete set.
HomeDNS & domain monitoring
KEEP YOUR ADDRESS IN GOOD COMPANY.
A good domain deserves a lookout.And a gentle nudge before renewal.
Your website has an address. Your email has a route. Your domain has a renewal date. Give those quiet essentials their own owl, with separate DNS and domain-expiry checks in one clear view.
Start free. No card required.
A little notice before renewal
Choose a 1–90-day warning window for the expiry date published by the domain registry. Give your team time to check renewal with the registrar.
No date? No guessing.
Not every registry shares an expiry date. Unavailable or ambiguous evidence stays unknown, with no invented healthy result or false recovery.
A MOMENT FROM EVERYDAY MONITORING
The website is awake. Where did the email go?
A DNS edit quietly removes the mail record. Your homepage still loads, so its HTTP monitor stays healthy. An MX monitor notices the expected record is missing and starts the usual confirmation and alert flow. Different lookouts, one steadier day.
Public resolvers cache DNS records. Changes become visible according to DNS TTLs and propagation; this is not a global propagation test.
SMALL SIGNALS, EVERYDAY WORK
What could your owl listen for?
Keep the post owl on course
Check that your mail provider’s MX record is still present after a DNS edit.
Mind the signposts
Expect the CNAME your service needs. A wrong turn should not stay quiet.
Small records, important jobs
Watch a required TXT verification record. Match the text you expect, without surrounding quotes.
Renewal without the last-minute flap
Ask for a warning 30 days before the published registry expiry. Then confirm payment and auto-renewal with your registrar.
FROM FIRST STEP TO STEADY WATCH
Find your footing in three steps.
Choose your lookout
Open Domains & DNS in Monitors. Choose DNS records or Domain expiry; each has its own focused settings.
Set the expectation
For DNS, select records and values. For expiry, enter the registered domain and your warning window.
Keep one calm watch
Use your existing notifications and confirmation rules. DNS failures and verified expiry warnings follow the same incident flow.
ROOM FOR YOUR WATCH
Included from your first Free nest.
Free: 3 monitors, checks from 5 minutes · Starter: 10 monitors, checks from 3 minutes · Team: 30 monitors, checks from 1 minute · Business: 100 monitors, checks from 30 seconds. Enterprise allowances are arranged with Blastup.
Slack, Teams and mobile push on every plan. Monitor email alerts on paid plans.
A few things you might be wondering.
Is this included in Free?
Yes. DNS and domain-expiry monitors count toward your normal monitor allowance. Slack, Teams and mobile push are available on every plan; monitor email alerts require a paid plan.
How often are expiry dates refreshed?
Registry evidence is cached in shared Redis for up to six hours. Expiry monitors support hourly or longer intervals; daily is a useful starting point. Each check compares the known date to the current time.
Does this replace TLS monitoring?
No. Domain registration and TLS certificates have different expiry dates. Use separate monitors for each.
Can every domain be checked for expiry?
No. Some registries lack a supported RDAP service or omit a clear expiry date. Those checks stay unknown and do not open or resolve incidents.
Does this confirm auto-renewal or successful payment?
No. It reads the registry’s published expiry date. Your registrar remains the source for renewal settings and billing.
Do you check private DNS or global propagation?
These checks use public recursive DNS. They do not inspect private zones or promise visibility from every region.
A HELPING WING
Ready for the practical details?
Keep DNS records on the right pathGive domain renewal a little noticeGive passing hiccups a little patience
Browse more monitors & detections guides in the help center.