Responding
A public web server answered the request. Try the page on your device too: sign-in, search, streaming and other features may use different systems.
Check whether a public website responds from our server. A quick second opinion when a page won’t open, with a plain explanation of what we can actually tell.
One server location · Homepage only · A short check, not a worldwide outage verdict
Open the website yourself ↗A public web server answered the request. Try the page on your device too: sign-in, search, streaming and other features may use different systems.
Some sites block checkers or require a sign-in. We tell you when that happens, instead of turning a bot filter into a false outage report.
A server error, DNS issue, timeout or certificate problem is a clue. Check the provider’s official status page and compare another connection before drawing conclusions.
This checker makes a small request from one server location. A successful response suggests that the website is reachable there. It cannot prove that a service works everywhere. Compare the result with your own connection and the provider’s official status page.
A 403 response can mean that the website blocks automated checks. A 429 response means it is limiting requests. Neither response by itself means the website is down.
No. It starts at the public homepage over HTTPS and follows up to two safe redirects. It does not sign in, run the website’s JavaScript, test APIs or download games, videos or images. A working homepage does not guarantee that every feature works.
Results are reused for three minutes. A new network check is limited to three per minute per visitor connection and ten per minute across the whole service, with at most two checks running at once. A busy message is a safety limit, not a result about the website you entered.
Only the domain is sent to LoschaZ, not your URL path or query. The server uses Cloudflare’s encrypted DNS service to resolve public addresses, then makes a small request to the target website. The target sees our server address, not your connection address. Normal hosting access logs still apply.
Site Check makes header requests, with a small capped fallback only when a server does not support them. No page contents are shown or saved. There are no continuous monitors, visitor votes or invented outage histories.
The submitted domain and result are stored in a small, bounded private cache. Results are reused for up to three minutes; each cache slot keeps its latest entry until it is overwritten. Cloudflare DNS receives the domain for address resolution. The tool uses a rotating, server-secret hash of the connection address for short rate limits; it does not store raw visitor addresses in that quota file. Quota entries expire after one minute and are removed on the next fresh check. Hosting access logs may still contain request addresses. Read our privacy information.
Public websites only. Private networks, IP addresses, custom ports and unsafe redirects are excluded. Checks can be unavailable when their small shared budget is busy; games do not need this service to work.