Watchdog is Vigilbase's monitoring for your public domains. It checks each domain in two ways:
- Uptime: availability, latency and SSL certificates, probed from several regions.
- Security: scans of HTTPS, security headers, DNS and email settings, exposed files and subdomains, graded A to F.
Watchdog lives on the Monitoring page at https://one.vigilbase.com/dashboard/watchdog. Click Monitoring under Workspace in the sidebar to open it.
Older links to https://one.vigilbase.com/dashboard/monitoring and https://one.vigilbase.com/dashboard/security still work; the second opens the Scans tab.
Monitoring targets
A target is a domain Watchdog watches, with uptime checks, security scans or both. Your Vigilbase team adds and edits targets for you and chooses the probe regions. If a domain you care about is missing, ask through Support.
Until a target exists, the page shows No targets configured.
Summary
Above the tabs, four figures summarise all targets:
| Figure | Meaning |
|---|---|
| Status | How many uptime targets are up, labelled All Up, Partial or Outage. |
| Uptime (24h) | Average uptime over the last 24 hours. |
| Security Score | Average security grade and score out of 100. |
| At Risk | Targets whose latest grade is D or F. |
Overview tab
Overview shows uptime charts and a map of the probe regions. Filter them by Time Range (Last 24 hours, Last 7 days or Last 30 days), by target and by region.
Monitoring Targets lists each target with 24h Uptime, Latency, SSL, the overall Security grade, the HTTPS, Headers and DNS scores, and Last Scan.
Outages tab
Outages lists times a target went down or degraded, with Status, Severity, Monitor, Category, Region, Started, Duration and Events.
Scans tab
Scans shows the Security Posture of your targets from their latest security scans:
- The grade and score of the latest scan, and when it ran.
- Latest scan findings, counted by Critical, High, Medium and Low.
- AI Summary: click Generate AI Summary for a plain-language summary of the scan.
- The list of findings, each with what was found, what was expected and how to fix it. Filter by category (HTTPS, Headers, DNS/Email, Exposure, Subdomains) or severity, search with Search issues..., and download the list with Export CSV.
Scans run on a schedule for every target with security checks turned on. If no scan has run yet, the tab says No security scans yet.
Watchdog traffic on your sites
Watchdog sends a small amount of traffic to the domains it watches. You may see it in your logs or WAF events under these user agents:
| Source | User agent contains |
|---|---|
| Uptime probes | Vigilbase-Monitoring/1.0 |
| Security scans | Vigilbase-Watchdog/1.0 |
https://vigilbase.com/monitoring lists both user agents and the current probe addresses. Security scans run on Cloudflare Workers and have no fixed addresses.
The exposure check asks for well-known sensitive paths, such as /.env or /.git/config, to confirm your site does not serve them. It reads only the start of each response and does not follow redirects. These requests can show up as blocked in your WAF; that is expected.
If you use Vigilbase Shield, traffic from both Watchdog user agents is excluded from your billable bandwidth.
Related
- Run one-off checks of any site with the free Tools.