Websites
Status, speed, content
A page is up only if it answers the way you said it should: the status code, a response time limit, text that must appear on the page, or a header that must be present.
Solution · PulseWatch
Know before your customers do.
When a website goes down, a mail server stops answering, or a Transport Layer Security (TLS) certificate quietly expires, you usually hear about it first from an unhappy customer. PulseWatch checks your websites, mail servers, Domain Name System (DNS) records, ports and hosts around the clock, emails you when a check keeps failing and again when it recovers, and warns you before a certificate expires.
What it checks
The things customers notice first.
Each monitor is one address and one kind of check. PulseWatch runs it on a schedule and keeps the result, so an outage has a start time and an end time.
TLS certificates
Expiry warnings
Every check of an https:// address reads the certificate’s expiry date. You get an email when one is within 10 days of expiring (the window is adjustable), plus a weekly certificate summary.
Mail, DNS, ports and hosts
The rest of the stack
A mail server must answer with a ready greeting, a name must resolve, a port must accept a connection, and a host must answer a ping — each checked on its own schedule.
How it alerts
One email when it breaks, one when it’s back.
A single slow response is not an outage. PulseWatch opens an incident only after two checks in a row fail (the threshold is adjustable), emails you once, and emails again when the check passes. Every incident is kept with its cause and how long it lasted.
PulseWatch is the one Curtilage service that runs from outside your network — it has to, because that is where your customers reach you from. The checks need nothing but the addresses you give them.