Website Down Troubleshooting Checklist: A Step-by-Step Guide to Finding the Failure
website-troubleshootinguptimeoutage-responsedns-debugginghosting-support

Website Down Troubleshooting Checklist: A Step-by-Step Guide to Finding the Failure

MMegastorage Editorial Team
2026-11-16
7 min read

Use this step-by-step checklist to identify whether a website outage involves DNS, hosting, SSL, or the application—and recover safely.

When a website stops loading, the fastest path to recovery is a disciplined diagnosis rather than repeated changes. This website down troubleshooting checklist helps you determine whether the failure is caused by DNS, web hosting, TLS, or the application, then gives you safe checks, rollback steps, and an incident-notes template for future outages.

Overview

A website can appear to be down for several different reasons. The domain may resolve to the wrong address, the hosting server may be unreachable, an SSL certificate may not match the hostname, or the application may be returning an error after a deployment. Your browser may also show a cached result that does not represent what other visitors are experiencing.

Start by separating the problem into four layers:

  1. DNS: Does the domain resolve to the intended nameservers and IP address?
  2. Hosting and network: Can the web server be reached, and is the hosting account or server healthy?
  3. TLS and HTTP: Does HTTPS negotiate successfully, and what status code does the server return?
  4. Application: Is the site code, database, plugin, theme, or recent configuration change failing?

Test from more than one network when possible. A site that fails on a local office connection but works over mobile data may point to local DNS, firewall, routing, or caching issues rather than a complete outage.

Do not begin by changing several settings at once. Record the current symptom, time, hostname, recent changes, and each test result. That record reduces guesswork and makes a hosting support request much easier to investigate.

Checklist by scenario

1. The domain does not resolve

Use DNS checks before changing hosting files or application settings. From a terminal, run:

dig +short example.com
dig example.com A
dig example.com CNAME
dig example.com NS

Replace example.com with the affected hostname. An empty response, an unexpected address, or nameservers belonging to the wrong provider suggests a DNS management problem. Check the domain registration account, nameserver delegation, A and CNAME records, and whether a recent transfer or DNS edit was completed correctly.

Also test the www hostname separately. The root domain and www may use different records and can fail independently. If DNS was recently changed, avoid repeatedly editing records while caches are updating. Confirm the intended values first and document the change.

2. The domain resolves, but the connection times out

A timeout usually means the request is not receiving a usable response. Confirm the resolved IP, then check the site over HTTP and HTTPS:

curl -I --max-time 15 http://example.com
curl -I --max-time 15 https://example.com

Review the hosting control panel for service alerts, resource limits, suspended-account notices, expired billing status, server health indicators, and recent configuration changes. On a VPS or cloud server, check whether the instance is running, whether storage is full, and whether web-server, database, or firewall services are active.

If you use a reverse proxy, CDN, load balancer, or managed WordPress hosting platform, check its status and origin-server settings as well as the hosting account. A proxy can be reachable while the origin is unavailable, producing a misleading partial failure.

3. The site returns an HTTP error

HTTP status codes narrow the search:

StatusTypical direction for investigation
404Check the requested path, rewrite rules, deployment files, and application routes.
403Check file permissions, access rules, authentication, firewall rules, and security plugins.
500Review application logs, server logs, recent code changes, PHP or runtime errors, and database connectivity.
502Check the connection between a proxy or web server and the upstream application server.
503Check maintenance mode, overloaded services, process limits, and temporary provider or application failures.

Capture the response headers and body without relying only on the browser:

curl -i https://example.com
curl -sS -o /dev/null -w "%{http_code} %{time_total}\n" https://example.com

For a deeper TLS check, use:

curl -Iv https://example.com

Look for certificate hostname mismatches, expired certificates, protocol negotiation errors, or a redirect loop. Do not disable certificate validation as a permanent fix. If the issue began after changing DNS or hosting, verify that the certificate is installed on the server currently receiving traffic.

4. The homepage works, but visitors see broken pages or features

