Status checks
Browser and API probes request HTML, CSS, SVG, JavaScript, and JSON resources to confirm the edge behaves like a normal HTTPS service.
Network quality
Static pages document latency windows, TLS availability, cache headers, and operational maintenance notices without collecting personal data.
Stable endpoints
The public /api/health response is intentionally simple so monitors can validate the service path with a predictable JSON payload.
Why this site exists
Designed for routine service traffic.
Monitoring tools often load several resources per visit to verify TLS, content negotiation, caching, redirects, and simple API behavior. This decoy keeps those interactions generic and lawful.
- HTTPS landing page and linked internal pages
- Versioned static assets with cache headers
- Robots and sitemap metadata
- Static JSON health endpoint