Questions people ask before they start changing settings.
Short answers first. When a topic needs more detail, the relevant guide is linked inside the answer.
What does LookItsDown actually check?
We ask the address to respond from our server. The result tells you whether that request worked at that moment. It does not test every page, login, payment or feature.
Does “working” mean the problem is on my side?
Not always, but it makes a local or regional problem more likely. Try the same address on mobile data, another browser or another device before changing anything complicated.
Why can LookItsDown reach a site that I cannot?
Your browser cache, Wi-Fi, DNS provider, internet provider, account or location can change what you receive. Our check comes from a different server and connection.
Can part of a website be down?
Yes. A homepage may work while login, checkout, video or an API fails. Check the exact page and the website owner’s official status or support channel when the main address responds.
Should I clear my cache straight away?
Try a private window first. It is faster and does not sign you out everywhere. Clear site data only when the private window works and the normal window does not.
Do you store the address I check?
The public recent list keeps only the latest 18 checks: the hostname, result, HTTP status, response time and check time. It does not display a submitted page path, and older entries are replaced by newer checks. See the privacy notice for the full explanation.
Can I check a private or local address?
No. Private networks, localhost addresses and non-standard ports are blocked for safety. Do not submit an address containing a password or access token.
Will recommendations affect the status result?
No. The result is calculated before any commercial recommendation. Affiliate links and advertisements are labelled, and they never change whether a site is reported as working or down.