Website projects
Follow DNS, HTTPS and expected public content over time.
Saved with the project: Website URL, expected response and a bounded observation history.
View worked example for Website projectsKeep the checks you want to repeat
Save a website’s expected responses, check a release or investigate a broken page. Each service starts with a private website project.
Use a website you manage. Verify its exact hostname, then choose the checks you need. Release checks and deployment investigations run when you start them.
What do you need to check?
Release checks
Check expected pages, public text and a short browser journey after a release.
Saved with the project: Page checklist, browser viewport, retained runs and an approved baseline.
View worked example for Release checksJavaScript and deployment investigator
Investigate a page that loads but has broken JavaScript or missing content.
Saved with the project: One page check, expected visible content, retained runs and a baseline.
View worked example for JavaScript and deployment investigatorYour project is the working space
Open Website projects to select an existing website or add one. Hostname verification uses a DNS TXT record or an HTTPS file. Keep that proof in place for later checks.
Project access belongs to your browser. Save the private recovery key shown when you create the project so you can recover access in another browser.
Read about project access and verificationNeed one answer now?
Individual tools remain available for a DNS lookup, certificate check, page comparison or local HAR analysis. Use them when you do not need a saved project.