A little more context
Three signals, kept separate
Each one answers a different question. We show where the information came from and when it was checked.
Direct website check
When you enter a website, we make one short request from our server and report what happened: whether the address resolved, whether a secure connection worked, and what HTTP response came back. A successful check means we reached the site from our network at that time. It doesn’t prove the site works for everyone.
Community reports
Visitors can say which part of a named service is giving them trouble. Reports contain no account identity or free text, are rate limited, and are counted over a rolling 24-hour window. A temporary keyed hash helps suppress duplicates. Reports are not verified, may not represent the service’s users, and won’t be called an outage without enough volume and history.
Official provider updates
Some services publish their own status pages. Those are useful first-party sources, but we haven’t connected live feeds in this MVP. Service pages link to provider information and clearly show that it hasn’t been integrated here.
Freshness and privacy
Checks are briefly cached to avoid repeated requests to the same site. We don’t save page contents or display submitted URL query strings. Report data in this preview runs in memory and may reset when the app restarts; persistent storage and a written retention policy are part of production readiness.