You are not watching the site all day

When a public URL stops answering, most owners find out late: a client message, a quiet inbox of form submissions, or a day when ads still spend and the landing page does not load. Opening the site yourself when you remember is not a plan. It only proves the page worked in the moment you looked.

A website down email alert is the opposite habit. An external service requests your URL on a fixed schedule. When the check fails, it sends mail to an address you actually read — with the site name, the URL, and enough context to act.

What the alert is for

The job is time to detection. If checks run every 30 minutes, you learn about a sustained outage on that cadence instead of hours later. Shorter intervals exist on other tools; the useful part is that someone outside your server is looking, on a clock, without you remembering.

Typical failures that should produce a down alert:

  • Connection refused or timed out
  • DNS that no longer resolves to a working host
  • HTTP 5xx from the app or a proxy in front of it

Recovery mail matters too. A second message when the URL answers again closes the loop so you know whether the fix worked without refreshing a dashboard on your phone all evening.

Why the check must be outside your server

A script on the same machine cannot tell you the host is offline. A process that dies with the site cannot send the warning. The useful check is a request from the public internet to the same URL visitors use — the marketing homepage, the shop, the booking form — not only an internal health endpoint you never publish.

Start with the URLs that lose money or trust when they fail. Add campaign or subdomain pages that sit on other hosts; each one can fail on its own.

Email is enough for many small sites

Chat tools and on-call pages help larger teams. For a freelancer, a small agency, or a solo operator, email is the channel that already exists on the phone. A clear subject line with the site name beats a vague “check failed” that forces you to open another app before you know which client is down.

Alerts are only useful if they reach someone who can fix or escalate the problem. Use an address you notice. Pause or expect noise during planned maintenance so you do not learn to ignore the inbox.

Uptime alerts do not replace certificate watching. A page can return a response while browsers block visitors on an expired certificate. That is a different signal — see uptime monitoring vs SSL monitoring and what happens when an SSL certificate expires.

Keep the setup small

You do not need to instrument the server. Paste the public URL, pick who gets mail, and let the schedule run. Watch history long enough to see whether an outage was a blip or a real incident.

SiteOK visits each URL you add every 30 minutes and confirms a healthy HTTP response. When a monitored URL goes down, it emails your registered address with the site name, URL, and a link back to the detail screen on your phone. The dashboard shows current status and a seven-day history. For HTTPS URLs it also tracks SSL expiry beside uptime. Nothing is installed on your server.

Start a free trial. No signup is required — add a URL and see the first checks.