This is often an application-level problem rather than a domain outage. Check whether the failure affects one URL, authenticated users, a particular browser, or all visitors. Review browser developer tools for failed network requests, JavaScript errors, blocked mixed content, and responses from APIs or third-party services.

For WordPress or another database-backed application, inspect error logs, database credentials, storage capacity, recent plugin or theme changes, scheduled tasks, and cache configuration. If a deployment preceded the incident, compare the release with the last known-good version and identify the smallest safe rollback.

5. The site broke after a migration or DNS change

Compare the old and new environments. Confirm the domain points to the intended server, both root and www hostnames are configured, the database connection works, environment variables are present, and rewrite rules were transferred. Check email-related records separately so a website fix does not disrupt mail delivery.

For domain moves, review the guidance in Domain Transfer Guide and How to Transfer a Domain Safely. For record-specific checks, use DNS Records Explained.

What to double-check

  • Test the exact hostname: Check both example.com and www.example.com, plus any important subdomains.
  • Check from multiple locations: Compare an office connection, mobile network, and an external uptime monitor when available.
  • Separate browser cache from server behavior: Use a private window and command-line requests, but do not assume a private window bypasses every network cache.
  • Inspect timestamps: Match the first failure with deployments, DNS edits, certificate renewals, hosting migrations, scheduled jobs, or security changes.
  • Read logs before restarting: Save relevant web-server, application, database, and firewall logs before a restart removes useful context.
  • Verify backups: Confirm that a recent website backup includes both files and the database. An offsite copy in cloud storage is more useful when its restore process has been tested.
  • Check dependencies: Payment systems, identity providers, APIs, object storage, DNS providers, and email services can create partial outages.

If the issue is a 502 or 503 response, use the dedicated 502 and 503 troubleshooting guide. For monitoring design and recurring checks, see the Website Uptime Monitoring Guide.

Incident-notes template

Incident ID:
Start time and time zone:
Affected hostname(s) and URL(s):
First observed symptom:
Who or what detected it:
Recent changes:
DNS results:
HTTP and TLS results:
Hosting-panel findings:
Relevant log excerpts:
Actions taken and timestamps:
Rollback performed:
Current status:
Follow-up owner and next review date:

Keep the notes factual. Record what was tested and what was not tested; this prevents repeated work during a prolonged outage.

Common mistakes

Changing DNS before confirming the failure: This can make an application or hosting problem harder to isolate and may introduce a second outage.

Restarting everything immediately: A restart may restore service, but it can erase evidence and conceal the underlying cause. Capture logs and metrics first when the situation allows.

Rolling back without checking data changes: Code can often be reverted more safely than database migrations. Confirm compatibility and preserve a backup before reversing a release.

Ignoring certificates because HTTP works: Many visitors and integrations use HTTPS only. Test the complete TLS path, including redirects and alternate hostnames.

Assuming one successful browser load proves recovery: Test key pages, forms, login flows, APIs, and the primary hostname from an external location.

Using an unverified backup: A backup that cannot be restored is not a complete recovery plan. Schedule restore tests and document the steps.

Making emergency fixes permanent: Temporary firewall bypasses, disabled security controls, debug settings, or manual file edits should have an owner and a removal task.

When to revisit

Revisit this checklist before seasonal traffic periods, major launches, hosting migrations, domain transfers, certificate renewals, and planned application upgrades. Use it during a short uptime drill so the team knows who can access DNS, hosting, logs, backups, and monitoring.

Refresh the command examples and escalation contacts when your hosting platform, DNS provider, web server, application stack, or monitoring tools change. Review the rollback path after each deployment, and test a website backup restore on a schedule appropriate to the site’s risk.

After recovery, spend a few minutes completing the incident notes. Identify the first reliable signal, the actual failure layer, the action that restored service, and one preventive improvement. That might be a missing alert, an untested backup, an undocumented DNS record, a resource limit, or a deployment step that needs a safer check. A reusable record turns the next website outage from a search for clues into a defined response.

Related Topics

#website-troubleshooting#uptime#outage-response#dns-debugging#hosting-support
M

Megastorage Editorial Team

Cloud Infrastructure Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.