Site Monitor
Site Monitor watches websites you manage for availability, TLS certificate problems, DNS changes, and page-content changes. It keeps a check history and raises alerts when it detects a problem. You can monitor your own business website; sites do not have to belong to a customer record.
When to use this
Add your business website or another public site you are responsible for when your team needs early notice of downtime, an expiring certificate, unexpected DNS changes, or a changed page. Site Monitor is a warning tool, not a guarantee that every outage or security issue will be detected.
Before you start
- You need access to Site Monitor. Ask an administrator about your role if you cannot add or edit sites.
- Use a public
http://orhttps://website address. Private network addresses and local-only hosts cannot be monitored. - Decide who should receive alert emails. An administrator with permission to change Site Monitor settings can add recipients under Settings.
- To run a Deep scan, you must prove you control the domain by publishing the DNS record shown in the site details. Do not scan a domain you do not own or manage.
Add a website
- Open Site Monitor and select Add site.
- Enter the website URL and a recognizable label.
- Choose whether to monitor TLS certificates, DNS, and page content. If a page changes frequently, you can record content changes without sending an alert for each change. You can also enter CSS selectors for sections to ignore when comparing page content.
- Save the site. Its health may show Unknown until its first check finishes.
The overview groups sites by Healthy, Warnings, and Down, and shows the number of open alerts. Filter by health to find a site. A paused site is not checked again until you resume it; an old status is not proof of current health.
Investigate an alert
- Open a site to see its open alerts and recent checks. A check marked Error means the probe could not run; it does not by itself prove the website is down.
- Use Check now for a fresh check. The button has a short cooldown after use.
- For a content-change alert, select View changes when a before-and-after comparison is available. Check the actual website before deciding whether the change is expected.
- After reviewing an alert, select Resolve if appropriate. Resolving an alert records your decision; it does not repair the website, DNS, or certificate. A later check may raise another alert if the underlying condition continues.
If the page cannot load your sites, use Retry rather than interpreting an empty or zero-count screen as a healthy watchlist.
Configure checks and notifications
Open Settings from Site Monitor to set the check frequency, certificate-warning lead time, email recipients, and monthly AI-check budget. Recipients must be valid email addresses. Only users with permission to change Site Monitor settings can save these options.
Alert emails are queued for the configured recipients. Check the alert in Site Monitor as the source of truth; an alert on the page does not guarantee that an email has already been delivered. The AI classifier is not currently a reliable independent security verdict, so do not treat its budget setting as a substitute for your normal security monitoring.
Deep monitoring
Open a site's details to find its ownership-verification DNS TXT record. Publish the exact name and value shown, allow DNS to propagate, then select Verify. Deep scans require verified ownership. The site details explain whether a scan is available for your account.
The included allowance is one manual Deep scan per calendar month. The optional Deep Monitoring add-on is billed at $5 per month and includes daily automatic scans for eligible verified sites. Review the add-on terms in the product before turning it on. Deep scans can discover pages and subdomains and show security findings; a finding needs review and is not proof of a breach. A scan may remain Queued or Running before it becomes Completed or Failed. Use the scan history rather than assuming that starting a scan means it finished.
Troubleshooting
- Website URL rejected: Enter a public website address without embedded credentials. Localhost, private networks, and unsupported URL schemes cannot be monitored.
- No email received: Confirm the recipient addresses in Settings, then inspect the open alert and the account's Communications queue. No email is sent for every check or every recovery event.
- Deep scan unavailable: Check the ownership-verification status and monthly allowance in the site's details. DNS changes can take time to appear; verify the record name and value before trying again.
- No content-change alert: Check whether change notifications are turned off or a section is excluded. Changes may still appear in check history without producing an alert.