Submit public page checks through an FTStatus-owned endpoint.
Tool
Page change preview
Preview visible page changes, content drift, or update signals, then turn important targets into continuous monitoring when needed.
Checker preview
Safe server-side check
Validate targets before creating recurring watches.
Change-check preview
This page is ready for a safe server-side checker integration.
Use Changedetection.io only as a private watcher backend when configured.
Promote important pages to recurring monitors after validation and consent.
Watch the signal
Start with a safe one-off preview before enabling recurring checks.
Measure the trend
Keep response, uptime, and incident context close to the decision.
Route the response
Alert the right people and publish customer-safe updates when needed.
How it should work
The FTStatus page collects a public URL, validates it safely, previews the watch, and can later create a Changedetection.io watch through a private server-side integration.
Safety requirements
The backend rejects private and reserved network targets, blocks credentials in URLs, avoids exposing the Changedetection.io admin UI, and keeps API credentials server-side.
Launch path
Start with safe preview checks. Continuous watch creation should be enabled only after the private Docker worker, access control, HMAC or token bridge, and retention policy are verified.
Tool workflow
One-off checks first. Continuous monitoring when it matters.
Tools should help people diagnose a specific target. If the target is customer-facing, FTStatus should turn that check into a durable monitor with alert routing and status-page impact.
Related pages
Continue building the monitoring workflow.
Ready to set up the right monitors?
Start with critical customer-facing services, then add status pages, alert routes, and managed help as reliability becomes more important.