- 01
Record the live dependencies
Verify where the public website runs, who manages the domain, and which provider handles each dependency. Keep forwarding-only domains separate. A saved URL does not establish the live hosting target.
- 02
Check recoverability
Identify the existing backup system and the scope it preserves, including files and database content where relevant. A backup label alone does not prove the right content can be restored. Recovery should be verified through an authorized process.
- 03
Control maintenance
Use established approvals, compatible software versions, and a relevant backup before changes. Coordinate work that may restart services. Check public pages afterward and record unresolved faults instead of assuming the update completed cleanly.
- 04
Keep an incident record
Document the symptom, verified cause where known, recovery action, and evidence of return to service. Separate a confirmed cause from a hypothesis. Use the findings to improve the dependency or process actually involved.
A planning exercise, not a client result
Put the idea to work
Planning exercise: HTTPS is valid but the homepage returns an error. Check the web service and content independently. Renewing an already valid certificate will not restore missing pages, so the incident needs evidence that identifies the actual fault.
What to watch for
- A certificate check treated as full website health
- Backups assumed recoverable without verification
- An outage cause asserted without evidence