
When you register a new domain and launch a site on it, monitoring is one of those tasks that's easy to defer — and then forget. This checklist covers everything to configure when setting up monitoring for a new domain so you start with complete coverage rather than discovering gaps after an incident.
The entire setup takes 10–15 minutes in Domain Monitor.
Add your homepage as an HTTP monitor
https://yourdomain.comAdd your most important pages
Add a health check endpoint (if your site has a backend)
https://yourdomain.com/health or equivalent"status":"ok" or similarAdd your API endpoint (if applicable)
Add SSL monitoring for your primary domain
yourdomain.com Add SSL monitoring for www subdomain (if you use it)
Add SSL monitoring for any other active subdomains
api.yourdomain.comapp.yourdomain.commail.yourdomain.comVerify the certificate is currently valid and the chain is complete. See what is SSL certificate monitoring
Add domain expiry monitoring
Confirm auto-renew is enabled at your registrar
Verify the payment card on file is current
Check that the registrant email address is monitored — renewal notices go there. See why domain auto-renew fails
Enable DNS record change monitoring for your domain
Enable nameserver change monitoring — NS record changes are the highest-priority security signal. See how to monitor nameserver changes
Record your baseline DNS records — document current nameservers, A records, MX records so you have a reference to compare against
Add your primary alert contact — email address for all monitors
Add a phone number for SMS alerts on critical monitors — email is too slow for active incidents. See SMS alerts
Add a backup contact — at least one other person who receives downtime alerts
Enable recovery alerts — be notified when the site comes back up, not just when it goes down
Set up Slack notifications if your team uses Slack. See Slack notifications
See how to test your website monitoring setup for a complete testing guide.
If you need to get something in place immediately and expand later:
| Priority | Monitor | Why |
|---|---|---|
| 1 | Homepage uptime | Core availability |
| 2 | SSL certificate | Prevents browser warnings |
| 3 | Domain expiry | Prevents total blackout |
| 4 | Email + SMS alerts | Fast notification |
Everything else can follow once the minimum is covered.
Domain Monitor covers all of the above from a single dashboard. Create a free account.
A subdomain takeover lets an attacker claim your subdomain by exploiting dangling DNS records. Learn how it happens, real-world examples, and how DNS monitoring detects it.
Read moreMean time to detect (MTTD) measures how long it takes to discover an incident after it starts. Reducing MTTD is one of the highest-leverage improvements in reliability engineering.
Read moreBlack box monitoring tests your systems from the outside, the way users experience them — without access to internal code or infrastructure. Learn how it works and when to use it.
Read moreLooking to monitor your website and domains? Join our platform and start today.