Questions

It looks up the domain name through Cloudflare's DNS, opens a secure connection to the site from a Cloudflare data center, follows up to four redirects, reads the response code and the page title, and times the whole thing. If the secure connection fails, it tries plain http to tell a dead server from a broken certificate, and if the name fails it tries the www or bare twin of the name. Then it says which step broke, in order.

From the Cloudflare data center nearest to you; the result says which city. It's one outside view, on a different network from yours, which is what you need to answer "is it me?". It isn't a check from every country.

Then the problem is between you and the site: your Wi-Fi, your provider, a stale address in your device's cache, a cookie or extension in your browser, or a block on your office network. The result lists the tests in order; the is it me guide goes deeper.

Three usual reasons. Your browser is showing a cached copy. The site blocks automated visitors (it answers 403 to us; we say so and count it as probably up). Or the site is up in your region and down from the data center that checked it. Press "Check again" in a minute; if it's still red, send the link to the site's owner.

It tells you the certificate was rejected by a strict client, which is what a browser is, and whether the server still answers on plain http. It doesn't read the certificate's dates or names. The certificate guide shows where to find those.

Each result is shared for 60 seconds, so if someone checked the same site a moment before you, you see their result and the site isn't asked twice. The result shows the time it was actually checked. Press "Check again" after a minute for a fresh one.

The free checker takes a domain name and asks for its home page. Watching a specific page, a login or an app is part of monitoring; tell us what you need and we'll quote it.

Yes. Every result has a link (downinfo.com/?site=yourdomain.com). Whoever opens it gets a fresh check of the same site. Send it to your host or web person instead of describing the error.

Nothing in a database. The result is cached on Cloudflare's network for 60 seconds. Your "last checks" list lives in your own browser and you can clear it. Cloudflare keeps standard request logs for a short time. The site you check sees a request from Cloudflare's network with our user agent, DownInfoBot, not your address. Details on the privacy page.

Thirty checks a minute from one connection. That's enough for anyone troubleshooting by hand; it stops scripts from using us to hammer a site.

One request to the home page over https, no redirects followed. Any answer other than a server error counts as up, including a redirect to a login page. Nothing answering within six seconds counts as down. It's a home-page check, so a service can be green while its app is broken.

Ask through the contact page. We keep it at twenty so the board loads fast, so adding one usually means swapping one out.

No. The free checker and the board are live; the monitoring and the status pages are being built. The monitoring page says what it will do. Requesting early access costs nothing and commits you to nothing.

It depends on how many sites you'd like watched and how many people get the alerts, so we quote each setup. Tell us your sites on the contact page. You get the quote and an email when it's ready for your site, and you can say no at that point.

The checks and alerts are automatic. The alert names the step that failed and what to do. If you'd like a person to fix it for you, WebLandscapes can; that's quoted with the monitoring.

No. We can't make your site stay up, and texts and emails travel over networks we don't control. We'll tell you what we saw and when.

The page is built on the monitoring: the checks write it, so it stays accurate without you remembering to update it. If you need something different, tell us and we'll quote it.