Website Down? Step-by-Step Checklist to Diagnose Fast

Few things are more panic-inducing than discovering your website is down. But staying calm and following a systematic checklist will help you identify the cause quickly, and often fix it yourself. Here's exactly what to do.

Step 1: Confirm It's Actually Down

Before assuming the worst, verify the issue isn't on your end:

• Try a different device: Check from your phone or another computer
• Try a different network: Switch from WiFi to cellular data
• Use a down checker: Sites like isitdownrightnow.com or downforeveryoneorjustme.com can confirm if it's global
• Clear your browser cache: You might be seeing a cached error page

If the site loads fine elsewhere, the problem is local to you, likely your ISP, network, or browser cache.

Step 2: Identify the Error Type

The error message (if any) tells you where to look:

• "This site can't be reached" / DNS_PROBE_FINISHED: DNS or domain issue
• 500 Internal Server Error: Server-side code or configuration problem
• 502 Bad Gateway: Server or proxy issue
• 503 Service Unavailable: Server overloaded or maintenance
• 504 Gateway Timeout: Server not responding in time
• 403 Forbidden: Permission or access issue
• 404 Not Found: Specific page missing (site itself may be up)
• White screen / blank page: PHP error or code problem

Step 3: Check Domain and DNS

If you see a DNS error or "site can't be reached":

1. Check domain expiration: Log into your registrar and verify your domain hasn't expired
2. Verify DNS settings: Ensure your nameservers point to the right host
3. Check for recent DNS changes: DNS changes can take 24-48 hours to propagate
4. Verify A record: Your domain's A record should point to your server's IP address

Tools like whatsmydns.net let you check DNS propagation status globally.

Step 4: Check Your Hosting

If DNS is fine, the issue is likely at the server level:

1. Log into your hosting dashboard: Check for server status alerts or maintenance notices
2. Check server resource usage: You may have exceeded CPU, memory, or bandwidth limits
3. Look for billing issues: Unpaid invoices can result in suspended accounts
4. Review recent changes: Did you update plugins, themes, or make code changes?

Many hosts display server status on a status page. Check there for known outages.

Step 5: Check SSL Certificate

If you see security warnings or "connection not private" errors:

• Check certificate expiration: SSL certificates expire (usually annually)
• Verify auto-renewal: If you use Let's Encrypt, auto-renewal may have failed
• Check for mixed content: HTTP resources on an HTTPS page can cause issues

You can check SSL status at sslshopper.com/ssl-checker.html or through your hosting dashboard.

Step 6: Check for Code or Plugin Issues

If you see a 500 error or white screen after making changes:

1. Revert recent changes: Undo the last update, plugin activation, or code edit
2. Access via FTP: If you can't reach the admin panel, use FTP to rename plugin folders or revert files
3. Check error logs: Your hosting panel usually has an error log showing specific PHP or server errors
4. Enable debug mode: In WordPress, set WP_DEBUG to true in wp-config.php to see error details

Step 7: Check for Security Issues

If your site shows strange content, redirects, or Google warnings:

• Scan for malware: Use Sucuri SiteCheck or Wordfence to scan for infections
• Check Google Search Console: Look for security issues or manual actions
• Review file changes: Compare current files to backups to identify modified files
• Change passwords: Immediately change all admin and FTP passwords

If your site has been hacked, restoring from a clean backup is often the fastest path to recovery.

Step 8: Contact Support

If you've checked everything and can't identify the cause:

1. Contact your hosting provider first: They can see server-level issues you can't
2. Provide details: When it started, error messages, recent changes, what you've tried
3. Follow up on domain issues with your registrar
4. Contact your web designer/developer if it's a code or application issue

Prevention: Monitoring and Backups

The best way to handle downtime is to catch it early and recover quickly:

• Uptime monitoring: Services like UptimeRobot, Pingdom, or Better Uptime alert you when your site goes down
• Regular backups: Automated daily backups let you restore quickly
• Staging environment: Test changes on a staging site before applying to production
• Keep software updated: Outdated CMS, plugins, or PHP versions cause many issues

Final Thoughts

Website downtime is stressful, but systematic troubleshooting usually identifies the cause quickly. Work through this checklist step by step, document what you find, and reach out for help if you get stuck. Most issues have straightforward solutions once you know where to look.