Website troubleshooting
A website that fails on one device may still be online for everyone else. Test the hostname, network and exact error before changing DNS or restoring files.
Try another deviceUse mobile data if possible.
Read the errorDNS, HTTPS and HTTP differ.
Check recent changesRouting or application updates.
Compare connections
Test both the root domain and www. Mobile data bypasses the home or office resolver and helps identify a local cache, filtering or router problem.
Identify the layer
A name-not-found error points toward DNS, a certificate warning concerns HTTPS, and a 403, 404 or 500 response means a web server answered. A screenshot and the affected URL help support investigate quickly.
Avoid unnecessary changes
Use Domain Diagnostics and hosting logs to confirm the route. If the issue continues across networks, open a ticket with the test results, time and any recent change.
Article feedback
