Five-minute uptime checks
Your homepage is requested every five minutes and the HTTP status and response time recorded. You get a timeline of checks rather than a single red or green light.
Your site does not stay healthy on its own
A check every five minutes, an independent second opinion before any alert, and a weekly full health scan that tells you when your score starts slipping.
Monitor my site
Free account
1 site
Email alerts
What monitoring watches
Two jobs: tell you the moment the site stops answering, and tell you slowly when it starts rotting.
Independent outage confirmation
When the primary probe sees a failure, a second independent probe has to agree before you are emailed. One flaky request from one network is not an outage.
Recovery alerts
You are emailed when the site comes back, not just when it goes down — so you know whether to stop what you are doing, without refreshing a dashboard.
Expected-text checks
Optionally require a string to be present on the page. This is how you catch the silent failure where the server happily returns HTTP 200 with an empty or broken template.
Weekly full health scans
The complete five-check audit re-runs on a schedule, so accessibility regressions, new broken links and speed drift surface without anyone remembering to look.
Score-drop alerts and trends
When the combined health score falls, you get an email. Every run is kept, so you can see the trend rather than one number out of context.
Continuous monitoring
Know your site is down before your users tell you.
OmniCheck checks your homepage every five minutes, independently confirms suspected outages, and emails you when your site goes down and when it recovers.
Five-minute HTTP and response-time checks
Independent confirmation before outage alerts
Optional expected-text checks for silent failures
Weekly full-health scans and score trends
Monitor my site
Free account · 1 site · Includes weekly full-site health scans.
Example status
Currently reachable
acme-shop.com
Last checkedJust now
Response time243 ms
HTTP statusHTTP 200
Next checkIn 4 minutes
Ten consecutive checks reached the site successfully.
Why a scheduled check beats remembering
A one-off audit is accurate for about a week. Sites decay continuously, and nobody notices the decay on their own site.
Outages are discovered by customers
Without monitoring, the notification channel for downtime is an annoyed email from someone who tried to buy something. The cost is the sale plus the trust.
Regressions arrive with ordinary releases
A new hero image, a marketing tag, a plugin update — each one can move speed or accessibility. A weekly scan attributes the change to the week it happened.
Silent failures are the expensive ones
A page returning HTTP 200 with a broken template passes every naive uptime check. Requiring expected text is what turns "the server is up" into "the site works".
How monitoring works
Add a site once; it watches itself after that.
-
Add the site
Create a free account and add the URL you want watched, optionally with a string that must appear on the page.
-
We check it on a schedule
Uptime every five minutes with independent confirmation before any alert, plus the full five-check health scan every week.
-
You only hear from us when it matters
Email on a confirmed outage, on recovery, and when the health score drops. Otherwise the trend is waiting for you when you want it.
Monitoring questions
Check frequency, how false alarms are avoided, and what it costs.
How quickly will I know about an outage?
The homepage is checked every five minutes, so a confirmed outage reaches you within a few minutes of the first failed check — the delay is the independent second probe confirming it, which is the difference between an alert you trust and one you learn to ignore.
What stops me being emailed every time the network hiccups?
A single failed request never triggers an alert. The primary probe seeing a failure only raises a suspicion; a second independent probe has to reach the same conclusion before any email is sent. Transient blips from one vantage point are discarded.
Does it catch a page that loads but is broken?
Only if you tell it what "working" looks like. Add an expected text string — a product name, a phone number, anything that only renders when the page is healthy — and a response missing that string counts as a failure even though the server returned HTTP 200.
What does monitoring cost?
A free account monitors one site, including the weekly full-site health scan. There is nothing to enter card details for to get started.
Will the weekly scan slow my site down?
Scheduled scans run on their own queue lanes, separate from interactive work, and are paced so they do not saturate your server. The speed check also runs alone rather than alongside the crawl, which keeps its measurements honest as well as keeping load down.
Can I pause monitoring or change what is watched?
Yes. Uptime checks and scheduled scans can each be paused and resumed independently, and you can edit the URL, the expected text and the scan options at any time without losing the history already collected.
What gets checked every week
Monitoring re-runs these five checks on a schedule. Each one also runs on demand.
Accessibility
Find the barriers that turn visitors away, and the compliance gaps that carry legal risk.
Speed
Slow pages lose sales and rankings. See exactly which pages drag, on mobile and desktop.
Broken Links
Dead ends frustrate visitors and quietly drain SEO. We crawl every page and flag every 404.
AI-Readiness
Check whether ChatGPT, Perplexity and Google AI Overviews can reach, read and quote your content.
Security
Passive checks on transport security, defensive headers and public exposure signals.
Full Site Check
Run every check in one pass and get a single health score with the top three things to fix.