Website projects
Keep a website’s expected responses and private check history together, so you can repeat the same check after a change.
Open Website projects, then select a website or add and verify one. Your project and run evidence stay private.
Save what a useful response looks like
A project keeps one public website URL and the response you expect. Checks observe DNS, HTTPS, redirects and public response content from the NosHost server. They do not run the page’s JavaScript.
Set the expected HTTP status. You can also save an expected final URL and a short, case-sensitive text marker from the response. A baseline helps you review later changes.
Before the first check
- Use the exact public hostname you manage.
- Publish its verification TXT record or HTTPS file and keep it in place.
- Save the recovery key shown once when you create the project.
- Review the response you expect, then run a check manually.
Worked example: the page responds, but is it the right page?
Illustrative configuration and outcomes. These are explanations of saved expectations, not measurements of a customer website.
Saved expectation
A public help page should return HTTP 200 at its saved final URL and include the public text Help centre in the HTTP response.
- Expected response observed
- The status, final URL and text marker match. That observation covers the saved URL and response at the recorded time. It does not test a login, contact form or browser rendering.
- Expectation failed
- The server returns HTTP 200, but the marker is absent. Open the returned page and check whether a maintenance page, different template or changed text explains the mismatch. The response alone does not establish the cause.
- Measurement unavailable
- The request cannot complete. Review the recorded error and retry when appropriate. Missing response evidence does not prove the website is down and does not resolve an earlier mismatch.
If the expected text appears only after JavaScript runs, use a release check or the deployment investigator to inspect the rendered page.
What the history covers
Each observation comes from one server at its recorded time. The history retains up to 100 observations and events for 30 days. Project settings and the latest observation remain until you delete the project.
The workspace shows whether scheduling is enabled. You can run checks manually. Selecting an interval does not activate scheduling when the administrator has it disabled.
Keep recovery keys and webhook secrets private. Project exports omit those secrets; review website information before sharing any report. Read the data and retention details.