Choose a provider whose security responsibilities, access controls and recovery commitments are documented, not merely advertised.
How to choose secure hosting: establish responsibility
Start by asking who secures each layer of your website. Shared-responsibility documentation distinguishes provider infrastructure duties from customer duties; an unmanaged virtual server can leave operating-system patches, applications and firewall settings with the customer. The boundary changes with the service selected. [1] Request a written responsibility breakdown for the actual plan, rather than treating the word “managed” as a complete specification.
For a lawful business, review the provider's legal identity, acceptable-use policy and abuse-handling process. Ask how legitimate complaints are investigated, how customers receive notice and how urgent suspension decisions are reviewed. Confirm the locations of production data and backups, contractual privacy obligations and export options. Security due diligence should support accountable operations, not promises to ignore abuse or legal requirements.
Put administrator access on your secure hosting checklist
Check whether the hosting dashboard supports enforced multi-factor authentication, separate staff accounts and permissions tailored to each person's work. CISA recommends phishing-resistant MFA and managing individual access privileges. [2] Ask whether those controls cover billing, domain changes, server management and backup deletion, rather than assuming protection of the website login also protects the hosting account.
Prefer a provider that documents staff-access approval, audit records and account recovery. Ask how access is revoked when an employee or contractor leaves, and how support verifies a sensitive change request. Our guide to phishing-resistant MFA for website administrators explains what to look for when choosing an authentication method. Include recovery procedures in your evaluation, not just the sign-in screen.
Verify transport protection and patch ownership
Transport Layer Security, or TLS, protects data during Internet transmission; certificate management and protocol configuration also matter. [3] Ask how certificates are issued, renewed and monitored, and whether connections between a proxy and the origin server are protected. A certificate included in the plan is one control, not evidence that applications, administrator accounts or stored customer records are secure.
Request supported software versions, maintenance schedules and the process for urgent security updates. Specify who patches the operating system, control panel, website application and plugins; infrastructure maintenance does not necessarily cover customer software. [1] Ask how updates are tested and how failures are reversed. If your team cannot perform the remaining work, budget for a clearly defined management service rather than accepting an undocumented gap.
Require backups you can actually restore
Ask what gets backed up, how often, how long copies are retained and who can delete them. CISA recommends offline, encrypted backups of critical data and regular tests of their availability and integrity. It warns that ransomware can destroy accessible backups. [2] A backup button inside the same account therefore needs further scrutiny: ask what protects recovery copies if that account is compromised.
Agree on acceptable data loss and downtime before comparing plans. Request a documented restore procedure, expected assistance and any recovery charges. Arrange a restoration exercise for your own site after onboarding rather than assuming a successful backup job proves recovery. Use our 3-2-1 website backup strategy to plan additional copies beyond the provider's standard offering.
Check incident support and service evidence
Find out how to reach security support outside business hours and who coordinates containment, recovery and customer updates. CISA recommends maintaining and exercising an incident-response plan with communication and notification procedures. [2] Ask which logs you can access, their retention period and how incident evidence is preserved. Document your own escalation contacts so responsibility does not disappear between the provider and your website team.
Finally, compare the uptime agreement with its exclusions, maintenance windows and remedies. Ask what DDoS protection covers and whether mitigation brings extra charges or service restrictions. Request relevant audit evidence and check its scope against the service you would buy. Secure web hosting is a fit between documented controls and your operational needs; decline a plan when important answers remain vague or contractual commitments contradict the sales pitch.
Sources & further reading
These resources provide background for the explanations above. External links are included for context, not as endorsements.
Official documentation illustrating how infrastructure, operating-system, application and configuration responsibilities vary by service; cited as an example, not a provider recommendation.
Defensive guidance supporting phishing-resistant MFA, access management, offline encrypted backups, recovery testing and incident-response planning.
Explains transport protection and the importance of certificates and TLS configuration; its federal requirements are not presented as universal business obligations.
Written with AI assistance and based on the sources listed above. Published November 16, 2026. No hands-on provider testing is claimed. Read our editorial policy.
