Skip to main content
WebTools

Is this website down?

Check whether a website is responding right now, from our server: status, response time, redirects, IP addresses and HTTPS.

Run all checks with the Website Health Check

Choosing a check opens its page. With the keyboard, use the arrow keys, then press Enter.

Popular website checks

Checked from our server every few minutes. Select a site to check it yourself.

A snapshot from one location, not uptime monitoring. Names and logos belong to their owners.

How this check works

We send one ordinary web request to the address from our server, follow any redirects, and report what came back: the HTTP status, how long each step took, where the redirects ended and which IP address answered. If the site ends up on plain HTTP, we also try HTTPS once to tell you whether it works.

It is a single check from one place at one moment. A site can be working for us and not for you, or the other way round, so the result also helps you work out where a problem is.

What the results mean

If the site is down for you but online here

Try another network (for example mobile data instead of Wi-Fi), restart your router, clear your browser and DNS cache, or switch off VPNs and browser extensions. If the site is offline here too, the problem is most likely with the site or its hosting.

Frequently asked questions

The site says it is online but I can't open it. Why?

We check from our server, so the problem may be between you and the site: your internet connection, your DNS settings, a firewall or browser extension, or a regional outage. Try another network or device, clear your DNS cache, or wait a few minutes and check again.

Why does it say online when the site shows an error?

If the server answers at all, it is online, even when the answer is an error such as 404 or 503. We show those as Attention with the status code, because the site is reachable but not working normally for that page.

Does this check monitor the site over time?

No. Each check is a single snapshot from one location at the moment you run it. Results are saved for about a minute so repeated checks don't hit the site again. It isn't uptime monitoring, and we don't send alerts.

Why might a site block this check?

Some sites refuse automated requests, for example with a 403 or 429 status or a bot challenge. Our check identifies itself as ToolSiteCheck, so a site that blocks it may still work normally in a browser.

What does "Unable to determine" mean?

We couldn't get a reliable answer for a reason on our side, for example the site only has an IPv6 address and our server has no IPv6 connection, or the site's DNS servers didn't answer.

Related tools

  • SSL Certificate Checker

    Check whether a site's HTTPS certificate is valid and trusted, which names it covers, and when it expires.

  • HTTP Header Checker

    See the HTTP status and every response header a website sends, for the final page and each redirect on the way.

  • Security Header Checker

    Check which browser security headers a website sends (HSTS, CSP, X-Content-Type-Options, Referrer-Policy and Permissions-Policy) and what they do.

  • Redirect Checker

    Follow a web address through every redirect, with the status code, destination and timing of each hop.

  • DNS Lookup

    Look up the DNS records published for a domain, one type or all common types at once, or the reverse DNS name of an IP address.

  • MX Lookup

    See which mail servers receive email for a domain, in priority order, with each server's addresses.

  • SPF Checker

    Check that a domain's SPF record is valid, stays within the 10-lookup limit, and says what you expect about servers that may send its mail.

  • DMARC Checker

    Find the DMARC policy that applies to a domain, see what each setting means, and spot mistakes that make receivers ignore it.

  • Website Health Check

    Run the main website, DNS and email checks on one site at once and get a short report, area by area, with links to the full results.