A website may fail to load because of a hosting problem, DNS issue, domain problem, server error or a problem with the website itself. Start by identifying whether the problem affects everyone or only your device.
1. Check the exact error
Open your website and note the message displayed by the browser.
Common errors include:
- DNS-related errors: The domain may not be resolving correctly.
- 5xx errors: The server or website may have encountered a problem.
- 4xx errors: The requested page or resource may not be available.
- Connection errors: The browser may not be able to reach the server.
The exact error can help identify where to investigate.
2. Check whether the website is down for everyone
Try opening the website from another device or network.
If it works elsewhere, the problem may involve your local browser, network or DNS cache.
If it fails from multiple devices and networks, investigate the website, domain or hosting environment.
3. Check your hosting service
Sign in to your hosting account and check for service outages, account issues or resource problems.
If the hosting server is unavailable, contact the hosting provider or check its service-status information.
4. Check your domain and DNS
Confirm that your domain has not expired and that its DNS records are still configured correctly.
This is particularly important if you recently changed hosting providers, nameservers or other DNS settings.
5. Check recent changes
Think about what changed before the website stopped loading.
Possible causes include:
- WordPress or plugin updates
- Theme changes
- DNS changes
- Server configuration changes
- New custom code
- Hosting changes
If the problem started immediately after a change, investigate that change first.
6. Check SSL/HTTPS
If the website loads over HTTP but not HTTPS, check the SSL/TLS certificate and HTTPS configuration.
A certificate problem can prevent secure connections from working correctly.
7. Restore or seek technical help
If the problem was caused by a recent website change and you have a known-good backup, restoration may be appropriate.
If you cannot identify the cause, provide your hosting provider or developer with the exact error message, when the problem started and what changed beforehand.

Salesforce

