Homepage checked
Responded in 0.4s, same as every morning.
200
For agencies and freelancers
Know before your client does when something revenue-critical on their website silently fails.
An uptime monitor tells you the site answered. That is not the same as the site working, and it is not what your client pays you for.
10checks, one address
3×confirms an incident
2×clean checks clear it
5minfastest check interval
Every client site, worst first
One list, ordered by what needs you. Press a filter — it works.
- HD Harbour DentalAnalytics tag missing · confirmed, 3 checks Critical
- NL Northgate LegalCertificate expires in 6 days Investigating
- WC Willow & Co.All ten checks passed · 4 min ago Healthy
- BC Brightside ClinicCheck could not run · no conclusion drawn Unknown
- AS Atelier StudioAll ten checks passed · 9 min ago Healthy
Healthy 24
Investigating 2
Critical 1
Unknown 1
Example portfolio. The filters above work — try one.
One silent failure, start to finish
The site answered every time. Nothing an uptime monitor watches ever changed — which is exactly why nobody would have caught this until the client asked why a month of reports showed no visitors.
HD
Harbour Dental
harbourdental.example — analytics check
200 OK
Tracking tag read
Present at every check since this site was added.
present
Tracking tag missing
The page loads perfectly. Nothing is recorded.
still 200
Confirmed — 3 checks in a row
One miss can be a fluke. Three is not.
confirmed
Analytics has been fiction since Thursday.
Every report sent this week used numbers nothing recorded. The site was never down.
What an uptime monitor sees
Responded 200 in 0.4s
Certificate valid
Everything is fine
No alerts. Nothing to report.
What is actually happening
HackedThis page is serving links somebody else injected.
DelistedA noindex appeared. Google is dropping the site.
Reporting brokenThe analytics tag has gone. Reports are now fiction.
Your client finds out first.
Things that answer 200 and still cost money
Every one of these returns a perfectly healthy page. An uptime monitor says everything is fine through all five.
The analytics tag vanishes
Every report you send from then on is fiction, and you are the one who sent it.
The domain expires in nine days
The single most avoidable outage there is, and the one nobody is watching for.
A noindex appears overnight
One line of markup tells Google to drop the site. Traffic falls for weeks before anybody connects it to a deploy.
A page starts serving somebody else's links
Injected spam on a page that loads perfectly. Customers see it before you do.
The contact form takes enquiries and emails nobody Not yet
The page says thank you. The message goes nowhere. Nobody finds out until a client asks why the phone stopped ringing.
The one marked Not yet is the only thing on this page we cannot do today. It is built and it works, but it decides whether an enquiry arrived by waiting for a copy at its own address, and most contact forms never send one there — so it would report a healthy form as broken. It stays switched off until that is fixed.
Ten checks, one address
What actually gets watched, from the URL alone. The rest are on what we check.
01
The website itself
That the site loads for visitors, and how quickly.
02
Domain name
That the domain is not about to expire and take the site down.
03
The padlock in the address bar
That the certificate keeps working. When it runs out, every visitor is shown a full-page warning that the site is unsafe — and renewal is meant to be automatic, so this warns while there is still time to do it by hand.
04
Search engine access
That nothing is telling Google to stay away, and that the sitemap works.
05
Email records
That the domain still receives email, and that its records keep messages out of spam folders.
06
Speed for real visitors
How the site actually feels to the people who visit it — measured by Google from real Chrome users over 28 days, not from a test run here.
How it works
From the address alone. Nothing to install on your client's site, and nothing to ask them to add.
Give us the address
Nothing to install on your client's site, no code to ask them to add, no login to their hosting. One URL and we start watching.
We check from the outside
The way a visitor and a search engine see it — every few minutes for the things that break suddenly, daily for the things that rot slowly.
You hear only when it is real
A problem has to happen repeatedly before we say anything, so an alert you forward to a client is one you did not have to check first.
Alerts you can forward without checking first
Most monitoring cries wolf. One blip at 3am and your client gets an email about a site that was never down — and after the second one, nobody reads the third.
Here a failure has to happen three times in a row before anyone is told, and two successes in a row before we call it fixed.
Problems that are real but not urgent — a lost share image, a slower page — are shown to you and sent to nobody. Six kinds of problem are allowed to interrupt someone. The rest wait to be looked at.
That restraint is the feature. An agency woken for a changed page title stops reading the alerts, and the one they stop reading is the one that mattered.
Not open yet
If you look after client sites and want to try it early, say hello.
Ask about early access
support@peaceofsite.com