Website Down but Hosting Is Online: What to Check

Website down troubleshooting starts by separating the website from its hosting control panel. Your account can be accessible while DNS, a certificate, the web server or WordPress prevents visitors from loading a page. Record the exact browser error and compare the same URL from another device and connection before changing settings.

Start website down troubleshooting with the exact error

Write down exactly what is failing, when it started and who is affected. Test from another device or connection where appropriate. Save the exact error message rather than paraphrasing it. Small details can distinguish a local device problem from a DNS, hosting, account or WordPress issue.

Distinguish a name-resolution failure, certificate warning, timeout and HTTP error. Each points to a different stage of the request. For a live service, technical support can help interpret the evidence before a migration or reset is considered.

Use recent changes to guide website down troubleshooting

Recent changes are often the most useful clue. Look for plugin or theme updates, password changes, DNS edits, hosting migrations, PHP upgrades, new security rules or mailbox configuration changes. Do not assume the most recent change caused the fault, but use the timeline to narrow the investigation.

Protect your recovery options

Before editing files, databases or DNS, confirm that you have a usable backup or another recovery path. A backup is only useful when you know what it contains and can restore it. For security incidents, preserve relevant logs before cleaning up because they may help explain how access occurred.

Compare the domain’s current DNS destination with the address supplied by your host. Then check certificate coverage and the exact server response. The Cloudflare DNS record reference explains the record types involved; preserve existing values before an authorised change.

Follow the request from DNS to WordPress

Start with basic reachability: domain resolution, SSL, hosting response and account status. Then move into the application, plugins, database and individual devices. This order helps avoid spending an hour inside WordPress when the domain is simply pointing at the wrong server.

Change one thing at a time

Multiple simultaneous changes make troubleshooting harder because you lose the ability to identify what fixed or worsened the issue. Record important settings, make one controlled change and test again. If it has no effect, revert it where practical before moving to the next hypothesis.

If DNS and the certificate are correct, give your host the failing URL and timestamps so they can review web-server and application errors. A database message should lead to the database checks below, while a failure after a specific update should be investigated against that change.

Complete website down troubleshooting with service tests

A homepage loading does not prove a website is healthy, and sending one email does not prove mail flow is correct. Test the functions the business actually relies on: forms, logins, checkout, inbound and outbound email, mobile access, SSL and scheduled processes where relevant.

Prevent the same issue from becoming an emergency again

Once the immediate fault is resolved, document the cause and the recovery steps. Keep domain, hosting and email ownership clear. Maintain backups, updates and account security. Record DNS settings and important third-party services so the next incident starts with useful information rather than guesswork.

Related troubleshooting guides

Also see Database Connection Errors and Domain Transfer Checklist for related checks and preventative steps.

Practical takeaway

For website down troubleshooting, diagnose before you repair. Confirm the scope, protect recovery options, check recent changes, test systematically and verify the full service afterwards. That approach is usually faster and safer than trying a long list of unrelated fixes.