Free tool / website down checker

Is your website down, or is it just you?

Enter a website address and Pulse will request it from our monitoring servers and tell you what came back. If it answers here but not for you, the fault is on your side of the connection, and this page explains how to tell which.

One check, straight away. No account, no card, nothing to install.

Check a website From outside your network

Ask somebody else
to try it.

We check the homepage, even if you paste a deeper page. One check per website every 12 hours.

[ Down for everyone, or just you? ]

What "my website is down" usually turns out to mean

When a website will not load, the cause is about as likely to be between you and the site as it is to be the site itself. A stale DNS entry, a VPN, an overzealous browser extension, an ISP hiccup or a cached error page will all produce exactly the same blank screen as a genuinely dead server.

The way to separate them is to ask from somewhere else. The check above runs from Pulse’s servers, on a different network, with no cookies and no cache of yours. If it gets a clean response and you do not, the website is fine and your route to it is not.

Failure modes What actually goes wrong

The ways it breaks
without telling you.

01

It is down for everyone

The server is off, overloaded, misconfigured or out of disk. You will get an error code or a timeout here too. This is the one case where waiting for the host to fix it is the right move.

02

It is not down, it just refused us

Plenty of large sites turn away automated visitors. A 403 or 429 from a bot filter says nothing about whether a customer can reach the site, so the checker reports that as blocked rather than down. Open it in a browser to see what a person gets.

03

The SSL certificate expired

The server is perfectly healthy and every visitor sees a full-page security warning instead of your website. Browsers make this look like the site is gone. It is the most preventable outage there is.

04

The domain lapsed

A renewal notice went to an inbox nobody reads, and the domain now points at a parking page or nowhere at all. The website is still sitting on the server, untouched and unreachable.

05

DNS has not caught up

After a host or domain change, different networks see different answers for hours. The site is genuinely up for some people and genuinely down for others, and both of them are right.

06

It is only down for you

A cached DNS record, a VPN, a corporate firewall, a browser extension or your ISP. If the check above says the site answered, this is where to look, and the steps below sort it in about two minutes.

07

It loads but does not work

The page answers perfectly while the booking widget never appears, the form delivers nowhere or the checkout errors. No availability check will ever catch this, including this one.

08

It answers, but far too slowly

A site that takes thirty seconds is functionally down for most visitors even though it eventually responds. Our check gives up before that, so a timeout here is worth treating as a real fault rather than a quirk of the checker.

The test Five minutes, done properly

Check it yourself,
the way a customer would.

01

Run the check above first

It costs nothing and it immediately halves the problem. A clean response means the server is answering and you can stop looking at the host.

02

Try it on mobile data

Turn Wi-Fi off on your phone and load the site. A different network with different DNS is the fastest second opinion you can get.

03

Open it in a private window

That rules out cached pages, cached redirects and browser extensions in one step. If it works here, clear your normal browser’s cache.

04

Flush your DNS cache

On a Mac, `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`. On Windows, `ipconfig /flushdns`. This fixes the majority of works-for-everyone-else cases.

05

Turn off the VPN and any ad blocker

Both routinely block whole domains, and both do it silently. Worth ruling out before you phone your host.

06

Check the certificate and the domain expiry date

If the browser shows a security warning rather than an error, the certificate has expired. If the site has been replaced by adverts, the domain has. Neither needs a developer to diagnose.

If it failed

If it is genuinely down, the useful question is how long it was down before you noticed.

Almost nobody finds out about their own outage first. It is usually a customer, a colleague or nobody at all: the visitors simply leave. A scheduled check removes that gap: something else watches the site and tells you, with the time it started and what the server actually returned, so the conversation with your host begins with evidence rather than a guess.

Check it automatically No card required

Rather not remember
to check?

Pulse can watch the journey for you on a schedule and tell you the moment it stops working, with a screenshot of what a customer would have seen. Start with one website free.

One check, straight away. No account, no card, nothing to install.

Useful answers Without the jargon

Questions about
website down checker.

How can I tell if a website is down for everyone or just me?[+]

Use the check above. It requests the site from Pulse’s servers, on a different network with no shared cache or cookies. A clean response there while it fails for you means the problem is local: DNS, VPN, browser cache, an extension or your ISP.

Why does the checker only treat 200 OK as up?[+]

A 200 means the server actually delivered the page, and redirects are followed to the final destination, so a result of up is never a guess. A 401, 403 or 429 is reported as blocked rather than down: those mean the server turned our request away, usually bot protection or a rate limit, which is not the same as the site being unavailable to your customers.

The check says my site is up, but I still cannot reach it. What now?[+]

Work through the steps above in order. Mobile data and a private window between them resolve most cases, and a DNS flush covers most of the rest.

My site loads but the booking form does not work. Will this catch that?[+]

No, and neither will any other availability checker. A page can return a perfectly healthy 200 while the booking widget, contact form or checkout inside it is broken. That needs a real browser to work through the journey, which is what Pulse does on its paid plans.

How often can I check the same website?[+]

Each website gets one outbound check every 12 hours, and each visitor can check up to three websites an hour. The limits exist so the checker cannot be pointed at somebody else’s site as a crude load test.

Can I be told automatically when my site goes down?[+]

Yes, and that is the point of it. Free monitoring watches one website and notifies you, without a card. Paid plans check more often and go further into the journeys customers actually use.