Public domain root URL
Always monitor the public domain. On shared hosting in particular, response-time anomalies are usually your first signal that the shared resources are oversubscribed.
Hostinger covers shared hosting through full VPS, and the monitoring picture changes a lot depending on which tier you're on. Self-hosted (VPS) means you're responsible for the full stack health; shared hosting means you're at the mercy of the host's resource limits and noisy neighbors.
Always monitor the public domain. On shared hosting in particular, response-time anomalies are usually your first signal that the shared resources are oversubscribed.
If you run a CMS like WordPress, monitor /wp-admin separately — not for uptime per se, but because admin slowness often precedes user-facing slowness by minutes-to-hours.
Pick a representative page that requires a DB query (a recent posts page, a search result, a product listing) and monitor it. Static pages will keep responding even when the DB is melting; this is your DB-side canary.
On shared tiers, response time will fluctuate based on what other tenants are doing. Our anomaly detector may flag spikes that aren't really 'your' fault. The fix is moving to a less crowded tier — we don't try to suppress the signal.
If you deploy by uploading files via FTP, partial uploads can leave the site half-deployed. The monitor will go down or degraded; check the deploy log when this happens before assuming it's the host.
WordPress sites have a long tail of monitoring concerns we don't try to cover (plugin updates, database bloat, comment spam queues). Use a WP-specific tool alongside us if those matter.