More self-hosted services need DNS and SSL checks
As the number of services grows, checking the app itself is often easier than checking the surrounding setup. Important checks include DNS records changing by mistake, getting close to expiration, missing , CORS problems on APIs, robots.txt or sitemap issues on public websites, and domain settings that break after migrations.
Possible ways to watch these issues include , custom scripts, Prometheus with Grafana, and outside monitoring services. Simply renewing s and hoping nothing else breaks is easy, but it becomes risky as more services are exposed to the internet.
Key points
- Running more services means checking domains and s, not only app uptime.
- DNS record mistakes, expiry, and missing can break .
- CORS problems can stop APIs from working correctly in browsers.
- robots.txt, sitemap files, and domain settings can matter for public-facing sites.
- , custom scripts, Prometheus with Grafana, and external services are possible monitoring choices.