Websites and digital presence
Is the website down for everyone or only for you?
Safe checks to work out whether a website problem is local, browser-related or affecting visitors too.
What you will learn
You'll know simple checks to separate a local viewing problem from a wider website issue.
Before you continue
Do not change DNS, nameservers or hosting settings while guessing.
Stop and get help before changing DNS, domain or hosting settings, especially if the website supports business enquiries or payments.
Start with another connection
Open the website on a phone using mobile data, not the same Wi-Fi. If it works there, the site may be fine and the problem may be local to your internet connection, browser or device.
Do not change website settings yet.
Try another browser or private window
Open the website in a different browser or private window. This can help separate a website problem from a cached page, extension or browser session.
If only one browser has trouble, make a note of that.
Check the exact address
Look at the full address. A missing letter, old bookmark or wrong ending can take you to a different place.
If your site has both www and non-www versions, check the version your customers normally use.
Check your hosting or website platform status
If your provider has a status page or dashboard, open it directly from a saved bookmark or by typing the address yourself.
Avoid clicking support links from unexpected outage emails.
Do not rush DNS changes
DNS and domain changes can make a problem worse if the original issue is only temporary or local. Write down what you see, take a screenshot if useful and ask for help before changing records.
What to expect
You have checked the website from another connection and know whether to investigate the site, browser or internet connection.
Sources and further reading
- Core Web Vitals report · Google Search Console Help
Supports checking real user and site-level issues rather than relying on one local view.