Inventory every dependency
List hosting, domain registrar, DNS, files, databases, email, analytics, licenses and payment integrations with ownership details.
Keep separate copies
Maintain an independent backup outside the hosting account so one lost login or server failure cannot remove every copy.
Test recovery
A backup is only an assumption until restored. Run a safe test, record the outcome and update the recovery instructions.
Protect the registrar first
The domain controls where the business points. Use a unique password, multifactor authentication, recovery information you control and renewal alerts that do not depend on the same domain email.
Document DNS and integrations
Save DNS records and identify email, analytics, forms, payment tools and external APIs. Restoring website files alone will not restore services that depend on missing connections.
Give recovery an order
Write the sequence for regaining domain access, restoring hosting, importing data and testing critical functions. During an outage, an ordered checklist reduces rushed changes and forgotten dependencies.
Frequently asked questions
Is a hosting backup enough?
No. Keep an independent copy and document access to the domain, DNS and connected services.
How do I know a backup works?
Test restoration safely and record the date, result and any missing dependencies.
A responsible next step
Use this guide to identify one action you can complete and document. Avoid changing everything at once. A small test with clear records usually teaches more than a large campaign built on assumptions.