How to evaluate third-party hosting risks for my small business
Summary
This guide helps you troubleshoot and resolve: How to evaluate third-party hosting risks for my small business. Follow the steps below to fix the issue.
Common Causes
How to Evaluate Third-Party Hosting Risks for Your Small Business
Small businesses often choose commodity or budget hosting providers to minimise upfront costs. While these services can appear economical at first glance, they frequently shift operational burdens onto the business owner. Evaluating third-party hosting risks requires looking beyond the monthly price to understand who is responsible for uptime, security, backups, and compliance when something goes wrong.
Understanding Commodity Hosting vs Managed Infrastructure
Commodity hosting typically provides raw server space or shared resources with minimal oversight. The provider maintains the physical hardware, but the customer is responsible for software updates, security patching, performance tuning, and troubleshooting. Managed infrastructure services, by contrast, include proactive monitoring, routine maintenance, and a defined point of accountability for the hosting environment.
Key Differences in Support Models
- Reactive support queues: Common with budget providers. You submit a ticket and wait in a general queue, often with offshore teams and no guaranteed response time.
- Proactive monitoring: Standard with managed services. Issues are detected and resolved before they affect your website or email, often without you needing to raise a request.
Australian Data Sovereignty and the Privacy Act 1988
Australian small businesses must consider where their data is physically stored. Under the Privacy Act 1988 and the Australian Privacy Principles (APPs), organisations are required to take reasonable steps to protect personal information. Storing data offshore can complicate compliance and create legal obligations regarding cross-border data flows.
Ask your hosting provider the following specific questions about data residency:
- In which Australian city or state is my data physically stored?
- Are backups replicated to an offshore location?
- Which laws govern access to my data by the hosting provider or third parties?
- Can you provide written confirmation that data remains within Australian borders?
- How do you handle data requests from foreign government agencies?
Evaluating Your Current Hosting Provider
Follow this step-by-step methodology to assess the risk level of your existing hosting arrangement. Record your findings in a risk register using the scoring table provided below.
Step 1: Review Support Options in Your Control Panel
- Log in to your hosting control panel. Common platforms include cPanel, Plesk, or a proprietary dashboard.
- In cPanel, look for the Support or Contact section in the right-hand sidebar.
- In Plesk, navigate to Help > Contact Support from the top navigation menu.
- Note whether live chat, phone support, or only ticket-based assistance is offered. Record the stated response times.
Step 2: Check Invoices and Terms of Service
- Open your most recent hosting invoice. Look for line items labelled Malware Removal, Priority Support, Backup Restoration, or SSL Installation.
- Review your Terms of Service for clauses regarding Uptime Guarantee, Liability Limitation, and Data Location.
- Identify any fees charged for support tickets or emergency restores.
Step 3: Verify Server Location
- Find your website's IP address in your hosting dashboard (often listed under Server Information or Account Details).
- Visit an IP lookup tool such as
https://whatismyipaddress.com/ip-lookuporhttps://iplocation.net/. - Enter the IP address and note the country and city listed. If the location is outside Australia, document this as a potential data sovereignty risk.
Step 4: Review Backup Settings
- In cPanel, navigate to Files > Backup or Files > JetBackup if available.
- In Plesk, go to Websites & Domains > Backup Manager.
- Confirm the backup frequency (daily, weekly, monthly) and retention period.
- Determine whether backups are stored off-site or on the same server as your live website.
- Attempt a test restore of a non-critical file or directory to verify the process works without opening a support ticket.
Step 5: Test Support Response Time
- Submit a non-urgent enquiry through your provider's support portal.
- Record the date and time of submission.
- Note how long it takes to receive a substantive reply, not just an automated acknowledgment.
Step 6: Document All Vendors
Create a list of every vendor involved in your online presence, including:
- Domain registrar
- DNS provider
- Email host
- Website host
- SSL certificate provider
Hosting Risk Scoring Table
Use this checklist to rate your current provider. Assign one point for each "Yes" answer in the high-risk column.
| Risk Factor | Low Risk | Medium Risk | High Risk |
|---|---|---|---|
| Support model | Proactive monitoring with SLAs | Ticket-based with defined response times | Reactive queue only, no guaranteed response |
| Data location | Australian data centre, confirmed in writing | Australian data centre, not confirmed in writing | Offshore or unknown location |
| Backups | Automated, off-site, self-service restore | Automated, on-site, support-assisted restore | Manual or no backups available |
| Security patching | Provider-managed OS and control panel | Customer-managed with provider guidance | Customer-managed, no guidance provided |
| Vendor consolidation | Single provider for domain, hosting, email, SSL | Two to three providers | Four or more separate vendors |
Scoring:
- 0–1 high-risk factors: Low overall risk
- 2–3 high-risk factors: Medium overall risk
- 4–5 high-risk factors: High overall risk
Troubleshooting Common Hosting Failures
Backup Restoration Failure
If a backup fails to restore:
- Verify that you have sufficient disk space available on the target account.
- Check that the backup file is not corrupted by attempting to download it locally.
- Ensure you are restoring to the correct directory path (e.g.,
/public_html/for cPanel or/httpdocs/for Plesk). - If the restore fails repeatedly, open a ticket with your provider and request a manual restoration from their off-site backup.
DNS Propagation Delays
After changing nameservers or DNS records, changes may not appear immediately:
- Use a DNS propagation checker such as
https://www.whatsmydns.net/to verify global propagation. - Flush your local DNS cache. On Windows, run
ipconfig /flushdnsin Command Prompt. On macOS, runsudo killall -HUP mDNSResponderin Terminal. - Allow up to 48 hours for full propagation, though most changes appear within a few hours.
- If email stops working after a DNS change, confirm that MX records were not accidentally overwritten.
SSL Certificate Errors
If visitors see certificate warnings:
- Check the expiry date in your hosting control panel under Security > SSL/TLS (cPanel) or Websites & Domains > SSL/TLS Certificates (Plesk).
- Ensure the certificate covers both the www and non-www versions of your domain.
- If using AutoSSL in cPanel, check the SSL/TLS Status page for failed domains and run Run AutoSSL again.
- If the certificate is expired and you cannot renew it yourself, contact your provider immediately.
Consolidating Hosting Under an IT Service Partner
Moving hosting under a single IT service partner reduces vendor sprawl and creates clear accountability. Instead of managing separate relationships for domains, hosting, email, and security, one organisation oversees the entire stack.
Criteria for Selecting a Managed IT Partner
- Australian-based support team with local business hours
- Regular security patching and operating system updates
- Managed backups with documented and tested restoration procedures
- Compliance guidance aligned with the Privacy Act 1988 and Australian business obligations
- Clear SLAs for uptime and support response times
- Transparent billing with no hidden fees for malware removal or priority support
If your current provider scores as medium or high risk, consider migrating to a managed partner. Plan the migration carefully to avoid email downtime or data loss. Do not cancel your existing service until the new environment is fully tested and DNS changes have propagated.
If you need assistance evaluating your hosting provider or planning a migration, Open a Ticket.
Still Having Issues?
💻 Open a Ticket